The live protocol on Solana mainnet, from your own wallet. Every transaction is built in this tab and signed by you; there is no server between you and the chain, and the price is posted in the same transaction as the trade. Program 1oooxLtzLiYV6LcDybrEPcyXVLPWGnAmeif9s5oNrp6.
Walletmainnet
One-click trading
Connect a wallet to turn this on.
Waiting for a price and the market.
Approve quickly. The price is posted in the same transaction and the market accepts one no more than a moment old, so a slow approval loses the race. A lost race moves no money and is retried automatically with a fresh price.
Marketno quote
BTC · price2 min · composite 4 Hz · anchor 5 s · cannot settle
Open a position and your entry is drawn here, with the barrier and the take-profit, while the price keeps moving against them.
free public-exchange composite — display only. It settles nothing. Your position is judged on the signed Switchboard quote inside the transaction — never this line, and never the anchor. The anchor is that same feed sampled every 5 s through crossbar /simulate, unsigned, and it is the only one of the two that tracks what settles.
Your positions0 live
Connect a wallet to read your book.
Live P&L — open positionsno wallet connected
Connect a wallet to see what your open positions are worth.
How your closed trades performedno wallet connected
Connect a wallet to see how your finished trades performed.
Closed tradesnot read yet
Connect a wallet to read your finished trades.
Where these rows come from — a settled position no longer exists on chain
These rows are not read from an account. settle frees the slot and the next open writes over it, so every closed trade above was rebuilt from the SettlementPriced event in the transaction that closed it, with the SDK's settlement engine re-run over each one and all five money columns checked against what the chain emitted. The entry price, the exit price, the rung and the money are on the event; the stake, the side, the tier and the split between the loss tax and the exit fee are recovered, and a row that could not be recovered says so rather than guessing.
Before you open — every gate the chain appliesno take-profit, so the rung rows are judged at the payout cap — that row sits ON its limit by construction, not near it
Connect a wallet and wait for a price. The gates are the chain's own refusals, in the order the program applies them.
Fine print — priority fee, retries, timer, and what is not verified
These change what is sent. Each one is here because it changes whether a transaction lands inside the price freshness window, not because it is a preference.
packages/sdk and are the same ones scripts/send.ts landed on mainnet; the wallet signature path and the measured slot distance are what only a real Phantom approval can answer.