Site wallet & treasury shows the Solana wallets associated with your site, the treasury they control, and who must approve treasury changes. Use it to understand setup progress, identify the correct address, and review signer or key changes.
Open Tools → Vault, then select Open, Set up, or Continue setup on Site wallet & treasury, depending on its current status. This area is for administrators. If Vault itself needs setup, start with Storing credentials in Cedros Vault.
Understand the three parts
- Operational wallet: the site wallet that signs treasury transactions and pays setup and network fees. During treasury setup, the deposit instructions point to this wallet.
- Treasury: the Squads account used to receive and hold treasury funds. Once it is created, its receiving address appears under Receive at.
- Site Assistant wallet: a separate wallet for supported assistant operations. It starts unfunded and is isolated from the treasury; creating it does not give the assistant access to treasury funds.
Cedros Vault holds the site-wallet keys. The page shows public addresses and key history; it does not offer a private-key or recovery-phrase export.
New site wallets use Solana mainnet. Setup involves real SOL. Solana charges transaction fees in SOL; see the Solana fee documentation. Use the amounts and addresses shown for your site rather than copying an example from another setup.
Read the current status
The Vault summary and wallet page tell you where setup stands:
- Not set up: the operational wallet has not been created.
- Setup unfinished: the operational wallet exists, but the Site Assistant wallet is still missing.
- Wallets active · no treasury: the wallets exist; treasury setup has not been prepared.
- Waiting for a SOL deposit: treasury setup is waiting for enough SOL in the operational wallet.
- Deposit received: the displayed minimum has been met; Create treasury is the next step.
- Treasury active · site wallet only: the treasury exists with the operational wallet as its only signer.
- Signer change unfinished: adding the independent signer has not finished.
- Treasury active · 2-of-2: the operational wallet and independent signer are both required to approve treasury changes.
A wallet address appearing on the page does not mean the treasury is ready. Check the Treasury status and its Receive at field before treating setup as complete.
Set up the wallets and treasury
Proceed when your site administrator intends to use a Solana treasury and the site supports wallet setup. You need access to a source of SOL on Solana mainnet for the setup deposit.
- Select Set up site wallets. Cedros creates the operational wallet and the separate Site Assistant wallet, then prepares treasury setup. If you return to an unfinished setup, use the displayed resume action.
- If both wallets exist but there is no treasury yet, select Prepare treasury.
- Read the Treasury card's Send, To, and Received fields. To is the operational-wallet address for this setup deposit. Check the network and full address in your sending wallet before approving a transfer.
- Send the displayed SOL amount when you are ready. The card also shows the minimum required. Setup funding covers the Squads creation fee, account rent, and network fees; the suggested amount includes a reserve for later network fees.
- Wait for Received to update and Deposit received to appear. The page checks while it is open and visible. Use Refresh balance if automatic checks pause or you need a fresh reading.
- Select Create treasury. This submits the treasury-creation transaction. Wait for the active treasury, its Receive at address, and the signer list.
Meeting the deposit minimum enables creation; the deposit alone does not finish it. An initial treasury has one signer: the site operational wallet. Creating the wallets and this initial treasury does not require the separate Cedros Wallet extension.
If a step fails, keep the existing setup and read the error before sending more funds. A delayed balance or confirmation is not a reason to repeat the deposit automatically.
Use the right receiving address
During setup, the To address receives SOL for creating the treasury. After setup, Receive at identifies the treasury's receiving address. These addresses serve different purposes.
Copy the address beside the relevant label and verify it in the sending application. The Received amount shown during setup is the operational wallet's balance for the setup check; it is not a report of the treasury's total holdings.
Use the treasury's receiving address for treasury deposits. Do not substitute a signer address, the Site Assistant wallet address, or a Squads multisig account address. Squads distinguishes its vault address for holding assets from the multisig account that stores configuration; see Squads address guidance.
Creating a treasury does not by itself configure your checkout or change an existing payment destination. Complete the relevant payment-service setup separately.
Understand the signer requirement
The Treasury card shows Signers, their addresses, and how many must approve. With the initial 1 of 1 setup, the operational wallet is the only signer. A 2 of 2 setup requires both the operational wallet and your independent signer.
Where available, Add independent signer changes the treasury to 2-of-2. This requires the Cedros Wallet extension and a different wallet you control. If the page offers Open Extensions instead, ask your administrator to check the extension's availability and enabled state before proceeding.
The flow connects the independent wallet and asks you to prove control of it. Review the wallet prompt and the address being added. After completion, confirm that Signers shows both intended addresses and 2 of 2 must approve. If the page offers Resume hardening, reconnect the same independent wallet used to start the change.
Two required signers also means losing access to either signer can prevent approvals. Keep access and recovery arrangements for the independent wallet before choosing this setup. The Squads settings guide explains confirmation thresholds and their access implications.
Review key history before rotating a key
Under either wallet, expand Key history and rotation to see public-key versions and their status. Rotation creates a new key version; it is not a way to refresh a balance or fix an ordinary loading error.
If you intentionally need a new key, select Rotate key for the correct wallet and read the confirmation before accepting. Rotation cannot be undone, and anything using the old public key needs to be reviewed and updated. Key history does not mean a retired key remains usable for signing.
Operational-wallet rotation may be unavailable while treasury setup or a signer change is unfinished. An active treasury needs the independent signer and Cedros Wallet support to replace its operational signer. The page explains the restriction instead of offering a rotation that cannot complete.
If Resume rotation appears, finish that existing operation rather than starting a different key change. Confirm the current public key, version status, and treasury signer details afterward. Rotating the Site Assistant wallet changes its own identity; it does not replace the treasury's operational signer.
Resolve common problems
I cannot see Site wallet & treasury. Check that you are using an administrator account with access to Vault. Shared-credential access alone does not make someone a wallet administrator.
Wallet state could not be loaded. Select Try again. If it still fails, give your administrator the exact error. A wallet loading problem does not mean your saved Vault credentials are missing.
Wallet creation is unavailable or says mainnet wallets are not enabled. Ask your site operator to check the Vault service's wallet support. This cannot be resolved by adding a normal password item or sending SOL to an unrelated address.
Only the operational wallet exists. Use Create assistant wallet or the displayed resume action to finish the missing wallet. Then continue treasury setup.
Create treasury is disabled after I sent SOL. Check the transfer's network and destination against the displayed setup address. Use Refresh balance and compare Received with the current minimum. Review any balance-read error before sending another payment.
The signer change is unfinished. Use Resume hardening and reconnect the same independent wallet. If the extension is unavailable, restore that connection before retrying.
Rotation is blocked or unfinished. Read the message under Key history and rotation. Finish the existing setup or signer change first, or use Resume rotation when shown. If the error persists, contact your administrator with the status and public addresses involved; never send private keys or recovery phrases.