How Bitborn actually works.
Every mechanic below is written, compiled, and tested before it ships. No promises without the code behind them.
"Built & tested" means exactly that: the code exists and has been verified. It goes live on-chain the moment the Genesis collection finishes minting, not before.
Network
Bitborn runs on Robinhood Chain mainnet.
| RPC | rpc.mainnet.chain.robinhood.com |
| Explorer | robinhoodchain.blockscout.com |
Motion
Every Bitborn keeps changing after mint, entirely on-chain. Each bloodline follows its own rule, permanently recorded as a trait.
Human, Motion: Mirror
Drifts in a continuous mirrored sweep. The baseline behavior, present on the majority of the collection.
Ape, Motion: Jump
A periodic crouch-and-leap cycle. Background stays fixed.
Alien, Motion: Static
The character itself doesn't move. Instead, the background evolves through a fixed 12-hour cycle: solid color, then a mosaic blend into the next color, alternating continuously across all 9 palette colors before looping.
Zombie, Motion: Mirror + Decay
Carries the same mirror sweep as Human, plus a second layer: loses one random pixel every 12 hours, regenerating fully once roughly 25% of its original pixels are gone. The cycle then restarts.
Staking
Soft staking. Your Bitborn never leaves your wallet. No lock-up, no custody transfer, ever.
Register, don't transfer
Staking a Bitborn records a timestamp on-chain. The NFT itself stays exactly where it is, in your wallet, tradeable at any moment.
The multiplier grows on its own
0 to 30 days: x1. 30 to 90 days: x1.5. 90 days and beyond: x2. No action needed, it's calculated from how long the piece has been staked continuously.
Selling resets it
Sell or transfer a staked Bitborn, and its pending rewards are forfeited, then redistributed to everyone still staking. The multiplier for that piece drops back to zero for its next owner.
Claim any time
No epochs, no waiting for a distribution date. Rewards accrue continuously as secondary sales happen, and are claimable the moment they're earned.
The reward-per-share accounting was rebuilt and tested end to end after switching from a locked to a soft model, including a rounding bug caught and fixed during testing before this was shipped.
Merge
Combine two Bitborn into a stronger one. Available any time, no staking required.
Pick a survivor and a sacrifice
Choose which of your two Bitborn stays, and which one you're willing to burn.
The survivor absorbs 50%
Half of the sacrificed piece's share weight transfers permanently to the survivor. The other half leaves circulation entirely.
The sacrifice is gone for good
Burned to a dead address, on-chain, irreversible.
Vault Drop
Once a month, one random Human quietly becomes the Vault. It only reveals itself under one condition.
One Human, chosen at random
Every cycle, a new Human becomes eligible. Nobody, including the team, knows in advance which one.
Staked for 30 straight days to reveal
Its owner has to be staking it, continuously, for the reveal animation to ever show. Otherwise it looks like any other Human.
Burn it to claim
Burning the piece while staked and revealed triggers the payout event. The pot is sent manually, once the on-chain burn is confirmed, rather than in the same transaction, to reduce attack surface on real funds.
Stops at a supply floor
The monthly cycle halts once total supply reaches 5,000, whether from Vault burns or Merge activity. At its own pace alone, that floor is effectively never reached, so expect a Vault most months.
Revenue Split
Every secondary sale splits automatically, the moment it happens.
Funded by trading activity, not by minting new tokens or diluting anything. If nobody trades, nothing flows. If the collection stays active, so does the treasury.
A wallet for every Bitborn
Each Bitborn has its own on-chain account, separate from your personal wallet but permanently tied to the NFT. Built on ERC-6551, an open Ethereum standard, not something proprietary to Bitborn.
Every piece gets its own address
The address is computed deterministically from the NFT contract and the token ID. It exists the moment the collection is deployed, whether or not anything has been sent to it yet.
Staking rewards land there, not in your personal wallet
WETH from secondary sales is paid directly to the Bitborn's own account. Only the current owner of the NFT can move it out, to their personal wallet or anywhere else.
Value travels with the piece
Sell the NFT before withdrawing, and whatever's sitting in its account, WETH, $BIT once it exists, goes to the new owner automatically. A Bitborn with a history of staking carries that history with it.
Visible on your profile
Connect your wallet on the site and your profile shows the combined balance across every Bitborn you hold, not just one piece at a time.
This changes where rewards are paid, not how they're earned. Staking mechanics, weights, and multipliers work exactly as described above.
Contract Addresses
Live mainnet addresses on Robinhood Chain. Filled in at deployment.
| Contract | Address |
|---|---|
| Bitborn NFT | TBD |
| BitbornStaking | TBD |
| BitbornShares | TBD |
| BitbornMerge | TBD |
| BitbornVaultJackpot | TBD |
| BitbornRevenueSplitter | TBD |
ABI Quick Reference
Key entry points for anyone integrating directly with the contracts.
| Contract | Function | Purpose |
|---|---|---|
| BitbornStaking | registerStake / unregisterStake | Declare or stop staking, no NFT transfer |
| BitbornStaking | claim | Pull accrued WETH rewards |
| BitbornStaking | refreshWeight | Lock in an upgraded duration multiplier |
| BitbornStaking | reclaimStaleStake | Free up a sold piece's stale registration |
| BitbornMerge | merge | Burn one piece, boost another's share |
| BitbornVaultJackpot | triggerVaultBurn | Claim the monthly pot by burning the Vault piece |
| BitbornVaultJackpot | isVaultPieceRevealed | Check this cycle's reveal status |
| BitbornRevenueSplitter | splitManually | Route incoming revenue 80/10/10 |
Security
A few principles we hold to across every contract in this system.
No private keys, ever, in any client-side code
Every claim, stake, and burn is signed by the holder's own wallet. Bitborn's contracts never hold a key that could move funds without the owner's signature.
Written, compiled, tested, in that order
Nothing here is described before it's built. Every mechanic above exists as compiled, tested code before it's documented on this page.
External audit before mainnet
Every contract handling real funds goes through independent review before deployment. This documentation reflects the design and testing, not a substitute for that audit.
Legal Disclaimer
Generic structure only. Every bracketed section below needs review by a qualified lawyer in the relevant jurisdiction before this page goes live.
No warranty
- This site and the underlying smart contracts are provided "as is" and "as available," without warranty of any kind, express or implied, including any warranty of merchantability, fitness for a particular purpose, non-infringement, or uninterrupted, error-free operation.
- Blockchain technology, smart contracts, and third-party infrastructure (including the underlying network, wallets, oracles, and marketplaces) carry inherent technical risk. By interacting with Bitborn, you accept that risk in full.
Limitation of liability
- To the fullest extent permitted by law, Bitborn and its founders, contributors, and affiliates are not liable for any direct, indirect, incidental, consequential, or punitive damages arising from your use of this site or the Bitborn smart contracts, including but not limited to: software bugs or vulnerabilities, smart contract exploits, network outages or congestion, attacks on the underlying blockchain network, third-party service failures (marketplaces, oracles, wallet providers), or loss of funds due to user error.
- Nothing in this documentation or on this site guarantees the security, availability, or correctness of any contract at any point in time. Independent audits reduce risk; they do not eliminate it.
- Events outside reasonable control, including but not limited to network attacks, chain reorganizations, validator or sequencer failures, and force majeure events, are expressly excluded from any liability.
Your responsibility
- You are solely responsible for the security of your own wallet, private keys, and seed phrase. Nobody from the Bitborn team will ever ask for them.
- You are solely responsible for verifying contract addresses and transaction details before signing. Transactions on-chain are irreversible.
- You are solely responsible for complying with the laws and regulations of your own jurisdiction, including any restrictions on prize draws, giveaways, or similar mechanisms where you reside.
Rewards, not investment
- Staking rewards and Vault Drop payouts are promotional rewards paid under the Bitborn ecosystem program to eligible holders. They are not dividends, not investment income, and holding a Bitborn grants no equity, ownership stake, or shareholder rights.
- This site is a user interface only. It lets you interact with permissionless smart contracts that live fully on-chain.
- Nothing on this site is financial, investment, legal, or tax advice, and nothing here is an offer or solicitation to buy or sell any security.
Indemnification
- By using this site, you agree that you, not Bitborn, are responsible for any claim or loss arising from your own use of the site or violation of these terms.
Operated by Bitborn. No formal legal entity is currently registered for this project.