Contracts & Addresses
BSC deployment addresses have not been supplied for this documentation revision. No placeholder below is an address that can receive funds. The migration specification targets BSC mainnet, chain ID 56.
BSC Mainnet — Registry Pending
| Component | Address | Role |
|---|---|---|
| AuctionFactory | Pending publication | Registers projects and deploys rounds. |
| AuctionRound | Pending publication | BNB-denominated deposit accounting and clearing. |
| Settlement | Pending publication | Merkle commitments and token/BNB claim rights. |
| CanonicalLPFactory | Pending publication | Creates Project Token/WBNB pools. |
| StakingPool | Pending publication | Project-isolated reward buckets. |
| FeeRouter | Pending publication | Existing project-type fee shares. |
| BuybackVault | Pending publication | JUMP buyback and burn routing. |
| JumpReserveVault | Pending publication | Receives operations share. |
| WBNB / Stock Tokens / DEX router | Pending approved asset and route list | Verify BSC token and router identities before enabling conversion. |
Publishing a Verified Deployment
For each released component, publish its BSC address and BscScan verification link, source repository, tagged commit, compiler settings and deployment transaction. Compare runtime bytecode and initialized parameters with the released build. No source verification, proxy status or audit coverage is claimed here until that evidence is attached.
Implementation Requirements
The specified round parameters and activated settlement commitments must remain immutable under the documented rules. A revised mechanism requires an explicitly versioned deployment. Actual upgrade and access-control properties must be checked against the released BSC contracts.