Trading fees

Approved target; integration pending

These are the October 2 approved production economics. The new net-receipt allocation is tested independently. The isolated local curve still models the previous fee version and does not implement venue protocol collection. Trading remains disabled until the adapter and custody accounting pass end-to-end verification.

Four purposes

Each trade pays 5% of its gross quote-asset value: 2.55% for the project development treasury, 0.5% for community contributors, 0.8% for governance inference/API costs, 0.15% for the foundation, and 1% for the venue protocol. Evangel receives the remaining 4%; its net receipts are allocated 63.75% development, 12.5% community, 20% governance and 3.75% foundation.

For a 100 e/acc buy, 95 enters the trading inventory, 2.55 goes to development, 0.5 to contributors, 0.8 to governance, 0.15 to the foundation and 1 to the venue protocol. A sell deducts 5% from its gross e/acc output. Integer fees round upward to the nearest base unit. Network fees and rent are separate SOL costs. The same percentages apply to SOL pairs, using nine-decimal wrapped-SOL amounts.

Developer income without milestone permission

After verified adoption, development fees are automatically claimable to the fixed project owner. Anyone can trigger payment, but cannot change its recipient. Before adoption, income remains protected for the eventual verified owner. Community fee funds follow objective milestones, completion review and challenge periods.

Daily governance surplus

Venue fees count toward the UTC day Evangel actually collects them. Delayed collections do not reopen earlier days. Each project and UTC collection day has a separate quote-token vault. At daily close, unused governance fees and allocation dust become that same project’s development balance. Approved unpaid expenses remain reserved. No other project can receive the surplus. Closing twice fails; late settlement remains callable.

A keeper submits settlement and development payout together after midnight UTC. Programs do not wake themselves up. The runner is implemented; an active funded scheduler and verified deployment are operational prerequisites, not implied by local tests.

Expenses and quorum timing

An incurred inference/API invoice is proposed for a future reimbursement booking day so the Squads two-day delay can elapse. Only fees available on the execution day can be reserved; the service date may be earlier. The operator fronts costs. Missing the booking day needs a new proposal, and insufficient fees may leave costs unreimbursed. Merely submitting an invoice does not reserve funds or delay daily surplus.

Approval binds invoice identity, project, quote mint, base-unit amount and evidence. The test pilot caps approvals at 100 dummy quote tokens per project UTC day. Payment waits a further two-day notice and goes only to the governance vault. Canceling an unpaid expense returns it to that day’s governance budget before close, or development after close. Paid or canceled invoices cannot be charged again. Paying fiat vendors remains an accountable offchain duty.

Venue compatibility

The 5% specification is tested locally, not a claim that a production pool is live. External venue charges must be reconciled before activation; no silent fee increase is authorized. External pools and ordinary wallet transfers are outside Evangel fee enforcement.