Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.binibit.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Three bridges total

BridgeWhat it movesDirectionRatioLevel gate
Bridge ACrystals (CRS) ↔ USBIOff-chain ↔ BiniChain ERC-2010,000 : 1Level 5
Bridge BBINI off-chain ↔ BINI nativeOff-chain ↔ BiniChain native1 : 1Level 7
Cross-chain bridgeERC-20 BINI ↔ native BINIEthereum ↔ BiniChain1 : 1None (standard)
Bridge A and B are off-chain ↔ on-chain (within the Binibit ecosystem). The cross-chain bridge connects BiniChain to Ethereum.

​
Bridge A — CRS to USBI

Detail: Tokenomics → USBI Bridge, Bini App → USBI Bridge. Summary:
  • Convert off-chain Crystals (CRS) earned in Bini App into on-chain USBI ERC-20
  • Fixed rate: 10,000 CRS = 1 USBI
  • Gated at Level 5 (50M XP)
  • USBI used in BaiDEX pools as LP
The Bridge A contract on BiniChain mints USBI when off-chain CRS is consumed. The Bini App backend signs the redemption request; the contract verifies and mints.

​
Bridge B — BINI off-chain to native

Detail: Tokenomics → BINI Bridge, Bini App → BINI Bridge. Summary:
  • Convert off-chain BINI rewards (quest wins, lottery, grants) into native BINI on BiniChain
  • Fixed 1:1 ratio
  • Gated at Level 7 (105M XP)
  • Native BINI used for gas, staking (after withdrawal to Ethereum), pool participation
The Bridge B contract on BiniChain transfers native BINI from the Rewards pool reserve when off-chain BINI is consumed. The Bini App backend signs; the contract verifies and transfers.

​
Cross-chain bridge — Ethereum ↔ BiniChain

For users moving BINI between Ethereum (ERC-20) and BiniChain (native): 
ERC-20 BINI on Ethereum  ←→  Native BINI on BiniChain  (1:1)
Mechanism (TBD pending team finalization):
  • Lock-and-mint: lock BINI on origin chain, mint on destination
  • Burn-and-mint: burn on origin, mint on destination (more capital-efficient but trusts the bridge contracts)
The exact mechanism + bridge contract addresses publish before mainnet. For now, the canonical path for cross-chain users is via Binibit Exchange (which handles the bridge as part of withdrawals).

​
Anti-sybil

Bridges B and A both have anti-sybil designs:
BridgeAnti-sybil mechanism
Bridge A (CRS→USBI)Level 5 gate + USBI entitlement cap (max 101K USBI per user)
Bridge B (BINI off→native)Level 7 gate + monthly cap (TBD value) + per-account fraud detection
Cross-chainStandard signature verification + nonce + replay protection
The L7 gate on Bridge B is intentionally high — BINI is real-value, so the gate has to filter out farm accounts.

​
Bridge security

All bridges are smart contracts with:
  • Audited code (audit firm TBD pre-mainnet)
  • Multi-sig admin (no single key controls minting/locking)
  • Emergency pause (can halt withdrawals if exploit detected)
  • Time-delayed governance for parameter changes
  • On-chain logs for every action
The bridge contracts custody real BINI (in the lock-and-mint case). Bridge security is the most critical security concern in the ecosystem.

​
Failure modes

ScenarioWhat happens
Bridge contract has a bugEmergency pause; users wait for fix; no funds lost from contract
Bridge admin keys compromisedMulti-sig requires multiple keys; mitigates single-key compromise
Cross-chain message lostReplay protection ensures no double-spend; users can retry
Off-chain backend (Bini App) compromisedBridge contract verifies signatures cryptographically — backend can’t mint without valid sigs

USBI Bridge (Tokenomics)

Bridge A formula

BINI Bridge (Tokenomics)

Bridge B formula

Bini App / Bridges

User-facing bridge UX

BINI Token

What native BINI is for