Merge in RC cost rationalization code (there is a small possibility this change doesn’t get into the HF if we encounter too many issues in the next couple of days).
Is this something to do with RC delegation? If so, I'm getting worried...
0E-8 BEE
Merge in RC cost rationalization code (there is a small possibility this change doesn’t get into the HF if we encounter too many issues in the next couple of days).
Is this something to do with RC delegation? If so, I'm getting worried...
I believe he is referring to the changes to custom json costs and other resource credit changes. Resourse credits were implemented in a minimum viable product back on Steem but never re-addressed. The problem is it doesn't scale, it mostly affects low HP users, and that's it. Right now we have 2-4M custom json ops per day, this accounts for around 23-50 ops per second. This is a big chunk of the current daily ops. So re-evaluating their RC costs first is a good start.
As for RC Pools, last I spoke of it it was good to go in this hard fork, I haven't asked about it recently so I am not 100% sure.
That being said, RC are not consensus, so they do not need a hard fork for RC pools to be implemented.