How to Unstake BSR

Note: Depending on which tier you are participating in, your BSR will be locked for a set period of time. Your tokens cannot be moved during this period.

Tier 1 — Lock Period 30 Days

Tier 2 — Lock Period 30 Days

Tier 3 — Lock Period 30 Days

Tier 4 — Lock Period 30 Days

Tier 5 — Lock Period 60 Days

Tier 6 — Lock Period 90 Days

Tier 7 — Lock Period 120 Days

Tier 8 — Lock Period 150 Days


1. Navigate to the BinStarter App found on this link https://bsr.binstarter.ai/. Click on "STAKE" from the main menu and then select "BSR STAKING."

2. From the staking section, click the “UnStake” button to proceed with the unStake process.  The lock period begins as soon as you click on the "UnStake" button. Once you have done this, the tokens will no longer be added to the Tier calculation for IDO allocations, but you will continue to receive staking rewards during the cool-down period. At the end of the lock period, you may claim your BSR back to your wallet.

3. Click "COOLDOWN" button to proceed.

4. The wallet confirmation pop-up will appear to confirm the approval of the cooldown. Review the transaction that you are about to make and click the “Confirm” button if everything is in order.

5. After confirming the transaction, the “COOLDOWN ACTIVE" button and the countdown for the lock period will appear on the screen.

  1. After the cooldown process is completed, you can withdraw your funds to your wallet using the "UnStake" button.

Canceling the Unstake Process

If you change your mind and want to join an IDO after initiating an unStake, you can cancel the unStake process anytime and reset the lock duration.

1. To cancel the unStake process, click the “CANCEL COOLDOWN” button shown when you click. This will undo the unStake process.

2. The wallet confirmation pop-up will appear to confirm the approval of the cooldown cancellation. Review the transaction that you are about to make and click the “Confirm” button if everything is in order.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.