Marketing Vault

Most projects spend their marketing budget in private. Firstance puts it in a program. The Marketing Vault holds 3% of the supply and a fixed USDC pool, and it pays that out to the people who promote Firstance on X, in proportion to a public leaderboard, and only after the price clears real milestones.

The six milestones#

The vault unlocks in six steps as the marketcap climbs. Each milestone releases one sixth of the token allocation, so after all six the token side is fully paid out. The USDC pool is paid once, at the first milestone.

Each time the price crosses a milestone, a new leaderboard period opens, and the next tranche rewards what people did during that period. The reward is not loaded onto whoever showed up first. Each leg of the run pays the people who pushed it.

How rewards are sized#

Between milestones, an offchain engagement system scores every linked X account for how much it helped Firstance. Your share of a tranche is proportional to your score, above a small floor so dust payouts do not clog the round. The scoring leans on the firstdoor.app door score, a rating from 0 to 1000 of an account's crypto reach, which can multiply a contributor's earnings by up to five times. Posts have to include the required mentions and stay clear of the banned content listed for that period.

You do not claim anything and you do not pay gas. When a milestone completes, the program pushes each payout straight to the linked wallet.

How a payout is proven, not promised#

This is what makes the 3% verifiable instead of a slush fund.

1. The keeper snapshots the leaderboard at a milestone, computes each wallet's share, and builds a merkle tree of the payout list. The full list is published, so anyone can rebuild the tree from scratch.
2. The keeper commits only the merkle root, the totals, and the recipient count onchain. That step reads the live marketcap from the bonding curve or the PumpSwap pool plus a Pyth price, and it rejects the whole round unless the milestone is genuinely reached. The token total is capped onchain at one sixth of the vault, and USDC is allowed only at milestone one.
3. Each recipient is paid, checked against the committed root, so a payout can only send the committed amount to the committed wallet, and only once. When the last payout lands, the milestone advances and the next period opens.

What the keeper and authority cannot do#

• They cannot distribute early, because the oracle has to prove the marketcap reached the milestone at commit time.
• They cannot over distribute, because the token total per milestone is capped in the program and USDC only ever moves at milestone one.
• They cannot pay the wrong wallet or a different amount, because every payout is checked against the root.
• They cannot stop a round once it is committed.
• They cannot take the money. The authority can rotate the keeper key, propose a round, or, only after all six milestones are done, sweep leftover dust.

A wrong list is fixed the only place it safely can be, offchain, before the root is committed.

Failsafes#

• If the marketcap never reaches $100k within 24 hours of launch, anyone can sweep the whole vault, tokens and USDC, to a fixed refund address.
• If the vault survives day one but never reaches milestone one within 30 days, anyone can refund the still undistributed USDC pool, and the vault keeps running in case the price recovers later.
• Because $250M may never arrive, milestone six becomes distributable 30 days after milestone five completes, so the last contributors still get paid.