Policy set 2026-09-09. The first monthly entry is published one month after launch.
The rule
Pons V2 charges the creator tax $DAWN launches with — 2% of every trade, on the bonding curve and, after graduation, in the Uniswap v4 pool — and pays it in full to the creator fee recipient, which is the Dawnscan treasury. The treasury spends it in three equal parts:
| Part | Pays for |
|---|---|
| Research bounties · 1/3 | Researchers and builders who verify ships, correct records and map sources (the Scout layer, M12) |
| Infrastructure and data · 1/3 | Servers, RPC, indexing, the public API and feeds |
| Platform operations · 1/3 | Moderation, the weekly content, badges and films |
Never a buyback and never a market operation. Buyback is price language; Dawnscan's rules forbid it, Pons's own buyback flag stays off for $DAWN, and no part of the treasury is used to trade $DAWN.
Where the rows come from (M13-B)
Since 2026-09-10 every Dawnscan movement the platform handles is a row in hey_treasury_ledger:
research-request payments, bounty funding and payouts, bond deposits, refunds and forfeits, and the
infrastructure and operations lines the founder records on /admin/treasury. The monthly block
below is generated from that table with pnpm data:hey ledger YYYY-MM. Creator-tax sweeps in ETH
are read from the chain as described next and listed alongside.
How the numbers are read
Inflows come from the chain, not from a spreadsheet:
- On the curve, the 2% accrues inside
PonsV2BondingCurveascreatorTaxBalanceand is paid to the recipient when anyone callssweepFees(the curve emits its sweep event; the payment is a plain transfer of the quote asset, ETH for $DAWN, to the treasury). - After graduation, the hook (
PonsV2MemeHook) collects the tax on pool trades and pays the creator's share to the same recipient onsweepPoolFees. - The ledger lists every sweep by transaction hash and sums them per month. A reader can re-derive the total from the treasury address on Blockscout.
Outflows are the founder's monthly entries, one line each, with a transaction hash for on-chain payments or an invoice reference for services. Each line carries one of the three categories.
Template (one table per month)
## 2026-10
Inflows (from chain)
| Date | Tx | Source | ETH |
|---|---|---|---|
Outflows
| Date | Category | What | Reference | ETH |
|---|---|---|---|---|
Totals: in X ETH · research bounties Y · infrastructure and data Y · platform operations Y · carried forward Z
The same table is what the /hey page will show once the first month is published; until then the
page states the policy and the date the ledger starts.