OPEN-SOURCE FUNDING

Back the people behind the code.

Discover a public repository, verify its maintainers, and fund work with a clear record of where the money goes.

Choose how to support a project

Repository discovery is open to everyone. After maintainer verification and adoption, supporters can fund a treasury bucket for maintenance, contributors, security, documentation, or operations.

You can also send direct support to a verified maintainer wallet. Direct gifts transfer immediately and have no platform refund or milestone conditions. Sponsorships have a 24-hour refund window. Once settled, funds become available to the selected treasury bucket. Contributor payouts require a funded milestone, evidence, governor review, and a challenge period.

Discover a repository →

Funding and coins are separate

A repository does not need a coin to receive support. New coins launch through the Evangel launchpad with 21 million tokens: 70% initial liquidity and 30% governed reserve.

Developer reserve claims are capped at 20% of supply; at least 10% supports community and workers. All reserve releases share a 1% limit per rolling 21 days. Buy and sell fees start at 2.1%, with a 5% cap per direction.

Explore the launchpad rules →

How funding decisions work

GitHub verification binds repository authority to a public charter and maintainer wallets.
The founder-controlled governor reviews work. A conflict, abstention, low confidence, or security block prevents approval.
Adoption and approved claims have a 24-hour challenge window. Launchpad decisions use a separate two-day window.
Work authorization must bind the contributor wallet to the milestone and submitted artifacts. Public evidence alone is not proof of who should be paid.
Eligible refunds remain available during a security pause.

Connect the testnet treasury

The funding protocol uses Base Sepolia (84532), testnet ETH for gas, and six-decimal testnet USDC. Transactions remain disabled until a deployment is connected.

Operator setup

npm install
npm run contracts:build
npm run contracts:abi
npm test
npm run deploy:testnet

Configure NEXT_PUBLIC_EVANGEL_ADDRESS, EVANGEL_DEPLOYMENT_BLOCK, and EVANGEL_RPC_URL from the deployment. GitHub verification also requires a read-only GitHub App and an isolated verifier signer. Keep private credentials out of browser variables.

Deployment and reviewer instructions are in the repository README and implementation guides.

Get testnet USDC ↗

A public record of support

Treasury balances, charter terms, review decisions, and payment events come from contracts. Transaction inclusion, Base L1 finality, and application challenge windows are separate stages.

Historical v0 coin markets use their original rules. They are not the template for new launches. Evangel is not operated or endorsed by Kairence, Circle, or Base.