Allstake withdrawals
· updatedAllstake’s documented architecture provides withdrawal functionality through client contracts on networks such as Ethereum and Solana. Assets are withdrawn on the relevant client chain, while the Allstake Hub on NEAR tracks withdrawal states alongside deposit and delegation states.
Undelegation and withdrawal
The Allstake Hub can initiate Chain Signature transactions to perform undelegation on client chains. Allstake’s Technical Architecture describes this capability separately from client-contract withdrawals. It does not specify whether a particular asset must be undelegated before withdrawal, or establish that undelegation alone completes an asset exit.
Operator delegation and withdrawal tracking therefore answer different questions: which operator receives an allocation, and what withdrawal state the Hub records. The architecture does not provide an asset-specific sequence connecting those operations.
Bitcoin implementation
Bitcoin restaking has a separate implementation described around Chain Signature-based logic. The Ethereum and Solana client-contract description does not supply the procedure or completion conditions for a BTC exit.
Waiting periods, fees, and limits
Allstake’s Technical Architecture and Modules descriptions do not specify a withdrawal waiting period, withdrawal fee, or minimum or maximum withdrawal amount. They also do not define position-specific eligibility or the status that establishes completion. Those descriptions do not establish a settlement deadline or confirmed withdrawable amount for an individual position.
Withdrawal decision checklist
- For a position on Ethereum or Solana, match the withdrawal terms to the asset and the client chain where it is restaked.
- For a Bitcoin position, establish the applicable Chain Signature-based exit procedure before relying on instructions written for client contracts.
- If the position’s eligibility, timing, fees, or completion conditions remain unspecified, resolve those details before initiating a withdrawal.