Allstake
Allstake: Solana LST Delegation
· updatedAllstake is a multichain staking and restaking protocol. In its documented NEAR-Solana architecture, the Solana Delegation Manager lets restakers delegate liquid staking tokens (LSTs) on Solana to operators registered on the NEAR-based Allstake Hub. Client contracts handle the Solana delegation, while the Hub coordinates service and operator registrations.
Which modules handle deposits and operator delegation?
Solana’s Strategy Manager accepts deposits and stakes native LSTs. Allstake’s Modules documentation names mSOL as an example. The Hub’s Strategy Manager tracks deposit and stake states across chains; the Solana Delegation Manager handles delegation of restaked LSTs to Hub-registered operators.
The Hub’s Delegation Manager registers operators for actively validated services (AVSs) and application chains, and allows restakers to delegate to operators. Developers register their AVS or application chain through the Hub’s AVS/App chain Directory. Service registration, operator registration, and a restaker’s delegation therefore have separate roles in the architecture.
How does delegation state pass between Solana and NEAR?
State from Solana’s Strategy Manager and Delegation Manager is relayed to Light Clients on NEAR. Connector contracts on NEAR make that state accessible. In the other direction, Chain Signature enables the Hub to synchronize AVS, application-chain, and operator registration state to Solana.
An AVS’s Stake Registry can read delegation shares from the Delegation Managers on both NEAR and Solana. This allows the service to use restaked assets from both networks. Each AVS selects its combination of chains and assets, so the applicable asset selection remains part of that service’s security configuration.
Does a NEAR-registered operator require bridging mSOL to NEAR?
Allstake’s native restaking design allows Solana assets to participate without bridging them to the Hub’s network. For this hypothetical example, assume an AVS accepts mSOL on Solana, its selected operator is registered for that AVS on Allstake Hub, and a restaker has restaked and delegated mSOL through the Solana client contracts.
The delegation is handled by the Solana Delegation Manager. Once its state is relayed to NEAR, Connector contracts make that state accessible, and the AVS’s Stake Registry can read the Solana delegation shares. The resulting relationship combines a Solana asset and delegation with an operator registration maintained on NEAR. The mSOL does not need to become a NEAR-based asset for the AVS to use those shares; this example depends on the stated asset acceptance and operator registration.
How are rewards and slashing connected to delegation?
The Hub’s Payment Coordinator distributes rewards to operators and restakers based on operator performance and delegation amount. Its Slasher handles operator slashing for underperformance according to the network’s performance evaluation criteria.
Solana’s Operator Manager manages slashing and reward distribution to delegators on Solana. Chain Signature enables the Hub to initiate these actions on the client chain, connecting the Hub’s coordination role with the contracts that handle the Solana position.