Inside the office.

Collect.

Creator fees are assigned to the program's vault. The worker checks the mint, vault, fee routing and program configuration before it prepares a cycle. A reserve stays in the vault, so allocation does not mean every lamport is spent immediately.

Buy.

Eligible funds purchase CLERK on its bonding curve or PumpSwap pool, depending on the token's current route. Transaction size can require separate collection, purchase and burn steps. Each finalized buyback or burn appears with its own stage in the ledger.

The worker records pending transactions before broadcast and reconciles their outcome before retrying. Insufficient funds, the daily fee budget, a paused configuration or failed validation can stop a cycle.

Burn.

Tokens purchased by a completed cycle are burned. Existing vault dust may also be burned, so recorded burned tokens can exceed that cycle's bought amount. Tokens held separately by the developer are not included.

Check the receipt's mint, token amount and burn instruction in the explorer. The site publishes finalized receipts, rather than treating a submitted transaction as a completed burn.

Observe.

The website is a read-only view. It cannot sign or trigger a buyback. Published launch addresses are labeled reserved until finalized mint, creator and program checks pass. A read-only worker watches the shared launch and account streams. After finalized verification, it pushes the CA and refreshed ledger to connected browsers. Polling remains a fallback if the stream is unavailable.

The chart plots observed buyback and burn transactions only. A staged buyback shows zero burned until the burn settles separately. The latest on-chain activity says when a recorded transaction happened; it does not prove the worker is online now.