There won't be RC pools. We could implement something similar to EOS resource market (and from technical point of view it would be even cheaper and simpler to operate than direct RC delegations), but as far as I know there are no plans for that.
There is (always was) a way to make something that would resemble RC pools, although it has some limits. You can create a "pool account", delegate some HP to it (fill the pool) and then give selected users authority over that account (pool beneficiary). First limit is how many users can be supported by such pool - 40 if I remember correctly is the limit on amount of account type authorities, so you can't give access to the pool for more users. Second problem - it increases RC cost somewhat. The way pool is used is to put small custom json at the front of the transaction that you want to finance from the pool (that is the source of extra cost). That operation needs to declare the pool account as required authority. This way RC will be taken from the pool (it is always taken from first account which signature is required in transaction) and user can still sign with his own private key, as he is part of pool account authority.
Well that sucks. So nothing like delegating HP and in return earning a passive stream of Hive/Leo/TokenX?
I guess I wasn’t paying close attention, I thought that was the obvious thing to build. For me at least, the new RC plans are a big disappointment then.
Of course, my little world of self-interest pales in comparison to how this might improve the blockchain over time. A more robust chain is good for all.
So nothing like delegating HP and in return earning a passive stream of Hive/Leo/TokenX?
There was never such on-chain mechanism, but it does not mean there can't be one on second layer. If you have a plan how it should work you could even create a proposal to finance implementation and make it yourself :o)
There won't be RC pools. We could implement something similar to EOS resource market (and from technical point of view it would be even cheaper and simpler to operate than direct RC delegations), but as far as I know there are no plans for that.
There is (always was) a way to make something that would resemble RC pools, although it has some limits. You can create a "pool account", delegate some HP to it (fill the pool) and then give selected users authority over that account (pool beneficiary). First limit is how many users can be supported by such pool - 40 if I remember correctly is the limit on amount of account type authorities, so you can't give access to the pool for more users. Second problem - it increases RC cost somewhat. The way pool is used is to put small custom json at the front of the transaction that you want to finance from the pool (that is the source of extra cost). That operation needs to declare the pool account as required authority. This way RC will be taken from the pool (it is always taken from first account which signature is required in transaction) and user can still sign with his own private key, as he is part of pool account authority.
Well that sucks. So nothing like delegating HP and in return earning a passive stream of Hive/Leo/TokenX?
I guess I wasn’t paying close attention, I thought that was the obvious thing to build. For me at least, the new RC plans are a big disappointment then.
Of course, my little world of self-interest pales in comparison to how this might improve the blockchain over time. A more robust chain is good for all.
There was never such on-chain mechanism, but it does not mean there can't be one on second layer. If you have a plan how it should work you could even create a proposal to finance implementation and make it yourself :o)