PONSYour first fork
Choose a source, define a useful change and understand what happens before a build.
Find the right starting point
Open the repository index and search by project name, source owner, category, language or proposed fork name. Each entry is a research snapshot with a GitHub source link, review depth, recorded revision and a proposal for Robinhood Chain.
Choose a small, concrete outcome for the first build. Replacing one chain integration, adding a compatible client or extracting a well-defined contract component is easier to evaluate than asking for an entire protocol to be ported in one run.
Read and save the prepared brief
The detail page explains the migration strategy, expected difficulty, acceptance criteria and known blockers. Download its Markdown brief to retain the exact proposal you reviewed. The download is available without signing in.
A prepared brief describes intended work. It does not contain a completed implementation, confer reuse rights or reserve the proposed token symbol. Open the upstream source and check whether its license and runtime fit the intended change.
Write a specification a reviewer can check
- State the existing behavior and the exact behavior the fork should add or change.
- Identify the source components in scope, the target environment and dependencies that must be replaced.
- Define observable acceptance criteria: inputs, expected outputs, error behavior and commands that should pass.
- List explicit exclusions, unresolved dependencies and assumptions that require a reviewer’s decision.
- Keep personal details, credentials, private code and confidential instructions out of the public specification.
Submit when account services are available
A saved request needs persistent storage and a verified account session. The default Vercel website currently provides browsing and research; its durable database adapter and account gateway must be connected before votes and submissions can be saved.
The request form accepts a public GitHub repository URL, a project name, an uppercase proposed ticker, a category and a description. You must accept the terms. Intake fetches the source again and pins the current revision, so it may differ from the catalogue’s original research revision.
Follow evidence through the build
The requester prepares a source review before requesting execution. An eligible license, connected runner and at least $10 of settled build credit are required. The dispatcher reserves no more than $25 for one job.
When execution and publication are configured, the build room shows actual tool events and public commit links. Review the final patch, limitations and test results before arranging any release. Voting, requesting, building, deploying software and launching a token are separate actions.