The Vault
Two revenue streams, one treasury, and a buying process nobody can game — including the team.
Two funding paths
- NFT royalties — the collection's existing locked 10% royalty splits 4% to the dev wallet and 6% to a permanent wallet, which gets swept into the Vault ahead of each buying epoch.
- $BAG trading fees — a sell-side (and launch-window buy-side) fee on the canonical $BAG pool, pushed into the Vault automatically by the swap fee hook. See Security & Governance for the exact fee schedule.
Permissionless, bounded execution
Anyone can trigger the Vault's next buy once conditions are met, and they earn a small bounty for doing so — a protocol that only works while a specific server happens to be awake is a protocol with a single point of failure. But the caller controls only timing. They never choose the target asset, the spend amount, the route, or the destination — every one of those is already locked in by the vote and by the Vault's own safety rules.
Purchase protection
- Oracle price floor — the minimum acceptable output is always derived from an on-chain price feed, never from anything the caller supplies.
- Hard slippage cap — a fill more than 5% away from the oracle price reverts, no exceptions.
- Chunking — one buy call spends only a bounded share of the treasury, so a single transaction can never drain it.
- Pacing — a minimum interval separates consecutive buy calls.
- Adapter allowlist — only a governance-approved route can ever execute a purchase, and it receives no caller-supplied calldata.
- Capped bounty — the caller's incentive is hard-capped at 1% of the buy, set well below that in practice.
Together, these bound what a hostile or bribed caller could possibly extract to a small fraction of a single buy — and they do it without anyone needing to be trusted, including the team.