evangelEVANGEL DOCUMENTATION / 08
Open-source funding
Direct support, sponsorships, milestones, evidence, and payouts.
A coin is optional
The funding protocol is separate from token launches. A verified repository can receive support without creating a coin. Funding currently uses six-decimal USDC on Base Sepolia; alternative launch pairing assets do not change treasury funding.
Choose the right support path
| Path | Destination | Refund or review |
|---|---|---|
| Direct maintainer gift | Selected verified maintainer wallet | Immediate transfer; no platform refund |
| Treasury sponsorship | Selected project purpose bucket | 24-hour refund window before settlement |
| Milestone payout | Authorized contributor | Evidence, governor approval, and 24-hour challenge period |
Repository verification and adoption
Discovery begins with a public GitHub repository. Registration and adoption require provider-backed authority checks and a charter binding maintainer wallets. The verifier API returns unsigned proof data. The authority wallet reconstructs and signs the exact payload in the browser.
Public discovery is not proof that a repository is verified. Direct gifts and treasury funding must check the current onchain project state. A repository owner name or GitHub URL alone is not sufficient payout authority.
Sponsorship buckets
Sponsors select a purpose such as maintenance, contributors, security, documentation, or operations. Their money is credited to that selected bucket rather than distributed through the retired fixed fee-allocation scheme.
Before settlement, an eligible sponsor may refund within the 24-hour window. After settlement, the funds become available for that bucket’s work. Direct gifts do not appear as treasury sponsorship receipts or verified-work payout totals.
Milestone and work authorization
A funded milestone defines the work and budget. Maintainer authorization must bind the exact contributor wallet, milestone, and evidence. A public pull request or commit is evidence of work, not proof that an arbitrary claimant should receive payment.
The work interface can import an authorization packet and validate signatures against current onchain maintainers before submission. Changing the contributor or evidence invalidates the original authorization.
Evidence review
A review report binds deployment, claim, recipient, budget, terms, and evidence. Reports expire after 24 hours. The isolated signer rechecks context, maintainer authorization, and cited artifact hashes. Low confidence, conflicts, a security block, or unverifiable evidence prevents approval.
The funding protocol uses one founder governor approval, not three independent reviewers. Approved claims have a 24-hour challenge period. Funding timing is separate from the launchpad’s two-day notices and rolling 21-day token limits.
Useful evidence
- The exact issue, milestone, or acceptance criteria.
- Immutable commits or other reproducible artifacts.
- Tests, build output, or documentation demonstrating the result.
- Authorization identifying the intended recipient.
- Disclosed conflicts and a clear account of what remains incomplete.