Wallet connection and privacy
Connecting lets Qart ask your wallet to do something. Your wallet holds your keys and controls each approval. Connecting alone does not give Qart permission to spend.
Updated 31 October 2026.
When Qart connects to your wallet
Qart uses the Wallet Application Interface (BRC-100). It tries a wallet in your browser first. To find a desktop wallet, your browser may ask for access to apps on this computer. That browser permission is broader than wallet access; Qart uses it only for wallet discovery and wallet requests you initiate. It does not approve a payment or share your identity by itself.
You can decline and keep using features that do not need a wallet. If browser access is blocked, check this site's permissions beside the address bar, use a browser wallet, or open this site inside your wallet's browser. Qart does not currently offer remote phone pairing.
| Feature | Request | What Qart keeps |
|---|---|---|
| Sign in or link an identity | Public identity key and a signature over a one-time challenge. | Public key, derived identity identifier and the account it belongs to; challenge/proof data for verification and the resulting session. |
| Choose a receiving address | Network and a public receiving key. | The receiving address and network used by the shop or order. |
| Pay or add funds | Network and a payment action naming its amount, destination and description. | Transaction ID, payment destination, amount and order or wallet records. For BSV, the connected wallet chooses inputs and signs. |
| Show a membership item | Items from the relevant basket, their key instructions, and a signature proving control. | The presented item, its public ownership proof and the resulting membership/session record. |
| Link an on-chain identity record | Public identity keys, signatures and the matching record in the identity basket. | Public identity record and signatures used to verify it. |
Sign-in uses the wallet's public identity key. Other apps requesting that same key can recognise the same wallet. Qart deliberately uses that shared identity for portability; it is not a separate private identity for this site. You can use email sign-in instead.
Qart asks when you use a feature. It does not request an automatic spending allowance, identity certificates, key-linkage disclosure or your unrelated transaction history. The connected-wallet path does not ask for your seed phrase or private key. Qart does not launch an autonomous agent through this connection.
Methods, protocols and baskets
Direct requests: getVersion, waitForAuthentication, getNetwork, getPublicKey, createSignature,
createAction
and listOutputs.
Sign-in: [2, "message signing"], counterparty anyone, a fresh key ID
and a BRC-77 envelope. Receiving: [0, "onesat"], key ID 1sat 0.
On-chain identity: [1, "sigma"], key ID identity-0.
Membership items use their stored derivation instructions in the 1sat
basket;
identity records use the bap
basket. Payment actions carry qart
labels.
A wallet may show its own permission prompts. Qart's manifest describes its sign-in protocol; it grants no spending authority. An embedded merchant checkout calls the wallet as that merchant site's domain, so the wallet should identify the merchant as the requester.
Three questions, answered
- Who could stop this?
- Your wallet decides each request, and you can decline any of them. Whoever runs this Qart instance can stop offering a feature. Once a payment is broadcast, no one can stop or reverse it.
- Who can see this, and for how long?
- Payments are public on the chain, for good. Your identity key is shared with every app that asks your wallet for it. What Qart keeps is in the table above, held by whoever runs this instance.
- What happens if I lose my key?
- Your connected wallet holds the keys, so its recovery phrase is the way back. Qart never has those keys, so it can't recover them for you.
If a request stops
A connection error does not prove that a wallet is missing. A payment timeout does not prove that nothing was sent. If the result is unknown, Qart asks you to check your wallet or order before sending again. Technical details stay under Details. Qart does not automatically resend an uncertain payment or repeat a request your wallet declined.
When you use a wallet managed in Qart
This is separate from connecting an external wallet. A hosted wallet or a key imported into Qart is stored encrypted on the server; Qart can decrypt it to sign the operations you request. A watch-only wallet holds public information. A browser-held key signs in your browser and is stored there in wrapped form; scripts running on the page remain part of its trust boundary.
Qart stores wallet, address, output and transaction records for these wallets. Keep a copy of your seed phrase or imported key and the wallet's derivation information; a complete recovery can also require wallet records. Qart's wallet screens are not currently a BRC-100 provider for other sites. External-wallet permission grants are reviewed and revoked in that external wallet; browser access is managed in browser site settings.