PONSFees & funding
Creator fees fund development. Product revenue returns to the FORKD treasury.
Creator fees
PONS applies its own launch and trading fee rules. Forkd does not receive every trading fee: it receives the configured creator share. The native-ETH router is designed to claim that share from the verified PONS v2 fee escrow.
For each fork, the proposed allocation is 70% to the build/API treasury and 30% to the FORKD treasury. These percentages describe the division of received creator proceeds, not the total trading fee or a trader’s purchase amount. The current router supports native ETH only, not arbitrary ERC-20 quote assets.
Product revenue
Revenue paid through a fork’s designated product-revenue contract entry point routes entirely to the FORKD treasury. Only money actually received through that route is counted. A project’s external revenue is not automatically observable or automatically redirected by Forkd.
Treasury receipt does not itself purchase or burn the FORKD token. Main-token buybacks need a separate configured and reviewed executor; no such executor is active in this release. Holding a token does not create a right to treasury assets or distributions.
From ETH to API credit
The ledger verifies successful transactions from registered router addresses on Robinhood Chain, checks the canonical block and waits for at least 12 subsequent blocks. Transaction and log identifiers prevent a receipt being counted twice. This confirmation policy cannot eliminate deeper chain reorganisations.
Native ETH is not an API account balance. After proceeds are converted and usable provider credit is provisioned, an authorised operator records a unique settlement reference and USD amount against the verified build-fee receipt. This is a trusted accounting step, not an automatic exchange or oracle valuation.
Reservations, failures and refunds
Starting a build reserves a capped amount of settled credit. The authenticated completion record settles its reported cost and releases unused reserved credit. Duplicate callbacks cannot settle twice.
A timeout may still incur provider cost. Ambiguous dispatches, interrupted runs and unknown costs remain reserved until reconciled. Token trades, on-chain fees, already consumed model calls and third-party charges are not automatically refundable. Mandatory legal remedies are preserved.