FORKD DOCUMENTATION

From source to deployment.

Understand the product, explore the source, and see exactly what a funded build needs.

28 guides

Start here

Find a repository and understand the path to a build.

Under the hood

The website, storage, runner and public repository.

API reference

Read endpoints, authentication and response states.

Understand Forkd

8 guides

Introducing Forkd

A platform for turning open-source crypto repositories into new projects on Robinhood Chain, with token launches through PONS.

2 min read

Your first fork

Choose a source, define a useful change and understand what happens before a build.

3 min read

How it works

From a crypto GitHub URL to a funded, reviewable fork.

2 min read

The repository index

345 researched crypto repositories, source-specific fork proposals and community priorities.

2 min read

Crypto repositories

Which projects are eligible and what remains attached to a fork.

2 min read

Voting & request limits

How repository votes work, what they prioritize and the limits of account-based voting.

3 min read

Fees & funding

Creator fees fund development. Product revenue returns to the FORKD treasury.

2 min read

Frequently asked questions

Practical answers before requesting a fork.

2 min read

Build & operate

17 guides

System architecture

The website, durable state, isolated runner and public publisher have separate responsibilities.

3 min read

Source & license review

Interpret the research snapshot, verify the exact revision and prepare an actionable migration review.

3 min read

Repository & fork folders

Where every candidate, run and reproducible patch lives in the public workbench.

2 min read

Porting to Robinhood Chain

Different source runtimes need different migration plans and evidence.

3 min read

The agent runner

Isolated execution, pinned source, bounded spending and reviewable outputs.

2 min read

Build lifecycle & recovery

Track request state, runner state, event delivery and credit reconciliation without confusing them.

3 min read

Live public coding

Actual model tool events and incremental code commits, with a separate trusted publisher.

3 min read

HTTP API reference

Read the catalogue, understand availability flags and integrate authenticated requests and callbacks.

4 min read

Accounts & authentication

A private gateway verifies sessions while Forkd stores only an opaque account identifier.

2 min read

Availability & service states

Understand the difference between published research, configured services and verified activity.

2 min read

Setup & operations

The services and configuration required to activate builds and funding.

2 min read

Configuration reference

Configure each service privately and understand what a variable can—and cannot—enable.

3 min read

Deployment & PONS

Software deployment and token launch are separate steps, each requiring verifiable configuration.

2 min read

Review & release evidence

What needs to exist between a generated patch and a project described as live.

2 min read

Security boundaries

What the controls protect, and where trust remains.

2 min read

Troubleshooting

Resolve common website, account, execution and publication failures without inventing state.

3 min read

What Pyre does

The public implementation behind fee-funded apps and what Forkd adopts.

2 min read

Terms & privacy

3 guides

Terms of use

Conditions for using the Forkd interface, submitting source, and interacting with experimental builds and tokens.

5 min read

Privacy & data

What Forkd processes, why it is used, and the limits of pseudonymity.

2 min read

Risk disclosures

Understand what can fail before funding, launching or using a crypto fork.

2 min read