You are viewing a single comment's thread from:

RE: Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th

in Learn to Codelast month

temp.jpg

Thanks for the update on the pool.

I hope you didn't mind my driving up the price of STEM in these last two weeks.

STEM fell to 0.006 on March 6 on low volume. So, I started an accumulation campaign.

I have been playing footsy with a bid bot after the price collapse. I accumulated 2259 STEM in the campaign.

The little run up in price took place on extremely low volume as well.

Your BYTE:STEM diesel pool is a God send for me. I was thinking on staking the STEM. I now plan on putting it in the pool. I assume that I will need equal parts STEM and BYTE when the pool goes live.

I was actually planning on buying STEM with the @buynburn account. @buynburn was planning a huge STEM burn just before you announced the pool. Since you need STEM for the pool, I instructed @buynburn to sell the STEM it collected. It will start buying STEM again after the next price collapse.

BTW: I have 30K STEM in @irivers which has been working as a dedicated STEM curator. 30K STEM puts it in position 13 on the STEM Richlist. I really don't need more STEM than that.

I will accumulate my BYTE-power in @irivers.

Speaking of curation accounts. Is it considered bad form for a curation account that I control to upvote my posts? It usually only upvotes my posts when it can't find other posts to upvote ... BYTE doesn't have 10 posts a day yet.

Thanks again for the time and BEE that you've thrown into this project.

!WINE

Sort:  

Is it considered bad form for a curation account that I control to upvote my posts? It usually only upvotes my posts when it can't find other posts to upvote ... BYTE doesn't have 10 posts a day yet.

O.K. I want to be a little careful here. This is my own personal opinion and not that of @learn2code or the Learn to Code tribe. The self-upvote issue can be controversial and there's no need for the tribe to officially pick a side when it isn't necessary.

Speaking as @holovision or @holovision.stem, my views not necessarily representing those of the tribe:

Within reason I don't think self-voting with an alternate account is unethical. If the account is meant to curate certain content and the self-vote is the same percent as you would give if the exact same post had been written by a complete stranger, then I don't personally see that as a problem.

If I were you I wouldn't use the Verify Your Brain tribe tags in the self-upvote posts. That tribe has chosen a side on the self-vote issue and they are most definitely against self-voting.

That's one of the main reasons I prefer POB over VYB. In my personal view VYB is like a homeowners association on the Hive blockchain. You know how when letters are read in movies and the voice of the person who wrote the letter narrates what the letter says? When I was reading the VYB introduction post I heard Phil Hendrie doing the Bobbie Dooley character voice narrating the VYB intro in my head.

Again, just my own personal views as @holovision or @holovision.stem.😁

Loading...

I hope you didn't mind my driving up the price of STEM in these last two weeks.

No problem. "Decentralized exchange" is just a fancy way to say "crypto bidding." I bought a bunch of STEM a few months ago for @holovision.stem so I know how it is. Whatever STEM @learn2code is able to buy will be deposited as LP reward for the pool(s). There's no goal of how much STEM @learn2code needs to get.

I assume that I will need equal parts STEM and BYTE when the pool goes live.

Yes, 1:1 ratio relative to each token's SWAP.HIVE value on the exchange for how much of each token to pair. So 1 SWAP.HIVE worth of STEM needs 1 SWAP.HIVE worth of BYTE to add 1 SWAP.HIVE of STEM to the pool.

With sufficient liquidity being provided and a few enterprising Hive users (or bots) doing arbitrage the price of STEM should become somewhat more stable. Or at least the pool(s) will be an alternative to playing footsy with a bid bot.😁

I'll answer the second part with my own personal account and not the @learn2code account.