Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th
@learn2code has raised the funds to create a BYTE:STEM diesel pool and for LP distribution.
Currently, @learn2code has 2000 BEE. It costs 1000 BEE to create a diesel pool pairing BYTE with STEM and 100 BEE to create the smart contract for LP distribution. That leaves 900 BEE remaining. When @learn2code can sell enough BYTE to acquire another 200 BEE (at the current rate of around 60 SWAP.HIVE on TribalDEX), the BYTE:BEE diesel pool will also be created.
The BYTE:STEM diesel pool with LP distribution will be set up on April 13, 2024, one week after this post is made.
Thank you to everyone for your support of the Learn to Code tribe and the BYTE token.
0
0
0.000
why byte : BEE and not BYTE:SWAP:HIVE ?
Other than pairing with SWAP.HIVE as the first or second diesel pool for a new H-E token having become rather cliché?😁 I believe that @yintercept made a good point in a reply to one of the previous posts:
I am hoping to be sufficient in creating first layer Hive smart contracts within a year or so (and posting about what I learn here on @learn2code) and then move on to second layer smart contracts. BEE is the token of hive-engine (the token name is "Hive Engine Token"), for example, the airdrop contract requires BEE as payment for it to use a CSV or TXT file.
Therefore, as an aspiring hive-engine smart contract creator I want to abide by Ferengi Rule of Acquisition #33, “It never hurts to suck up to the boss.”😁
Congratulations @learn2code! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 200 upvotes.
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPCheck out our last posts:
Sounds interesting...
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
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.
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.
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.😁
People are strange. One never knows what will set someone off. The video was interesting. People drawn into denouncing witches can become more destructive than the people denounced as witches.
VYB went a little over the top in their distaste for self-voting.
But they do have a point. Both HIVE and SteemIt are dominated by groups that harvest rewards without providing much value.
Of course we are all trying to harvest rewards. Curation accounts harvest coins by upvoting content. IMHO, if the curator is sticking to its formula, then it is providing value. A curator account is only abusive if it upvotes posts outside its dedicated market.
I think that most most of the abuse takes place in the comment section. I upvote comments to encourage commenting. I upvote comments whose rewards are under $0.02 to sweep the dust.
Again, it is difficult to determine what is abuse and what is not in the comment section.
Just Some Brainstorming
Hey, I just had an idea.
We could create a tribe dedicated to harvesting HIVE rewards. The tribe could encourage members to upvote low value content in comments. To hide the design we could make up a word like, maybe, "treads."
The tribe could encourage self voting on the low value content in the treads.
I think that such a tribe could harvest the lion's share of the reward pool.
Come to think of it. Lion would be a good theme for the tribe.
We could give the coin a cat-themed symbol like MEOW.
Ooops. Never mind. Someone else is working that idea.
Yeah, that Star Trek mirror universe version of me that is an intellectual property lawyer was screaming about confusingly similar symbol.
Still might be stepping on a few toes. LasseCash is essentially @lasseehlers because the actual @lassecash account doesn't post LasseCash tribe updates. What @lasseehlers posts is mostly get rich quick stuff. So a reward harvesting tribe posting about 10x or 100x returns could encroach on LasseCash territory.
@memess has a faucet claimer community so might join in on that tribe idea. Right now I have MemeHive, Hive images, and Learn to Code. Soon I'll be doing Political Hive and Paranormal Hive. I guess that's my kind of harvesting.😁
Yep i have faucet claimer, but not a tribe yet if someone what to make a tribe of it feel free to make it with me.
Yep your are the biggest tribe creator of hive.
Very nice. Hope that'll incentivize the developers to keep learning...