RC Delegations!

Now of course they have been live ever since the hardfork occurred, but thanks to @peakd and other tools they are easier accessible to most end users now.

Are you someone who has a lot of RC and can't find what to do with it? Maybe you've claimed some account credits but aren't really using them and are aware they aren't transferable, then here's where your RC would be put to good use!

If you go to your wallet page and click on the magnifying glass you can view your active RC delegations, clicking on "Delegate" you can now also directly delegate RC to an account of your choice.

As you can see in the image above, I delegated my RC to @ocdb, which instantly allowed it to start claiming more accounts due to having more RC left over and the bot likes to keep it hovering at a certain percentage.

What does @ocdb do with the RC and claimed accounts?

For the longest time now it has been offering them for free to @hiveonboard. Although it is close to impossible to completely eliminate account creation abuse, we believe hiveonboard has done a good job at mitigating it through SMS verification and only allowing certain referrers who've proven themselves access to create invite links that bypass SMS verification.

There are many projects using @hiveonboard for account creation and lately we've also seen many users on hive refer new users through it as well. Some of the projects are @peakd and @liketu just to name a few.

How do we know this?

Well, when ocdb creates an account for @hiveonboard, hiveonboard places default beneficiaries on the account given to 1. The service itself (hiveonboard) 1%, 2, The issuer of the account ticket (@ocdb) and 3, the referrer which usually applies either to an account directly who used their Hiveonboard referral link or a front-end itself that a new user clicked through to sign up for an account and was sent to Hiveonboard which usually is 3%.

Notice the json_metadata at the end. Keep in mind that these beneficiaries are not "written in stone" even though they are written in blocks, they can be removed by the owner of the account or simply using a front-end that has its own beneficiaries it places on accounts posting through it. Usually new users aren't too bothered by it and it hasn't seemed like an issue in the past that has been brought up, so for a lot of projects and referrers it's a nice little bonus for having brought them on, possibly helped guide them through the beginning of their Hive journey, until they eventually remove it.

Why delegate HP or RC to @ocdb?

We are one of the possibly only curation projects who aside from taking a very small fee from delegators also send them rewards that occur from projects such as @reward.app or these beneficiaries in question from accounts we create. You can imagine that if enough accounts are created who turn out to be genuine users who become and stay active, keep their beneficiaries up for a short time, it wouldn't take too much for those rewards to add up to surpass the normal limits of curation returns towards delegators. This part is of course a bit speculative and so far we haven't seen all that big rewards coming through this way, nor do we encourage users to send beneficiaries to use in any way shape or form through extra curation or perks within our project, but we think it's a nice added bonus for those who don't mind to reward back to our delegators for supporting manual vetted curation.

If you are someone who uses your HP consistently and wants to continue doing so, then delegating RC in itself to us means that we'll be able to continue offering free accounts to SMS checked users as Hiveonboard is one of the options people see when they try to sign up for a Hive account on Hive.io:

Either way, figured I'd make this post since RC delegations are new and many may probably sit at 100% for longer not doing much with it or needing the excess RC they have due to their HP. So @ocdb could be a good choice until you may find something better to do with it down the line. :)

We'll also make sure to update if anything changes from our end with how we are using our account credits.

Thanks for reading! Feel free to ask if there is anything you're wondering about!