Skip to main content
All CollectionsAnnouncementLatest News
BIT will support Ethereum (ETH) London hard fork
BIT will support Ethereum (ETH) London hard fork
Updated over a week ago

Dear BIT users:

Ethereum (ETH) network will undergo a London hard fork upgrade at block height 12,965,000 (expected on August 5, 2021 at 11:55 UTC time).

This hard fork may generate new tokens. Therefore, in order to reduce the trading risk due to market volatility during the hard fork, BIT will make the following arrangements:

1. ETH deposits and withdrawals

To support this upgrade, BIT will suspend the deposits and withdrawals of ETH and ERC-20 tokens at 11:00 am on August 5, 2021(UTC). Please make deposits and withdrawals in time. BIT will handle any technical issues during the hard fork for you.

2. Regarding ETH hard fork

If no new tokens are generated after the hard fork, BIT will resume the deposit and withdrawal services of ETH and ERC-20 tokens as soon as possible.

If new tokens are generated after the hard fork, BIT will credit users with ETH from the chain with the most work done and will take a snapshot of ETH holders at a block height of 12,965,000 (i.e. at approximately 11:55 am UTC time on August 5, 2021, and airdrop the new tokens to ETH holders at a ratio of 1:1. The airdrop will be distributed to your BIT account and a new announcement will be made when the distribution is completed.

3. ETH trading services

Spot trading: The spot trading service of ETH and ERC-20 tokens will not be affected.

Futures trading: ETHUSD perpetual trading service will not be affected.

Options trading: ETHUSD options trading service will not be affected.

The hard fork may be accompanied by more violent price fluctuations. Please reduce the risk of forced liquidation by reducing your position, closing your position, lowering your leverage, or turning on margin call functions in advance.

BIT will continue to protect your assets and help you deal with the fork, and we appreciate your continuous support.

BIT Team

August 3, 2021

Did this answer your question?