Connect a wallet
Canary runs in your browser and signs with your own Solana wallet. The app never holds your keys: it prepares each transaction, your wallet shows it and signs it, and the app sends the signed transaction to the network.
Supported wallets
Any browser wallet that supports the Solana wallet standard appears in the list: Phantom, Solflare and Backpack are the common ones. Hardware wallets that need a USB connection are not supported.
- Open the app and choose Connect wallet in the top right.
- Pick your wallet from the list and approve the connection in the wallet.
- The button now shows your address. Open it to see your SOL and USDC balances, copy your address or disconnect.
Your wallet only signs. The app sends every signed transaction to Canary's own network (mainnet for the live service), so the network your wallet is set to doesn't change where a transaction goes. The wallet panel shows that network.
What you need
| Asset | For |
|---|---|
| SOL | Network fees and the rent of the accounts your first actions create (a token account for YES and NO, a vault, a receipt). A few hundredths of a SOL covers most use. |
| USDC | Bounty deposits and market collateral. Canary's markets and bounties settle in USDC only. |
Signing
Most actions are one transaction and one approval. A few are several transactions that the wallet approves together, and the app then sends in order, each confirmed before the next:
| Action | Transactions |
|---|---|
| Fund a bounty, mint or merge pairs, redeem | 1 |
| Create a Q-Vault and confirm its Falcon-512 key | 8 |
| Spend from a Q-Vault with the Falcon-512 key | 4 |
| Claim a Q-rung | 13 to 17, depending on the rung |
| Claim a terminal rung (T-256k, T-255e) | 1 |
Each transaction in a set carries a distinct memo, so a wallet that signs several at once never produces two identical ones. Your wallet may add its own safety instructions when it signs; the app leaves room for them.
After you sign
The app shows each step in place: building, signing, sending, and Confirmed with the transaction signature. Your balances, receipts, positions and vaults refresh within a few seconds of the confirmation.
If a set of transactions is interrupted (you close the tab, or the network drops one), check the page's lists for what already landed before you try again. Registering a vault's key resumes from the chunks already written; a claim starts again with a new job.