follow the receipts.
Creator rewards fund buybacks. Purchased tokens are burned.
The chain records what actually happens.
the mechanism
100% burn intendedcreator rewards
Validate the actual fee-sharing route and delivery to the vault.
the pinned mint
Spend economically eligible fees, preserving the vault reserve.
burn the purchase
Burn 100% of purchased tokens. Existing developer holdings remain separate.
The mainnet program is deployed. The live observation below checks its bytecode and upgrade authority. Launch configuration and the actual creator-fee route are validated after creation. A 100% burn share applies to bought tokens, not the whole supply.
mainnet observation
readingThe saved mainnet deployment is below. Its current bytecode and authority are awaiting a successful observation.
- website RPC WebSocket
- connecting
- RPC subscriptions
- reading
- WebSocket data gap
- awaiting reconciliation
- native runner observation
- reading
- native runner RPC WebSocket
- unknown
- browser event stream
- connecting
A server RPC WebSocket watches mint, vault and fee accounts. Account events refresh confirmed chain reads; HTTP reconciles every 10 seconds and after reconnect. Browser SSE and the native runner's WebSocket are separate connections.
mainnet configuration
confirmed chain readsThe address will appear here when the token is created.
- program
- moLdKy3RTpuAa9MErYpDdm59841qxwnSF66TFbYqAiz
- upgrade authority
- MoLDvfNrGJ7ZUZbzvC19XgggRt818pe4o5Z5coBR3cW
- configuration
- read unavailable
- burn share
- 100% intended; not observed
- reserve
- pending
- authority
- pending
- vault
- pending
- cranker
- pending
- vault SOL
- pending
- vault wrapped SOL
- pending
- vault tokens
- pending
- creator reward share
- 100% intended; pending validation
- creator-fee route
- pending validation
- fee delivery
- not verified
- available creator fees
- unavailable
- current supply
- pending
- cumulative SOL spent
- pending
- tokens bought
- pending
- tokens burned
- pending
cycle receipts
confirmed transactions onlynothing to account for yet
No finalized buyback receipt was observed in the recent transaction window. Missing observations do not establish that no cycles occurred.
Receipts cover at most five recent finalized configuration transactions, not complete history. Per-cycle SOL cost stays unavailable when it cannot be established from a transaction. Cumulative totals come from the program configuration.
Missing reads stay pending or unavailable. The disposable test below is separate from Mold's launch totals.
disposable mainnet test
separate test tokenOn October 1, 2026, a disposable token cycle bought and burned exactly 524,833.667233 tokens. Its supply decreased by the same amount. Existing developer tokens and the vault reserve were preserved.
This establishes the Pump bonding-curve direct creator cycleViaDev route only. It does not establish Mold's fee-sharing route, PumpSwap execution, or persistent runner behavior.