For creators

Locked and editable vaults

The one choice that decides whether your budget can ever change, and what holders see either way.

A Squads vault has members with three possible permissions: propose a transaction, vote on it, and execute it. Whoever can execute can, in principle, move vault SOL anywhere with an ordinary transaction, not only through the budget's spending limits. Fuelgauge gives you two ways to set that up.

After the budget lines are added, the last setup transaction rearranges the members:

Squads requires a vault to have at least one executor, and this one can never act. Nothing can execute on a locked vault again: no withdrawal, no new payee, no change of amounts. The spending limits keep working, because they do not need an executor, so the budget lines are the only way SOL can ever leave.

Holders see a Vault locked badge, and the vault card lists both members with their roles.

Editable

You keep every permission. You can change the vault later through the Squads app: add a line, remove one, change a payee, or move SOL out.

Every change waits in public for the time lock you choose (24 to 720 hours, default 48):

  1. You propose and approve the change in Squads.
  2. Fuelgauge sees it and shows Change pending on your coin's page, with what it does.
  3. After the time lock, you can execute it.
  4. Once it runs, the published budget no longer describes your vault, so the coin shows Checks failing until it matches a published budget again.

Holders see an Editable vault badge. It tells them that the creator can change the rules, and how much notice they get.

Which to choose

Locked Editable
Who can move vault SOL Only the budget lines The budget lines, and you after the time lock
Change a payee later No, ever Yes, after the time lock, then re-list
What holders see "Vault locked" "Editable vault", and every pending change
Best for Fixed, known costs Teams expecting their budget to change

What Fuelgauge checks either way

Fuelgauge reads every transaction your vault has ever made. Before listing, and every few minutes afterwards, the setup must be exactly:

all executed, with nothing else in between. A spending limit added by any other route, a transfer, or a batch makes the listing fail. See Trust model.