For holders

Check it yourself

Verify a coin's split, vault, budget and receipts on Solscan, without trusting this site.

Everything Fuelgauge shows can be checked on a block explorer. These steps use Solscan; any Solana explorer works.

#The programs involved

#1. The split

The coin page shows the vault address and links the burn wallet. On Solscan, open the coin's transactions and find the one that called the pump.fun fee sharing program to update the fee shares. Its decoded instruction lists the shareholders and their basis points: the vault at 9500 and the burn at 500. Later payout transactions ("distribute creator fees") send SOL to exactly those two addresses.

#2. The vault's members

Open the Squads multisig address from the vault card. In its account data:

• threshold is 1;
• config authority is empty (the default address);
• time lock is 0 on a locked vault, or the stated hours on an editable one;
• members:

That second address is derived from the System Program with the seed fuelgauge:no-executor. It is off the ed25519 curve, so no private key exists for it, and the System Program never signs for derived addresses. In JavaScript:

PublicKey.findProgramAddressSync([Buffer.from("fuelgauge:no-executor")], SystemProgram.programId)[0]

#3. The budget lines

Each line is a Squads spending limit account. The coin page links them, and anyone can recompute their addresses. Each limit's data shows:

• one destination (the payee);
• an amount in lamports (1 SOL = 1,000,000,000);
• a period (1 day, 2 week, 3 month);
• members: who may use it, the keeper and/or the creator.

#4. The vault's history

The multisig's transactionIndex counts every transaction it has ever made. On a correctly set-up vault it equals:

• the number of budget lines;
• plus 1 for the sunset line;
• plus 1 for the lock or time lock.

Each of those transactions is a configuration transaction adding exactly one of those spending limits, or the final lock. Fuelgauge checks this on every pass. You can open each one on Solscan.

#5. Receipts

The vault address (not the multisig) holds the SOL. Its transaction list on Solscan is the receipts list: payouts in, and spending-limit uses out. Each use carries a memo such as budget:servers: October hosting.

#6. The sunset wallet and the burn wallet

Both are ordinary wallets whose whole history is public:

• Sunset wallet: receives from the coin's sunset spending limit, buys the coin, and burns it.
• $GAUGE burn wallet: receives the 5% shares, buys $GAUGE, and burns it.

Every burn lowers the coin's supply, which Solscan shows on the token page.

#Using the API instead

The same data is available as JSON from the public API, for anyone who wants to check it in a script.