Follow
the fees.
One creator fee.
Three clear destinations.
$SPON directs its creator fees to a public smart contract called the Vault. It allocates those fees to holders, token burns, and operations.
See how it moves
From a trade
to three destinations.
Pons collects the creator fee. The Vault records each allocation when the fees are collected or synced.
ETH → $PONS → your wallet.
The Keeper triggers a market purchase of $PONS. The tokens go straight to the Distributor, which pays eligible holders in rounds.
Each swap is limited in size and frequency: a per-swap cap, a daily cap, a 30-minute cooldown and a 3% price-impact limit. Fees beyond those limits wait in the Vault for later swaps.
Buy $SPON. Reduce its supply.
The Keeper triggers a market purchase of $SPON using the burn allocation. The Vault then burns those tokens permanently. Each burn leaves a public transaction.
The burn swap has a weaker price guard than the holder swap.
A visible operations allocation.
The operations wallet receives its designated share for transaction gas, infrastructure, and marketing. This is the system’s stated operations allocation.
The proposed share is 10%. The contract limit is 20%. Check the wallet.
Three contracts.
Separate responsibilities.
What you hold.
How long you hold it.
The planned policy uses your average $SPON balance between rounds. Hold in your own wallet. No staking or locking is required; normal payouts are sent to you in $PONS.
Time changes your average.
Start with no $SPON, then hold the amount below for part of a round. Real calculations include every balance change.
Buying near the end counts only for that part of the round. This example checks the proposed balance threshold, not your actual wallet eligibility or payout.
Only eligible balances count.
Liquidity pools, burn addresses, system contracts, and exchange/router addresses are excluded. Holding through an exchange or an LP does not qualify.
Exclusion list · pendingSmall payments & failed payments.
The minimum payout and how smaller allocations roll forward are pending. A failed transfer is different: it becomes a credit owned by your address. Credits never expire.
A payout round,
step by step.
The proposed cadence is every 2 hours. Opening a round locks a pot of $PONS. A public list specifies each wallet’s allocation, followed by a safety delay before payments can begin.
- 01Pot reserved
Open
The Distributor reserves the pot for this round. New incoming funds remain available for later rounds.
- 02Public allocation
List published
The Publisher posts every wallet and amount publicly, and records the list’s fingerprint on-chain. Anyone can recompute it.
- 031 hourworking default
Safety delay
A separate watchdog is intended to recompute the list from chain data. Before the delay ends, the Guardian can cancel an incorrect list (once per round) and pause new lists for up to 72 hours; the Safe can also cancel. A corrected list then goes through its own full delay.
- 04Batched transfers
Paying
After the delay, the list cannot be changed or cancelled. Payments are pushed in batches of about 100 wallets. Each allocation is settled only once.
- 05Public receipts
Done
The round completes when every allocation is settled. Unallocated rounding stays available for future rounds. After the claim window, an expiry transaction returns the unsettled remainder to the Distributor for future rounds; that transaction cannot send it to the team.
The receipts
should be public.
Check the contract addresses, source code, and payout lists. Use the directory and on-chain records below to verify the fee flow.
Contract directory
Copy an address. Check its source.| Contract / wallet | Address | Verify |
|---|---|---|
| Addresses pending. Enable JavaScript to view configured reference addresses. | ||
Four checks you can make.
Once deployment links are published- 01Addresses ↗
Are fees going to the Vault?
On the Pons factory, read $SPON’s launch record. Its creator fee recipient should match the Vault address.
- 02Vault ↗
Does the split match?
Read the Vault’s split. The proposed values are 7000 / 2000 / 1000: 70%, 20%, and 10%.
- 03Contracts ↗
Did those tokens actually burn?
Compare the Vault’s burn event with $SPON’s total supply. The decrease should match the burned amount.
- 04Tool · pending
Does the payout list match chain history?
Download a round list and use the verification tool to rebuild the allocation and compare its fingerprint.
npx spon-verify --round NThe tool and public round lists are pending publication.
On-chain records
Awaiting Vault data connection| Round | State | Pot | Wallets settled | Transactions |
|---|
Wallet payout records are not connected yet. This is a read-only lookup; it never submits a transaction.
Common questions.
Why pay holders in $PONS instead of ETH?
$SPON launches on Pons. Purchasing $PONS for holder payments keeps that activity in the Pons ecosystem. Trading $PONS elsewhere depends on the liquidity and routes available.
Why build a custom system?
It makes the holder payments, $SPON buyback and burn, and operations allocation explicit in one fee policy. The proposed operations share is 10%. Source publication is pending in the verification directory.
Can the fee split change?
Yes, after a public 24-hour wait and only within the hard limits: holders at least 60%, operations at most 20%, burn at most 30%, with a total of 100%.
Can the team withdraw the Distributor’s $PONS?
There is no owner withdrawal function in the Distributor.
Why wait before a payout starts?
The safety delay gives others time to check the published allocations and catch a wrong or malicious list before payments can start. The proposed delay is 1 hour.
Does holding on an exchange or in a liquidity pool count?
No. The planned policy applies to eligible wallets holding $SPON directly. Exchange, router, and liquidity pool addresses are excluded.
Do I pay gas to receive a payout?
No. Payouts are pushed automatically every 2 hours; the sender pays gas. There is nothing for you to claim and no transaction for you to send.
What if the bot is down?
Anyone can trigger the payout of a published round, not just our bot. A bot outage delays nothing permanently.
Does the bot ever sell $SPON to pay rewards?
No. Nothing on our side ever sells $SPON. On the Pons bonding curve, fees on both buys and sells are taken in ETH, so the Vault only ever receives ETH. After graduation, Pons takes the fee in the output currency of each trade: sells leave the fee in ETH, buys leave it in $SPON. Those $SPON fees are converted to ETH by Pons itself, inside the pool, with a hard 3% price-impact cap per conversion; that is Pons's own mechanism for every coin on the platform. Our Vault has no code path that can sell $SPON. It only buys $SPON to burn it, and the only thing it can do with any stray $SPON is burn it. The bot adds buy pressure only. The "bot dumps the full clip" problem seen on transfer-tax coins, where the tax piles up in the coin and a bot sells it all at once, cannot happen here.
Where can I report a bug?
Security contact: Pending publication. A reporting destination will be published before launch.
The terms, explained.
- Vault
- The contract that collects and allocates creator fees.
- Distributor
- The contract that reserves $PONS for rounds and pays holders.
- Swapper
- The adapter that executes purchases on the exchanges.
- Round
- One recorded payout cycle with a fixed pot and allocation list.
- Pot
- The $PONS reserved for a particular round.
- Credit
- A failed payment saved for its recipient. It never expires.
- Safe / multisig
- A wallet requiring multiple signers. Here, two of three.
- Keeper
- The bot key allowed to trigger bounded swaps.
- Publisher
- The key that submits a round’s allocation list.
- Guardian
- The key that can pause swaps or cancel a list during its safety delay.
- Timelock
- A forced public wait before a proposed change can take effect.
- Burn
- Permanently removing tokens from the total supply.
- Time-weighted balance
- Your average balance over a period, accounting for how long each balance was held.
- Merkle list
- A payout list represented by one fingerprint. Changing any wallet or amount changes that fingerprint. A proof checks one wallet’s allocation against it.