Stake Abstraction Sits in the Docs Under a Name That Hides What It Does
found this on the sidebar under Protocol Capabilities, filed next to Digital Identity, and almost walked past it a third time.
stake abstraction. also referred to as hyperstaking in the URL, which is the more marketable name and less descriptive one.
heres the problem it addresses. running a provisioner node means operating infrastructure. uptime, upgrades, monitoring, and a slashing risk if you get it wrong — theres a whole RECOVERY guide for when people do.
most holders will never do that. so the staked share of supply ends up concentrated among people who can run servers, which is a smaller and more technical group than the set of people who hold the token.
abstraction separates the capital from the operation. you can contribute stake without personally being the one keeping a machine alive at 3am.
what that does to network security is genuinely two-sided and I dont think theres a clean answer. more stake participating means a higher cost to attack, which is good. but delegation historically concentrates around a few large operators, because people pick whoever is biggest and most visible, and that concentration is exactly what proof-of-stake was supposed to avoid.
so it widens participation in the capital and narrows it in the OPERATION. those pull opposite directions and which one dominates depends on how many operators there end up being, not on the design itself.
I havent read the full page yet, only the overview, so take this as a first pass rather than a verdict.
#dusk @Dusk $DUSK
found this on the sidebar under Protocol Capabilities, filed next to Digital Identity, and almost walked past it a third time.
stake abstraction. also referred to as hyperstaking in the URL, which is the more marketable name and less descriptive one.
heres the problem it addresses. running a provisioner node means operating infrastructure. uptime, upgrades, monitoring, and a slashing risk if you get it wrong — theres a whole RECOVERY guide for when people do.
most holders will never do that. so the staked share of supply ends up concentrated among people who can run servers, which is a smaller and more technical group than the set of people who hold the token.
abstraction separates the capital from the operation. you can contribute stake without personally being the one keeping a machine alive at 3am.
what that does to network security is genuinely two-sided and I dont think theres a clean answer. more stake participating means a higher cost to attack, which is good. but delegation historically concentrates around a few large operators, because people pick whoever is biggest and most visible, and that concentration is exactly what proof-of-stake was supposed to avoid.
so it widens participation in the capital and narrows it in the OPERATION. those pull opposite directions and which one dominates depends on how many operators there end up being, not on the design itself.
I havent read the full page yet, only the overview, so take this as a first pass rather than a verdict.
#dusk @Dusk $DUSK