This is a time to help a HIVE project help HIVE to have more users in this crucial moment of time. Hive account@dbuzz was onboarding ~1200 users every month to HIVE. During the time Hive account@arcange was publishing his daily statistics, Hive account@dbuzz was #1 or #2 on most days. They did amazing work during the long bear market to grow HIVE.

One might not think of 1200 users as a big deal. What I need you to remember is that this was better than what the other project were doing during the same time. We have to support our winners to even better. The rate of growth should not be allowed to slow down when it is within our power to help.

Delegating Your RC Helps

The problems with Hive account@dbuzz account creation is that their account has a very small amount of HIVE Power resulting in less Account Creation Tokens claimed. Other projects have not come to face this problem in recent times. Not having enough ACTs to onboard users could create a bad user experience and even use many potential users. These users may end up at worse or centralized social media projects that are linked to some Token and a blockchain.

I do not have a lot to delegate due to my existing delegations to primarily made to Hive account@leo.voter and Hive account@zingtoken. I only plan to have enough RC around to perform daily activity without obstructions or waiting. Since my voting power is very low, votes on comments should be below the dust threshold (meaning no payout happens to the account receiving the vote). If there is a plan to share curation rewards, I am very much interested in delegating HIVE Power to Hive account@dbuzz. This is how many projects have managed to gather large amounts of ACTs for user onboarding.

The other option is releasing a separate Token for the project and using that to incentivize delegations. This is a very complicated setup that would take precious development time. Sharing curation rewards in the liquid form is method that has been proven to be effective again and again on HIVE, BLURT and STEEM.

The Onboarding Funnel

It takes one click on the website and the user will be sent to https://join.d.buzz page which they will be asked to select a username. Then they are directly greeted to their private keys and multiple ways to backup the keys. Although some users may find the details intimidating, they will be sure to take the backing up of keys as a very serious act.

I blacked out the keys because I though I had already created the account when I picked the username. Giving this impression could create the sunk cost effect in the user and they could be more likely to follow through the entire process to get their hands on the keys and start using the blockchain.

This is likely the final step. I assume a hash of a phone number will be stored instead of the actual phone number of the user. Asking for the phone number anywhere before the end could have created a larger amount of friction. The user has now backed up their keys, taken screenshots etc. It should be too late to give up for most of them.

This is an extremely well designed funnel. There could be a dark mode made for the night owls who don't want a flashbang at their face in the middle of the night. I have to say that Hive account@dbuzz has made one of the best funnels to get masses into self custody. A link to Keychain website at the end as an option could be the cherry on top. Maybe it is already there. I don't want to create an account to find out.

This is what I see when I visit onboarding page. The lack of Resource Credits is not an issue that has been fixed. It will remain the same unless more users delegate (RC or HIVE Power) to Hive account@dbuzz account. There is a link to https://signup.hive.io which as two more free options. The problem is that these additional steps could create more friction and more potential users could end up giving up and settling for a more convenient but more centralized option.