Treasury policy
There is no treasury allocation at launch. No verified balance or receipt has been published yet. Do not present an unknown balance as zero.
Public wallets
The addresses are the ones in packages/brand/project.json, also shown on the website. Before relying on an address, compare it with the website.
| Role | Address |
|---|---|
| Creator (launch and fee receipt) | 47fVfGQwCoVStVrW6t9SaRqhPGS2pXgCerTSd1Cn2Gqt |
| Developer (40% of creator fees) | EQoETr1F24A62gyuwy8wWFuxYgQsMPMD7eodPANbdUmy |
| Project treasury (60% of creator fees) | GfS69mfm4z4L5zFvn3bRV1N7t1VMWGhd9kHkKy4RjNES |
The treasury wallet is never connected to launch or trading websites.
Creator fees, if received, are not guaranteed and depend on platform rules, contracts, network conditions and trading activity. Public donations or fees may fund a treasury later. No revenue share or token price support is promised.
Creator fee split
Any creator fees received are split as follows. The percentages are set in packages/brand/project.json (creatorFeeSplit).
| Share | Destination | Purpose |
|---|---|---|
| 40% | Developer wallet (public, separate) | Disclosed compensation for the developer who builds and runs the project |
| 60% | Project treasury wallet (public) | Website, infrastructure, security, design, community programs, specialist advice, reserves |
- This is not a token allocation. Founder, team, presale, VC and private-round allocations stay 0%, and the developer receives no tokens at launch.
- The developer share is announced before launch and is not hidden compensation. Changing the split requires a public announcement before it takes effect. A change never applies to fees already received.
- How fees reach these wallets (paid to the creator wallet and then transferred, or split directly by the platform) depends on current Pump.fun rules. Check this on the official source before launch and record it in source verification.
- Each split transfer is recorded with UTC date, amount, transaction reference and destination. Weekly summaries show the 40/60 reconciliation.
- Neither share may fund speculative trading, wash trading, price support, undisclosed promotion or fake giveaways.
Controls
Keep creator, developer, treasury, small operations and optional public team wallets distinct. Publish public addresses only. Prefer hardware wallets and minimal access. Project funds must not finance speculative trading, hidden compensation, fake activity or undisclosed promotion.
Spending priorities: infrastructure/security, creative work and documented community programs, specialist advice, monitoring, community events and reserves. Funded rewards require explicit terms before announcement.
Proposed review thresholds from the project spec: below $1,000, one public wallet with weekly reconciliation; at $1,000, transition to 2-of-3 multisig; at $10,000, transition to 3-of-5 with a documented approval policy. Record the valuation source and date. These are planned controls, not claims that wallets are already configured.
Reporting
Record UTC date, amount, asset, public sender/recipient, transaction reference, purpose, category, invoice/evidence and reviewer. Reconcile opening balance + receipts − expenses against closing balance, including fees and valuation differences. Publish weekly summaries and monthly detailed reports. Keep private personal data out of public invoices.
Reports belong in docs/treasury/reports/. Use ops/metrics/weekly-report.md; templates must never be published as completed reports. Tax and accounting treatment requires jurisdiction-specific review.