You are viewing a single comment's thread from:

RE: Direct RC delegations vs RC pools and tentative direct rc delegations spec

in #rc3 years ago

Direct RC delegations are super straightworward, just delegate 50 RC, your account now loses 50 max RC and the user you delegate to has an extra 50 max RC, I say max RC, because RC regenerates, so if the user you delegate to uses the 50 rc, it will come back eventually.

I think you want to do something similar to HP delegations where the receiving account gets not only max RC but current RC, and the delegating account needs to have unused current RC (which is deducted) to make the delegation.

You seemed to imply this when talking about the (important IMO) use case of users needing delegation because they used up all of their RC. This use case wouldn't be handled well if current RC doesn't transfer with the delegation because the receiver would need to wait for RC to charge up.

Sort:  

Sorry I didn't explain myself correctly, I just wanted to make the distinction that the rc delegated did regenerate and it wasn't a one-off, it's better explained in the technical spec, when you delegate you increase the user max and current rc.

And when you undelegate "regenned" RC delegation, does it come as MAX (unregenerated) RC or does it come with the extra vested value along?

As MAX (unregenerated) RC