Those of us who follow the blockchain core developments are anxiously awaiting hard fork 26. While we haven't received any communication in that sense, it won't happen in July, maybe not even in August, since many are taking vacations during that month. Maybe September then?
At some point, I wanted to write a post that compiled a list of features and connected tools, dapps, and frameworks that will come out with HF26, whether they need a hard fork or not to be released.
It was a surprisingly difficult task, as there isn't one place where you could find them in, as far as I know, and I checked the github project too. I guess the 'easiest' method would be to go through blocktrades posts since he started posting about HF26, which would be quite a while ago. And the core devs recordings. Easy, right? :)
Anyway, the work wouldn't be justified with so little time before the official announcement will come out, where the list of features should be presented.
Today, I want to talk in particular about the Resource Credits delegations (RC delegations, in short). There is another very good post on the topic written by 
We've heard many times about the importance of RC delegations for big projects, for improving the onboarding process, and for driving value to RCs and therefore HIVE (power). All great points.
I just realized last night how important RC delegations will be for personal accounts management, as well.
So, like many people on Hive, I have more than one account. Currently, only this one is for posting, but in the past, I posted on my gaming account and had an account where actifit content went.
Besides that, I have my gaming accounts (one main, and others I use every once in a while, if ever), my staking account (where my HP goes), and a few other accounts, including the ones I just started creating for holding Splinterlands rental cards by different categories.
My main posting account has the majority of the HP. Not directly, but delegated from the staking account, for an additional layer of security.
What I use is the voting power from that HP, besides posting. I proxy governance voting to my staking account, and I generally don't play games with this account (but that's not always the case), so I use it less for posting custom JSONs.
But I would have always almost full RCs, just by using it this way.
To not waste those RCs, I auto-claim 'free' accounts with it, when it gets close to 100%.
But that can change.
For example, my gaming account only publishes custom JSONs, but quite a lot of them. So I have HP delegated to it. Once RC delegations are available, I could use that HP on my posting account for its voting power, and delegate RCs to my gaming account to have enough to broadcast custom JSONs.
The same goes for my Splinterlands rental cards account(s). And basically for any account that only broadcasts custom JSONs or other transactions, but doesn't use its voting power.
Why is it about the voting power and not about any other operation, including publishing posts or wallet transactions?
Because curation rewards are based on your HP, owned or delegated to you. Everything else only needs RCs. Including governance voting, you can proxy it to the staking account, so you don't directly need HP if you have a separate staking account that does the governance voting.
So in my case, among my accounts, this one (
By concentrating HP on accounts that curate, the total active curation stake on Hive will increase. That also means the curation rewards APR will decrease.
Every other account should only need RCs to work, and having HP, directly or delegated to them won't be more useful. Again, governance voting can be proxied to a holding account for HP.
The decrease in curation APR should be compensated by the likely additional market that will form around the RCs delegation.
