How it works
From a crypto GitHub URL to a funded, reviewable fork.
1. Submit the repository
Paste the public GitHub repository URL. Give the fork a name, a proposed ticker and a detailed description of the functionality that should run on Robinhood. A ticker is a proposal and does not reserve a name or create a token.
You must accept the terms and confirm your rights to submit the source. Requests are saved against your signed-in site account. Connecting a wallet is separate and does not authenticate request ownership.
2. Review the source
The server checks the public repository, crypto relevance and exact Git commit. The source review records license information and a migration brief. Metadata-based crypto checks are an intake filter, not a security audit. Reviewers can reject misleading metadata or an unsuitable repository.
An EVM codebase may still need chain-specific addresses and integrations replaced. Solana and other non-EVM codebases require a port. A change of chain name or token address is not enough.
3. Fund the work
Only settled USD build credit can be reserved for a job. Native token receipts are recorded separately until an operator converts the proceeds and provisions actual API credit. A token purchase does not immediately or necessarily create build credit.
The current dispatcher requires at least $10 of available credit and caps one reservation at $25. A reservation prevents the same credit being promised to competing jobs.
4. Follow the agent
Once an isolated runner is connected, a queued job checks out the pinned source and generates an initial artifact within its configured budget. Tests run in the sandbox. The artifact records the source commit, patch, command exit codes and limitations; raw terminal output remains private. Failed or interrupted jobs may need reconciliation before remaining credit can be released.
5. Review and release
A reviewable artifact is not a production release. A deployment needs working code, test evidence, chain-specific configuration and independent review appropriate to its risks. Software deployment and PONS token creation are separate operations.