Today I'd like to suggest both HP and RC delegations expire after x amount of time by default.
There are several instances of active accounts benefiting from inactive account delegations from years ago. Not cool.
Same thing will happen with RC. Not cool.
That's only one problem I see.
Your thoughts? Anyone else care to chime in?
Hmmm, while I see the use case, we don't like to add time-based event too much because they cause load on the chain. This would be something could be automated through an L2 (for RC, HP requires an active key which is no go).
As for the HP I'm like, why is it a problem ? People are free to do what they wish with their stake, if they wish to delegate then go MIA well it's their choice. It was bad for governance votes because it directly affects things like witness rankings or proposals but for delegations it has a lower impact (if you want to mention people self voting and such, I'd say abuse can be countered with free downvotes or by various initiatives)
I hear you. People are most certainly free to make choices. Until they die or lose their keys. And sure, one could simply downvote. That always goes well...
I appreciate your thoughts on this matter.
Keep up the good work. It's appreciated.
Well the same was done for witness vote to expire if account is not active for kore than one year... so this will be an extension of it
Yes. That's how I imagined it. Wouldn't be hard to renew delegations before the time expires if needed, especially if the frontend somehow highlights which ones need attention. Just requires user input, like voting for witnesses.
Plugs up all the leaks.
From the technical standpoint something that stays up potentially forever is worse than something with definite lifetime (because the former can build up over time). That supports the idea of expiration.
From usability point of view I can see potential problem. Now you can set two accounts - one as cold storage, second as active. You set your active as proxy for cold storage, you delegate all HP from cold to active and you are good to go, never to have to touch the cold storage (well, until renewal of proxy setting once a year).
Back to technical side. It would require additional index on delegation objects, so it is not only pluses in that field.
I think we'd need to see what is average effective lifetime of delegation (with and without weighting it by its power) - maybe it is not such big of a problem after all?
At this point, I just wanted to throw the idea out there and see what people think. Certainly don't want to burden anyone or suggest bogging performance.
I see your potential problem and would counter it by delegating renewal rights from cold to active. Easier said than done. I know...
And I'm not really looking at it like it's a major issue, I just know it could turn into one. There are little pockets everywhere; seemingly forgotten delegations. And even being small I view as a problem because that just adds to the total of wasted resources. Similar to shrinkage, in a sense. Especially problematic in the long run, and if price goes up.
Handing out RC, set it and forget it. Incentive to powerup; set that and forget that too. Not a fan of the free ride.
Any single one of these little 'projects' springing up asking for delegation could stop paying out whenever they feel like it. Meanwhile inactive account doesn't notice for two years, passes away, or loses keys. That little project becomes a parasite, forever. Ill-gotten gains.
Again, I don't want to convince anyone it's a problem that needs an immediate solution. Just something not worth ignoring completely. Unfortunately I don't know a damn thing about what's under the hood of the blockchain. I just drive the damn thing and want it to be running efficiently.
Second.