create account

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

View this thread on: hive.blogpeakd.comecency.com

Viewing a response to: @learn2code/byte-stem-diesel-pool-coming-april-13th

· @yintercept ·
$0.04
![temp.jpg](https://files.peakd.com/file/peakd-hive/yintercept/Eo1vsCTtPeDYHqAWrRUULXGZN3i5VsQVDXRGFB1m3SeKizj6kvKyiYLH923DutTaw9a.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](https://he.dtools.dev/richlist/STEM). 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
👍  , , , ,
properties (23)
authoryintercept
permlinkre-learn2code-sbj6sa
categoryhive-188262
json_metadata{"tags":["hive-188262"],"app":"peakd/2024.4.1"}
created2024-04-06 17:19:24
last_update2024-04-06 17:19:24
depth1
children5
last_payout2024-04-13 17:19:24
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.020 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,601
author_reputation27,822,573,478,293
root_title"Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id132,650,345
net_rshares80,991,903,984
author_curate_reward""
vote details (5)
@holovision.stem ·
$0.04
> 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](https://hive.blog/proofofbrain/@vyb.vyb/new-tribe-and-token-verify-your-brain-oror-vybrainium-vyb).

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.😁

https://www.youtube.com/watch?v=M_uDjgqZbkk
👍  ,
properties (23)
authorholovision.stem
permlinkre-yintercept-sbkc2y
categoryhive-188262
json_metadata{"tags":["hive-188262"],"app":"peakd/2024.4.1"}
created2024-04-07 08:11:27
last_update2024-04-07 08:11:27
depth2
children3
last_payout2024-04-14 08:11:27
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.020 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,674
author_reputation379,952,258,600
root_title"Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id132,668,595
net_rshares81,326,081,014
author_curate_reward""
vote details (2)
@yintercept ·
$0.03
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.
👍  , , ,
properties (23)
authoryintercept
permlinkre-holovisionstem-sbn6x5
categoryhive-188262
json_metadata{"tags":["hive-188262"],"app":"peakd/2024.4.1"}
created2024-04-08 21:12:42
last_update2024-04-08 21:12:42
depth3
children2
last_payout2024-04-15 21:12:42
cashout_time1969-12-31 23:59:59
total_payout_value0.016 HBD
curator_payout_value0.016 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,511
author_reputation27,822,573,478,293
root_title"Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id132,708,354
net_rshares79,697,259,951
author_curate_reward""
vote details (4)
@holovision.stem · (edited)
> 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](https://peakd.com/c/hive-134889/created) 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.😁
properties (22)
authorholovision.stem
permlinkre-yintercept-sbpzvn
categoryhive-188262
json_metadata{"tags":"hive-188262"}
created2024-04-10 09:33:27
last_update2024-04-10 09:36:42
depth4
children1
last_payout2024-04-17 09:33:27
cashout_time1969-12-31 23:59:59
total_payout_value0.000 HBD
curator_payout_value0.000 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length781
author_reputation379,952,258,600
root_title"Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id132,750,147
net_rshares0
@learn2code ·
$0.04
> 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.
👍  ,
properties (23)
authorlearn2code
permlinkre-yintercept-sbkbz0
categoryhive-188262
json_metadata{"tags":["hive-188262"],"app":"peakd/2024.4.1"}
created2024-04-07 08:09:03
last_update2024-04-07 08:09:03
depth2
children0
last_payout2024-04-14 08:09:03
cashout_time1969-12-31 23:59:59
total_payout_value0.020 HBD
curator_payout_value0.020 HBD
pending_payout_value0.000 HBD
promoted0.000 HBD
body_length1,015
author_reputation776,556,767,445
root_title"Learn to Code Update: BYTE:STEM Diesel Pool Coming April 13th"
beneficiaries[]
max_accepted_payout1,000,000.000 HBD
percent_hbd10,000
post_id132,668,559
net_rshares81,169,539,200
author_curate_reward""
vote details (2)