Staking and Unstaking with Ike
How to Stake, Un-stake, and earn yield with Ike
Last updated
How to Stake, Un-stake, and earn yield with Ike
Last updated
When a user stakes tokens with the Ike protocol, the experience is as follows:
User initiates a stake
transaction with the contract, in which they submit AZERO tokens to the Vault
.
User receives sA0 from the Vault
. The amount received depends on the current Redemption Ratio
, which can be readily seen on the Ike dApp.
sA0 tokens are fungible, and can be traded on or used as a proxy for AZERO in other activities on the blockchain, such as DeFi applications, Gaming, NFTs, and more.
When AZERO tokens are staked with Ike, they are transferred to the contract. The Vault handles the rest of the process behind the scenes, including:
generating the new sA0 tokens and transferring them to the user, and
making sure the user's AZERO tokens make it downstream to for staking on the network.
For more technical information on how staking works behind the scenes, see Ike's docs on the .
Users can redeem AZERO from the Vault
in exchange for submitting sA0 to the Vault
. The number of AZERO received depends on the Redemption Ratio at that time, with respect to the number of sA0 they submit for redemption.
It's important to note that when using Liquid Staking, there will be a delay between the time that a user requests to unstake AZERO and when they actually receive them to their wallet. There are a few reasons for this, including native unstaking delays built into, and enforced by, the blockchain itself. The user experience is as follows:
Redemption: Once the Cooldown Period is over, the user can redeem their AZERO tokens to their wallet.
Initiation: User executes an unstaking request by making a call to the Vault. When they call this function, they specify either how many sA0 they'd like to submit, or how many AZERO they'd like to receive.
Cooldown Period: Once the unbonding request is sent to the Validators, the users must wait for the . This is enforced by the blockchain itself, and there is no way around it.
For more detailed technical information on how this process works, see Ike's docs on the .