Docs / Reference
Wallet troubleshooting and recovery
Which wallets work, what a declined or expired transaction means, and how a pending transaction is recovered after a reload.
which wallets work
Your wallet must return a signed transaction and must support version 0 transactions, which the launch needs for its address lookup table. Wallets that can only sign and send in one step are not listed: the client insists on receiving back the transaction it simulated, allowing only appended read-only safety assertions. §8.3
A wallet is an authorization key, not an identity. Nothing on Core is stored against it, and switching wallets switches positions. §8.4
what each outcome means
- 01
declined in wallet
Nothing was sent. The transaction dock shows the decline; retry from the same control.
- 02
tab closed mid-transaction
A signed transaction is recorded in durable browser storage before it is broadcast. On reload the dock recovers it and checks its status on chain. It is never sent twice.
- 03
unknown status
If the network did not answer in time, the dock holds the signature and offers a recheck that reads chain status without asking for another signature. Do not submit again until it resolves.
- 04
expired blockhash
The transaction never landed. Build and sign it again; nothing moved.
- 05
insufficient SOL
A launch needs the fees, the pool SOL and rent in the wallet before signing. The form states the shortfall rather than letting the transaction fail at the wallet.
reading a simulation error
The program returns named errors. A fee ceiling failure, for example, reads like this and means the live platform fee rose above the maximum your transaction signed for. §8.2
Simulation failed: custom program error 0x1771
live platform fee exceeds the user-signed maximumthis page expands
- 8.2The wallet cannot change what a transaction does
- 8.3Wallets that cannot return a signed transaction are not offered
- 8.4A wallet is an authorization key, not an identity
The paper is the authority. Where this page and §8.2 disagree, the paper is right and this page is a bug.