Asking the top-11 account-creating accounts to cooperate on hash-based HIVE disaster-recovery key inclusion

in #onboardinglast year

Working on the CoinZdense project, I've started looking into its (future) bindings with HIVE a little bit. In my previous two posts here and here on a little spin-off project, hive coinZdense disaster recovery I looked at setting up disaster recovery for HIVE just in case CoinZdense comes to late.

With this little simple tool, a HIVE account holder can use his master password to store disaster recovery info in his account json meta data. This is not the perfect place, and it is inconvenient for integration in account creation, so I've created an issue in gitlab hoping a better more structural way to implement quantum-disaster decovery in HIVE could get implemented.

For those that don't want to go back to my previous posts, a short description: CoinZdense aims to create many-use multi-layer hash-based signing keys for Web 3.0 platforms like HIVE. CoinZdense is not ready yet, and even if it were, there would be many considerations in dimensioning the parameters for its use by HIVE, paramaters that will determine how a master password or private key maps to a public key. Change one parameter for the layer-zero signing key and get a completely different pubkey.

To overcome this problem for disaster recovery, we don't actually use many-use hash-based signing keys, but a trivially simple one-time signing key meant only to allow for a single one-time transaction proving ownership of the account and setting the new hash-based signing keys for that account as a way of disaster recovery after a quantum-computing incident.

So now we have this tool where you as an account holder can prepare your account for disaster recovery. A tool that uses the same master password that account creation does.

But while barely anyone is securing their account for an event that may not be possible for a decade, many new accounts are getting created. I wanted to know who was creating all these accounts, so I ran a little script, processing the account creation transactions in the last 10,000,000 blocks seeing who is creating new accounts. These 10,000,000 blocks roughly represent a full year.

Turns out 11 accounts are responsible for 98% of all new accounts on the blockchain, roughly 230,000 accounts in roughly the last year

accountpercentage of new accounts
@ocdb59.7%
@appreciator15.4%
@steemmonsters11.2%
@threespeak5.5%
@ecency2.8%
@leo.voter1.4%
@roomservice0.6%
@ocd0.5%
@blocktrades0.5%
@therealwolf0.3%
@ocd-witness0.1%

I'dd very much like to talk to the people behind these accounts to see if we could either integrate hive coinZdense disaster recovery as it is now, or try to get this issue prioritized, and integrate a more fundamantal disaster recovery key solution into new account creation.

Support the CoinZdense project

As I mentioned in my talk at HiveFest, CoinZdense is a one-man and unfunded project. You can help support the project by buying project support tokens on hive-engine, by helping out looking at the 1995 style project website, or by advocating with the different target Web3 ecosystem communities.

So far the project has received roughly 30 HBD from sale of project support tokens on hive-engine and from a tiny Paypal donation on the tipping-jar page.

I would really like to spent some structural time on this project, so all donations and support are highly welcomed right now.

Sort:  

Sounds like you're looking at the long term. I'll see if I can buy some of your tokens to help with the project.

Dear @pibara,
Your support for the current Hive Authentication Services proposal (#194) is much appreciated but it will expire in a few days!
May I ask you to review and support the new proposal (https://peakd.com/me/proposals/240) so I can continue to improve and maintain this service?
You can support the new proposal (#240) on Peakd, Ecency,

Hive.blog / https://wallet.hive.blog/proposals
or using HiveSigner.

Thank you!


The rewards earned on this comment will go directly to the people( @pibara ) sharing the post on Twitter as long as they are registered with @poshtoken. Sign up at https://hiveposh.com.

Well, it took a minute, but I am now the proud owner of one whole COINZDENSE