VaultBags

Proof of Reserves

The vault holds real-world assets in on-chain wallets that anyone can inspect. Below are those wallets, the issuer behind each asset, and a Solscan link to check the numbers against the chain yourself. For the aggregate figures, see the Meter and the treasury dashboard. For the books closed each month, see Monthly Reports.

Total reserves, live on-chain

$1,084.76
Real-world assets held in the wallets below, priced from live DEX data. Check any balance on Solscan yourself.

Decisions stamped on-chain

132
Every daily decision since Jul 4, 2026, frozen and receipted with a signed Memo transaction. The first 3 days ran before stamping existed.

Paid to holders, lifetime

$4,629.51
1,102 distribution cycles, 286 holders tracked.

Reserves by asset

Each asset the vault holds, the issuer behind it and what that issuer can do.
GOLD$323.10
0.080768 tokens$4,000.32 each

Physical gold (XAU)

Issuer controlsIts issuer cannot freeze accounts, move balances or pause transfers.
Issueroro (GOLD)The VaultBags treasury buys this token in its regular purchases, so the mint is in active use on-chain.
SPYx$403.21
0.528792 tokens$762.52 each

S&P 500 (SPY ETF)

Issuer controlsIts issuer can move or burn it from any account, the vault's included, freeze any account holding it, pause all of its transfers (not paused right now) and attach its own program to every transfer (none attached now).
IssuerBacked Finance (xStocks)Each token's on-chain metadata is hosted on the issuer domain xstocks-metadata.backed.fi, which only Backed controls.
USDY$358.44
310.9598 tokens$1.15 each

US Treasuries + bank deposits

Issuer controlsIts issuer can freeze any account holding it.
IssuerOndo Finance (USDY)Address published in the issuer docs (docs.ondo.finance/addresses); symbol and decimals confirmed on-chain, and it is traded by the treasury in production.

Custody

The wallets that hold the reserves and run the protocol, each one open on Solscan.

Reserve pools

The assets $VAULT holders claim are held here. Open a wallet on Solscan to read the balance for yourself.

Holders (70%)$778.09
GOLD, SPYx, USDY claimable by holders
Lock Boost (20%)$299.78
GOLD, SPYx, USDY for lock boost

Supporting wallets

Liquidity, operations, and protocol-fee wallets, all public on-chain.

LP (10%)0.0411 SOL
SOL waiting to be paired into the next liquidity deposit, plus a small reserve for network fees. Deposited liquidity sits in the Meteora pool, locked permanently. Also routes the 5% protocol fee from external projects into $VAULT liquidity.
Operations wallet$3.96
Collects fees and holds assets in transit between swap and distribution

Every reserve wallet and balance above is public and verifiable on-chain right now, and so is what each asset's issuer can do to it, read from the asset's own mint. Those controls are set by each issuer, not by VaultBags.

The reserve wallets were also read together at Solana slot 468,354,785, 21 accounts in one request, so their balances can be checked against a single moment. Supporting wallets are read on their own. Updated ..., refreshes every minute. Live reads of on-chain balances priced via DEX data. Nothing here predicts returns or moves funds. Always re-verify a mint before sending funds.

Every payout, checked against the chain

606 of 606

payouts confirmed on-chain, every one this protocol has ever recorded

The claim records are a ledger this protocol keeps about itself, so each one is looked up on Solana and counted. Check it without trusting any of this: every day of payouts with the root stamped on-chain, and this same count as data. The latest day in full carries the transaction of every claim in it, so you can ask any Solana node for their status yourself.

Or run it against your own node, which is the version that contains nothing of ours: npx vaultbags-cli verify payouts

Liquidity the protocol built

A slice of every trading fee the protocol collects is used to buy $VAULT, pair it with SOL and deposit it as liquidity, and that position is then locked permanently. The position then earns fees of its own, from trades in the Meteora pool, and those are a separate thing: they are claimed and put straight back into the same position rather than withdrawn, so it grows on what it earns. Every figure below is priced at the hour its operation happened, not at today's rate, and all of it is rebuilt from the liquidity wallet's own public history.

Record read from Solana at Nov 12, 02:17 UTC. Pool position read at Nov 12, 02:17 UTC.

Put into liquidity

$870.61
128 deposits since Apr 8, 2026, each at its own price

SOL side

4.9128 SOL
paired with the token side

$VAULT side

10,075,145
bought with protocol revenue

Meteora LP fees, put back in

$287.40
autocompounding, 56 claims, 3.1607 SOL

What that liquidity represents today

$473.48

14,461,270 $VAULT ($237.16) and 2.8318 SOL ($236.32) at prices read at Nov 12, 02:17 UTC. This is a different question from the figure above: that one is what the deposits cost when they were made, this one is what the position stands at now. A pool trades its two sides against each other, so it holds fewer tokens and more SOL than went in when the price rises. None of it can be withdrawn.

The position is permanently locked. Read from the pool at Nov 12, 02:17 UTC: it holds no unlocked liquidity, so none of it can be withdrawn by anyone, including the protocol. Everything above was done by this one wallet, so the whole record can be rebuilt from its history without taking any of this on trust.

Recent deposits

DateSOL side$VAULT sideAddedBuy / add / lock
Nov 6, 20260.0294 SOL ($2.65)140,499 ($2.71)$5.36buy / add / lock
Nov 6, 20260.0246 SOL ($2.20)119,479 ($2.25)$4.45buy / add / lock
Oct 30, 20260.0472 SOL ($4.50)138,203 ($4.60)$9.10buy / add / lock
Oct 12, 20260.0491 SOL ($5.48)135,546 ($5.48)$10.97buy / add / lock
Oct 6, 20260.0503 SOL ($6.05)108,549 ($6.17)$12.22buy / add / lock
Oct 2, 20260.0237 SOL ($2.81)51,887 ($2.87)$5.68buy / add / lock
Oct 2, 20260.0250 SOL ($3.06)49,957 ($3.12)$6.18buy / add / lock
Oct 1, 20260.0265 SOL ($3.12)59,939 ($3.19)$6.31buy / add / lock

One lock permanently seals every unit of liquidity added since the previous one, so most deposits are sealed by a later cycle rather than by a lock of their own. None of it can be withdrawn by anyone.

Recent Meteora LP fee claims (autocompounding)

Not the protocol's own trading fees, which is what funds the deposits above. These are what the locked position itself earns from trades in the Meteora pool. They are claimed and spent on the next deposit rather than taken out, so the position compounds on what it earns. This pool pays its fees in SOL only, which is why every claim here is SOL.

DateClaimedAt the timeTransaction
Nov 6, 20260.0543 SOL$4.90claim
Oct 30, 20260.0507 SOL$4.84claim
Oct 12, 20260.0504 SOL$5.63claim
Oct 6, 20260.0501 SOL$6.02claim
Oct 2, 20260.0506 SOL$6.07claim
Oct 1, 20260.0504 SOL$5.93claim
Sep 29, 20260.0511 SOL$6.10claim
Sep 27, 20260.0503 SOL$6.18claim

Showing the most recent of each. The complete record, every deposit and every claim since Apr 8, 2026, is at /api/liquidity, and all of it can be rebuilt from the liquidity wallet on Solana without this site.

Claim ledger

Every day, all settled claims are hashed into a Merkle tree and the root is stamped on-chain. Verify any single claim below, or rebuild the whole tree yourself. The guarantee is on-chain, not here.

Paste the signature of any VaultBags claim to see the exact record committed for it, the day's root and the memo that stamped it.

How the check works

  1. 1Hash the claim record (wallet, amounts, tx) into its leaf.
  2. 2Fold the proof siblings up to the day's root.
  3. 3Check that root equals the on-chain memo, read from Solana.

Decision receipts

Every day the agent freezes what to buy and stamps a hash of that decision on-chain, before it buys anything. Recompute the hash here, in your own browser, and check it against the memo on Solana. The guarantee is on-chain, not here.

How the check works

  1. 1Take the published decision: the date, the three weights, and the market signals it read.
  2. 2Serialize it canonically and sha256 it, in this browser.
  3. 3Check that digest against the memo stamped on Solana that day.