Using the app
Wallets and transactions
Which wallets work with Plumb, what you are asked to sign, and how a transaction travels from the button to the chain.
Wallets
The app connects to any wallet that supports Wallet Standard, the common interface Solana wallets register in the browser. That includes Phantom, Solflare and Backpack. Wallets appear in the list as soon as they register; there is nothing to install on Plumb's side.
The app doesn't include adapters for hardware wallets connected over USB.
The app remembers which wallet you used last and reconnects quietly when you come back. Disconnect in the wallet menu forgets it.
What you sign
You only ever sign one kind of request: a Solana transaction that calls the Plumb program, built for exactly the action you chose. The app never asks you to sign a message, never asks for a token approval or delegation, and never holds a key.
Your wallet shows the transaction before you approve it. Plumb transactions also carry two compute-budget instructions: Plumb's program needs a larger memory heap than the default, and liquidations and stability-pool actions need more compute.
From button to chain
- Build. The app sends the action and its amounts to the Plumb API, which builds the transaction against the chain's current state, including any token account you are missing.
- Simulate. The API runs the transaction against the chain before anyone signs. If the program would reject it, you see the reason in a sentence and your wallet is never opened.
- Sign. Your wallet shows the transaction. Approving it signs it; nothing has been sent yet.
- Send. The app hands the signed transaction to the API, which checks the signature in one more simulation and forwards it to Solana.
- Confirm. The app follows the transaction until the network confirms it, then reads the branch again.
The API's relay only accepts transactions that call the Plumb program. It can't change what you signed: any change would break your signature.
Fees
Each transaction costs a Solana network fee of a fraction of a cent. Opening a trove also pays rent for your trove account, and, if you don't have them, your PLMB and JitoSOL token accounts. The app asks you to keep about 0.01 SOL in your wallet to cover these.
# Wallets and transactions Which wallets work with Plumb, what you are asked to sign, and how a transaction travels from the button to the chain. ## Wallets The app connects to any wallet that supports [Wallet Standard](https://github.com/wallet-standard/wallet-standard), the common interface Solana wallets register in the browser. That includes Phantom, Solflare and Backpack. Wallets appear in the list as soon as they register; there is nothing to install on Plumb's side. The app doesn't include adapters for hardware wallets connected over USB. The app remembers which wallet you used last and reconnects quietly when you come back. **Disconnect** in the wallet menu forgets it. ## What you sign You only ever sign one kind of request: a Solana transaction that calls the Plumb program, built for exactly the action you chose. The app never asks you to sign a message, never asks for a token approval or delegation, and never holds a key. Your wallet shows the transaction before you approve it. Plumb transactions also carry two compute-budget instructions: Plumb's program needs a larger memory heap than the default, and liquidations and stability-pool actions need more compute. ## From button to chain :::figure flow | Your key is used once, in your wallet. Everything else is done by the API and the chain. 1. **Build.** The app sends the action and its amounts to the Plumb API, which builds the transaction against the chain's current state, including any token account you are missing. 2. **Simulate.** The API runs the transaction against the chain before anyone signs. If the program would reject it, you see the reason in a sentence and your wallet is never opened. 3. **Sign.** Your wallet shows the transaction. Approving it signs it; nothing has been sent yet. 4. **Send.** The app hands the signed transaction to the API, which checks the signature in one more simulation and forwards it to Solana. 5. **Confirm.** The app follows the transaction until the network confirms it, then reads the branch again. The API's relay only accepts transactions that call the Plumb program. It can't change what you signed: any change would break your signature. > [!INFO] > A transaction is valid for about a minute after it is built. If you leave it in your wallet longer, it expires and the network drops it. Nothing happens, and you can start again. ## Fees Each transaction costs a Solana network fee of a fraction of a cent. Opening a trove also pays rent for your trove account, and, if you don't have them, your PLMB and JitoSOL token accounts. The app asks you to keep about 0.01 SOL in your wallet to cover these.