Currently, the Staking app supports staking BTC (Babylon) and ETH (Beacon Chain) within MPC Wallets in Organization-Controlled Vaults.

Select the BTC or ETH tab to view specific instructions for each.

Babylon offers two methods to withdraw assets:

  • Early unstaking: You need to unstake (officially referred to as unbond by Babylon) first and then withdraw.
  • Natural expiration: You can directly withdraw your assets without the need to unstake first.

Follow these steps to unstake assets before expiraion.

Prerequisite 1: You have staked BTC in an MPC Wallet in an Organization-Controlled Vault. The wallet has not been moved out of Wallet Scopes accessible by Staking.
Prerequisite 2: You need to have the Staker role to unstake assets.
  1. Click the Apps icon on Cobo Portal, find Staking, then click Open to open Staking.

  2. Click View under Actions in the row for Babylon.

  3. On the staking details page, click Unstake under Actions in the row of the staking position that you want to unstake.

    • The Unstake button appears only in the rows of the staking positions with the status Active or Limit exceeded.
    • For Babylon, you can only unstake the whole amount; partial unstaking is not allowed.
  4. Review the information in the pop-up window and click Submit. Note that the Babylon protocol does not support customizing your fee rate for unstaking. You need to have sufficient balance for the network fee to submit the transaction.

  5. In the Unstaking Request Submitted window, click Staking Activity to go to the staking details page.

  6. On the staking details page, you can find the following updates.

    • Under Staking Positions, the Position Status is updated to Unstaking in Progress.
      • If the unstaking succeeds, the Position Status will become Withdrawable, and a Withdraw button will appear under Actions.
      • If the unstaking fails, the Position Status will change back to Active, and the Unstake button will appear under Actions.
    • Under Activity, a record is created, and its Activity Status is Processing. If the unstaking request is rejected by risk control policies or signers, the status will be Failed; otherwise, it stays as Processing. Depending on whether Babylon confirms the transaction, the final status will be Success or Failed.