Live on BOT Chain · Chain ID 677
Say what you want to swap.
Let the chain remember it.
CrossBiDex is a single immutable registry where you publish cross-chain swap intents on-chain — source, destination, amounts, deadline — and confirm settlement yourself. No bridge contract. No order book server. No custodian ever touches your funds.
Why this exists
Bridges lock. Order books hide. Intents just sit on-chain.
- Custodial bridges concentrate risk by locking and minting synthetic assets.
- Most intent-based swap systems store orders on a centralized server, open to censorship or front-running.
- BOT Chain has no native, auditable primitive for cross-chain swap intent — until now.
- Unfilled orders rarely carry an on-chain guarantee that they'll expire.
What CrossBiDex does
One contract. Full visibility. Zero custody.
- Publish a bidirectional intent — BOT Chain out, or BOT Chain in — with explicit source and destination chain IDs.
- Every intent carries a real deadline, so stale orders can be identified and treated as expired automatically.
- Only the maker can cancel or confirm their own intent. There is no admin key and nothing to upgrade.
- Anyone can query intents by ID or by maker address, straight from the chain.
The workflow
From intent to settlement, in four steps
-
1
Create an intent
Set your source chain, destination chain, tokenIn, tokenOut, amount, minimum acceptable output, recipient, and a deadline. It's written to the registry in one transaction.
-
2
A solver fills it
Solvers watch the registry off-chain and deliver tokenOut to your recipient address on the destination chain — outside this contract, on the chain where the tokens live.
-
3
You confirm settlement
Once you've received your tokens, you confirm the fill and record the solver's address. Only the maker can do this, and only before the deadline.
-
4
Or cancel any time
If nobody's filled it yet, cancel your own open intent whenever you like. Past the deadline, unfilled intents simply read as Expired.
The application
Your intents, straight from BOT Chain
Connect your wallet to get started
Create intents, track their status, cancel or confirm fills — all signed directly by your own wallet. Nothing is stored off-chain.
You're on the wrong network. CrossBiDex lives on BOT Chain (Chain ID 677).
Connect and this will fill with your on-chain intents.
Built to be checked, not trusted
Four guarantees, enforced by code
No custody
The registry only records intent. It never holds, locks, or routes your tokens.
No admin key
There's no privileged role. Only a maker can cancel or confirm their own intent.
Immutable
No proxy, no upgradeability. The bytecode you audit today is what runs tomorrow.
Auto-expiry
Read an intent past its deadline and it reports Expired — no one can misrepresent a stale order as open.
Where this is headed
Roadmap
- Q3 2026 Whitepaper release Completed
- Q3 2026 Contract development & testing In progress
- Q4 2026 Mainnet deployment on BOT Chain Planned
- Q4 2026 Frontend dApp launch Planned
- Q1 2027 Solver reputation module Planned
- Q1 2027 Integration with BDEX & BOT Bridge Planned
Questions
Frequently asked
No. The contract is a registry only — it stores the details of your intent (chains, tokens, amounts, deadline) but never takes custody of tokenIn or tokenOut. Actual token movement happens between you and a solver, outside this contract.
Anyone watching the registry can act as a solver and deliver tokenOut to your recipient address on the destination chain. You then confirm the fill yourself by calling confirmFilled with that solver's address — nothing settles without your say-so.
It simply reads as Expired once the deadline passes, as long as it's still Open. You can also cancel it yourself at any point before it's filled.
Any EVM-compatible injected wallet: MetaMask, Bitget Wallet, OKX Wallet, TokenPocket, and others. CrossBiDex automatically detects every wallet extension you have installed and lets you pick which one to use.
No. There is no protocol token. Every action — creating, cancelling, or confirming an intent — is a simple state change paid for in BOT, the native coin of BOT Chain, typically for well under a cent.
No. There's no proxy pattern and no admin role. The contract deployed on BOT Chain is immutable, so the logic you review is the logic that will always run.