Thinking more on proof-of-burn mechanics, I begin to realize that this is derivative-consensus: consensus that is derived from the tokenomics and security of the other chain being burned. Any network or dapp that allows coins from another network to be burned in exchange for native assets inevitably trusts the other network's security.
If I create an asset that can only be minted when HBD is destroyed, I'm trusting Hive consensus and Hive witnesses to follow the rules and defend the network from harm and counterfeit inflation. Likewise if I burn LEO to create new assets I am trusting LEO security and tokenomics (and thus the entire network to succeed).
How much security does LEO have?
There will be a bit more when we get these consensus nodes up and running, but those consensus nodes themselves are yet again derivatives of Hive; second-layer consensus. LEO consensus nodes will trust Hive blocks to be 100% accurate, which is fine.
Hive has a system for deleting bad blocks, and we saw that system in action during the Steem hostile takeover as backup witnesses constantly attempted to transfer funds and/or initiate powerdowns of locked accounts. This forced the sockpuppet witnesses consensus-witnesses to roll-back the chain many many times, ruining many a Splinterlands game.
15 hours of frozen chain.
In any case, LEO trusts the Hive network 100%. Is that a bad thing? What's the tradeoff? Well, for starters 100% of all LEO inflation is controlled by stake holders. There is no block reward, as the operations involved are all stored directly on Hive, which already has separate block rewards and security, which LEO then capitalizes on to build community value.
100% inflation control
Pretty good. We pay $0 for security and pass on 100% of the savings to the stake-holder. Seems like people are taking this deal and loving it. Gogo LEO we believe. When LEO $1? When LEO moon?
So if I created a Proof-of-Burn game that destroyed LEO for magic dust, something I am seriously considering... the dust created would be a derivative of a derivative... pretty weird. I'm sure the crypto madness has only just begun. Think DeFi is weird? Just wait a couple years.
This is bad for Hive, right?!
Building value on Hive is bad for Hive?
So what I'm envisioning is those who hold the index derivative can use the same token to control the network in terms of listings, delistings, and inflation schedule.
You certainly wouldn't want to list just any token. An indexed derivative is trusting every token it lists to enforce proper security.
Obviously just the opposite of listing. If the asset in question becomes corrupted or loses its value it can be stripped of the ability to generate assets.
How much derivative asset is created when XYZ token is burned?
How fast do these burns accrue diminishing returns (log curve)?
Want kind of caps or circuit breakers are in place to avoid failure?
Basically anything I create is going to be on Hive, so branching out to other networks before having a popular working product is out of the question. Originally I was thinking this was only going to work with burning HBD due to the "stable" nature and my political motivation to push my own CDP collateral agenda.Basically if I can spike the price of HBD >$1 it gives the idea more merit and urgency.
But now that LEO is coming out with layer2 consensus nodes I could theoretically just one run of these nodes to perform the same type of burn on LEO instead of HBD. Obviously I'd eventually want both assets listed but hey you never know, maybe I could get a proposal funded by that time. That would be ideal in order to protest the ninjamine being dumped into the dev fund, as I could just burn the HBD I received from the fund to @null in order to farm the governance token and "magic dust" of my own product.
Sinks are an important part of any economy. The first phase is to try and generate inflation in the most profitable ways possible. With POW coins this means low inflation and 100% of it going to secure the network via block rewards to the miners. In terms of LEO and proof-of-burn assets it's a bit different, as inflation can be splashed in a lot of different places, especially if token sinks are trailing behind as a deflationary mechanic, soaking up rogue inflation.
Also, does anyone think it's weird that Ned Scott joins a group called Bitcoinhackers.org and then HiveEngine gets hacked for BTC and Hive but then the Hive gets returned? lol... what... It's more fun to speculate here than to actually dig deeper on this one. Don't rain on my parade. Exit scam? Collusion? Where my conspiracy peeps at?
Breaking away from HiveEngine couldn't come any sooner. We obviously need multiple nodes validating the network. Hopefully there's not any issue with coming to consensus with the randomness of LEO miners. It obviously can't be a local
Ah nevermind I forgot I was misinterpreting this issue. IIRC the randomness is determined by Hive witnesses (signature of current witness plus the previous sig). Once again we see that LEO security is 100% reliant on Hive witnesses, right down to the randomness of mining.
It's hard to imagine Hive running out of RCs, but in all likelihood that is exactly what's going to happen at the end of the year during the mega-bubble. Many do not remember how crazy it was during 2017. I remember running out of bandwidth; do you? This community has stress-tested the RC system zero times, as RCs were created in the wake of the 2017 disaster. Should be interesting to see the superiority of the RC system play out and if there are any bugs lurking.
Accounts that have low stake (say less than 50 HP) are going to have trouble posting/commenting/upvoting as much as they would like. Suddenly, playing a Splinterlands game will be the privilege of the elite until those transactions are taken off-chain to a more efficient database. People will think twice before spending RCs: they'll have actual value.
Just increase the blocksize, bro!
Forcing dozens of nodes to store data permanently is not a scale-friendly solution. I have brought up this issue many times and even top witnesses are like "we'll just increase the size of the blocks". Will you? That makes the cost of running a node higher for every single node in the network. At a certain point that just not an option. This is why we are constantly upgrading scaling solutions like MIRA and Condenser optimizations.
Even at a 65KB limit per block, that's potentially 1.785GB of RAW data added to the chain per day (per node). Raw data is then turned into even more useful data and quick lookup database tables/indexes stored in expensive RAM and offered to dapps built on top of the protocol via API. That's without raising the blocksize limit. How many nodes on Hive can afford that? Users will shut down their nodes if they become too expensive.
Bandwidth isn't free.
The higher we raise the blocksize limit the more prohibitively expensive it is to run nodes. These are the tradeoffs. Many Bitcoin forks have resulted from this exact argument, and to this day Bitcoin blocks remain quite small to accommodate cheap server costs and a more decentralized/robust/secure network. Bitcoin chooses the hardcore resilient option so we don't have to, as the Granddaddy network protects us all from that mean ol' fiat and centralized/bordered regulations.
Better have them RCs!
So it becomes obvious that if you want to build on Hive, you better have a ton of Hive Power so when users actually start competing for RCs and on-chain bandwidth, your dapp actually has enough bandwidth to work during the shitstorm that is a mega-bubble. Without the ability to scale any network loses a lot of users during the bear market. Bloated blockchains need time to deflate.
There's a lot going on right now and a lot to think about. Personally I think burning assets to generate other assets is going to be all the rage within a few years. Communities love a good deflation burn, even if the majority of market cap value is based on growth and demand for the underlying asset. Lowering the supply can't hurt.
I continue to plug away at my Magic Words database.
Things should get interesting once these LEO consensus nodes roll in.
Posted Using LeoFinance Beta