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](https://peakd.com/hive-163521/@holovision/learn-to-code-tribe-and-byte-token-will-launch-march-31): 

> My hope is that a "Learn to Code" tribe would discuss developing #hive-engine programs. In that case, a BEE:BYTE pair might be in order.

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](https://tribaldex.com/airdrop) 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.”😁

> 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

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