FUELThe production dashboard starts at zero and changes only from persisted funding records.
How FUEL can turn creator fees into agent work
FUEL makes the proposed economic loop inspectable: a creator launches through Pump, approves a disclosed 80/20 fee route, and completed work is recorded against confirmed funding. Until those events exist, the interface shows zero and empty states.
Canonical launch sequence
- Prepare metadata. The token image and metadata are pinned to a permanent HTTPS URI.
- Build with Pump. FUEL calls Pump’s official fun-block create-coin endpoint. The connected Phantom wallet is the transaction fee payer and creator.
- Creator approves launch. FUEL audits the fee payer, mint signer, requested metadata and dev-buy amount before Phantom displays the transaction.
- Creator locks routing. A second official Pump transaction assigns 8,000 bps to the agent inference treasury and 2,000 bps to the FUEL ecosystem/buyback treasury, then revokes admin.
- Verify before recording. FUEL waits for both transactions, checks the creator signatures and re-reads canonical Pump accounts before adding a launch to the registry.
- Simulate before distribution. FUEL invokes Pump’s read-only minimum-distributable instruction and simulates the official collect-fees transaction without broadcasting.
Agent accounting
Unpriced provider usage is never converted into an invented dollar estimate.
Runway is shown only when recorded funding exists; otherwise it reads “Not funded.”
The ledger starts empty and contains only completed user-requested jobs stored in D1.
Safety boundaries
- FUEL never asks for a creator private key.
- Project-default treasuries and the crank payer are unfunded FUEL-only identities, locally recoverable through DPAPI.
- An automation payer may trigger permissionless distribution, but cannot change recipients or redirect funds.
- Mainnet creation and fee-sharing each require an explicit Phantom approval.
- Proof pages re-read canonical Pump accounts and display mismatches instead of hiding them.
- No sample launch, fabricated balance, or seeded success record ships in production.
Inference adapters
Without a paid model credential, Signal Forge uses a labeled local rules engine at zero provider cost. A remote adapter activates only when AI_API_URL, AI_API_KEY, and AI_MODEL are present. If the provider does not return billable cost, FUEL labels the job unpriced instead of estimating one.