Skip to main content
Binibit is migrating BINI from the legacy V1 contract to BINI V2 on Ethereum. The holder migration is coordinated through the Binibit platform. Treat the V2 contract below as the canonical Ethereum ERC-20 contract and the V1 contract as a legacy reference.

​
Live contract

​
Ethereum ERC-20 (current BINI V2)

​
Legacy contract

​
Ethereum ERC-20 (legacy BINI V1)

V1 remains listed here for historical verification and migration reconciliation. It is not the current canonical Ethereum BINI contract.

​
Migration notice

Binibit is migrating BINI from V1 to V2 on Ethereum. BINI V2 introduces a safer governance architecture, fixed supply, multisig Safe custody, and transparent token distribution across dedicated pools according to the public tokenomics and whitepaper. The Binibit team has updated the contract and explorer information in its CoinMarketCap Self-Reporting Dashboard. CoinMarketCap should verify the new V2 contract, mark V1 as the legacy contract, and display a migration notice on the BINI page. During the review period, aggregator pages may still display legacy V1 contract data. See BINI migration for the current holder notice.

​
BiniChain (native, mainnet)

The BiniChain mainnet rollout for native BINI is in the roadmap.

​
wBINI (wrapped BINI on BaiDEX)

wBINI lets BINI participate as one side of a Uniswap V3-style pool. Wrap and unwrap via the BaiDEX UI or directly via the wBINI contract. Address: see BaiDEX → Contract Addresses (publishes with PR-5).

​
How to verify a BINI address

  1. Search the contract address on a block explorer (Etherscan for Ethereum)
  2. Confirm token name = “Binibit” and symbol = “BINI”
  3. Confirm the contract is verified (source code published)
  4. Cross-check the address on at least one aggregator page (CoinGecko, CryptoRank, etc.)
If you encounter an address that claims to be current Ethereum BINI but does not match the canonical V2 address above, it is not the current official token. Report scams to support@binibit.com.

​
Cross-chain mechanism

The link between Ethereum ERC-20 BINI and BiniChain native BINI is the bridge — see BiniChain → Bridges when published. The bridge maintains the 1:1 peg between the two representations. Total supply across both chains never exceeds 1,000,000,000 BINI.

​
Governance and upgrades

The BINI V2 control plane uses dedicated roles and multisig Safe custody for production operations. The BiniChain native protocol is upgradable through validator governance, but the BINI supply rules and emission schedule are constants enforced at the protocol level. Major token or protocol changes will be:
  • Pre-announced 30 days in advance
  • Validated by an audit before deployment
  • Logged on-chain

Where to buy

Listed CEX venues

BiniChain

Where native BINI lives

BaiDEX

Where wBINI is used

Allocation

1B fixed supply