Blind Bitcoin Intent Markets
Private BTC execution on Starknet, without leaking the trade before it lands.
Encrypt the order, store it at the gateway, commit it from the wallet, and let solvers compete on price after the intent is in the batch.
Public
Visible routing when speed matters more than concealment.
Hidden Amount
Hide order size while keeping the pair visible to solvers.
Max Privacy
Hide both size and direction until the execution path is ready.
BlindMarkets
How it works
Intent pair
BTC → USDC
Solver spread held until the batch closes.
Batch window
30 seconds
Wallet commit first, solver routing second.
Intent Composer
Execute with Privacy
From
To
Amount (base units)
Authorization comes from the connected wallet.
Deadline
Stored at gateway, committed with your wallet.
Connected Wallet
No Starknet wallet connected
Submission Mode
Gateway stores encrypted payload, wallet sends the on-chain commit.
Status Actions
Constraints
Privacy Mode
Estimated Execution
Wallet signature + on-chain commit + batch assignment
Total Cost
Wallet gas + solver fee ceiling 0.50%
Next Batch
⏱ —0% elapsed
Last Batch
No batch history yet.
Estimated Fill
⚠ This is an estimate.
Risk Disclosure
Bitcoin confirmations required before bridge release.
Intent History
Ciphertext First
The gateway receives encrypted payloads, not a plain order ticket.
Batch Auction
Orders collect inside short windows, then solvers compete on the filled route.
BTC-Focused Flow
Built for BTC pairs, bridge-aware settlement, and Starknet execution.
01
Encrypt and submit
Create the intent locally, encrypt it for the gateway, and store the ciphertext off-chain.
02
Commit from the wallet
The wallet sends the on-chain commit, so the user still controls the transaction boundary.
03
Clear and settle
After the batch closes, solvers compete and the settlement path is recorded for review.
Ready to route your BTC intent?
Connect the wallet, commit on-chain, and monitor the batch from one desk.