You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Users have expressed the desire to have IPC support delegated staking patterns, especially once for token-bound collateral is introduced (#1024). Given the right implementation of #1079, the core flows supporting delegated staking could live entirely in user/app-land, therefore requiring nothing else from IPC Core development.
Base flow:
Validator reward contract on the L1 acts as a management entrypoint for validators, collateral, and rewards. It transfers stake to the corresponding gateway actor.
Children subnets embed validator activity reports within every bottom-up checkpoint. These reports are rolled-up all the way up to the parent.
With every L2=>L1 checkpoint, the corresponding subnet actor relays validator activity reports to the validator reward for reward disbursement.
Delegated staking flow:
A delegating party turns up to the validator reward contract, deposits tokens as collateral, and delegates those tokens to specific validators.
On reward disbursement, the validator reward contract handles the apportionment of rewards between delegates and delegators, according to some contract-specific logic.
The text was updated successfully, but these errors were encountered:
Users have expressed the desire to have IPC support delegated staking patterns, especially once for token-bound collateral is introduced (#1024). Given the right implementation of #1079, the core flows supporting delegated staking could live entirely in user/app-land, therefore requiring nothing else from IPC Core development.
Base flow:
Delegated staking flow:
The text was updated successfully, but these errors were encountered: