Staking as Control Plane
This lens is for systems where staking, delegation, validator registration, or restaked collateral becomes the real authority surface.
Questions worth asking:
- Who can stake, delegate, or register operators, and who decides admission?
- Does stake decide who can issue commitments, route orderflow, sequence transactions, or collect rents?
- Are slashing and freeze rights actually live, or mostly roadmap theater?
- Is the advertised staking layer really a protocol rail, or just a wrapper around one gateway, sidecar, relay set, or validator menu?
- Which custody, portal, or treasury workflow decides where stake can actually go after the depositor says
yes?
Curated comparison set
- Validator-edge packaging where stake becomes service rights: mev-boost and puffer-preconf
- Shared-security rails where admission and delegated collateral matter more than the app story: babylon and symbiotic
- Distributed-validator coordination when the operator set is the real object: obol and ssv-network
- Institutional staking wrappers where custody and operator menus decide what can actually happen: liquid-collective and fireblocks
Reading rule
Do not stop at the staking contract. The real choke point is usually one layer over: operator admission, delegation policy, validator clustering, custody approvals, or the menu that decides which staking path a depositor can actually reach.