sauce reclaim lists the code buffers and address lookup tables a Solana owner has open from its cooks, with the rent they hold, and closes them.
Synopsis
Description
A program too large for one Solana transaction is staged into a Kitchen code buffer and run from there; a cook that names more accounts than fit goes through an address lookup table. Both are accounts that hold rent (Solana from the CLI).- A run closes its own code buffer, unless closing it failed. A plan that was given up on or never finished can leave one open.
- A run keeps each lookup table for the next cook that names the same accounts.
sauce reclaim finds both kinds for an owner. The lookup tables it considers are the owner’s tables that hold the Kitchen’s execution-fee config, which every Sauce cook’s table holds. A table the owner made for something else is left alone. Some endpoints refuse to scan for tables; --lookup-table names tables directly.
Closing.
- A code buffer closes in one transaction, and its rent comes back at once.
- A lookup table closes in two steps. The first transaction deactivates it. It can be closed once its deactivation slot has left the cluster’s recent slot hashes, 512 slots (about three and a half minutes) later; run the command again then. Until then the table still serves lookups, so a cook already built with it can still land during that cooldown.
--keep-tablesleaves the tables open and closes the buffers only.
- A buffer, or an active table, that a transaction named in the last 300 slots (about two minutes) is left open, because a cook built for it may still land. The listing gives the slot from which it can close.
--keep <cursor | @file>keeps a plan you mean to continue, by its cursor: its buffer and table stay open however long its cook waits. The cursor is the onesauce txprints for a multi-transaction plan.
--keypair or --wallet), the command asks, then sends each transaction and prints it; --yes sends without asking. With --owner alone it signs nothing and prints the closing transactions unsigned, as JSON, for the owner to sign anywhere and send with sauce send.
sauce reclaim is for Solana only. A cook on an EVM chain leaves no code buffer or lookup table.
Options
Solana only
Output
Text output names the owner, how many code buffers and lookup tables are open, and the rent they hold, then each transaction it sent or built. Notes go to stderr. With--json:
With
--wallet, the policy notes for that wallet come first on stderr, as with every signing command (spending policy).
Exit codes: 0 on success; 2 for a usage error, such as no --owner, --keypair or --wallet, or a policy file that does not parse.
Examples
List what an owner has open
The same, as JSON
Reclaim with a wallet
--yes sends without asking.
Next steps
- Solana from the CLI: staging, lookup tables and the execution fee.
sauce send: send the closing transactions that--ownerprints.sauce wallet: the wallets--walletsigns with.