PONSSource. Fork. Build. Repeat.
Crypto software, community priorities and fee-funded development, with evidence at every step.
Choose the source
Explore crypto repositories, check the pinned revision and read a proposed fork brief. Each source keeps its own licensing and attribution.
Explore repositoriesDefine the fork
A request records the intended change, scope and acceptance criteria. Votes help prioritize sources when voting is connected.
Requests & votingFund the work
Verified creator fees must become settled model and sandbox credit before a job can reserve a capped budget.
Understand the fundingBuild in the open
The isolated runner works from a pinned source. Public events and code commits record actual changes under the source’s own folder.
Open the build roomReview the evidence
Inspect the patch, test results, source notices and remaining limitations. Generated code needs review before release.
Review requirementsRelease separately
Deployment and a PONS token launch are separate steps. Product revenue received through a configured fork router goes to the FORKD treasury.
Deployment requirementsWhat is available today
Browse 345 researched sources, read their porting briefs and explore the code. Voting, saved requests and build activity are marked unavailable until persistent storage and authentication are connected. Paid builds, fee routing and deployments need their own configured services.
Read the service requirements