Crypto repositories
Which projects are eligible and what remains attached to a fork.
Eligible sources
- Public, non-archived GitHub repositories with a concrete cryptocurrency or blockchain purpose.
- Smart-contract languages such as Solidity, Vyper and Move; recognised crypto topics; reviewed crypto sources; or verifiable blockchain dependencies in source manifests.
- DeFi, perpetuals, wallets, on-chain applications and infrastructure, NFT infrastructure, and blockchain developer tools.
Not accepted
- General-purpose websites and software with no substantiated crypto functionality.
- Private repositories, credentials, leaked code, malware, wallet drainers or projects intended to facilitate abuse.
- Submissions that depend on impersonating upstream authors or stripping required attribution.
- Repos that are publicly visible but lack permission for the proposed reuse.
Public does not mean unrestricted
GitHub visibility alone is not a license. The platform records the repository’s detected license and preserves attribution. The automated build gate currently accepts a limited set of permissive licenses. Other licenses require review; dependencies and assets must also be checked.
Upstream source remains governed by its license. Generated modifications do not give the requester exclusive ownership of pre-existing code. Names, logos and trademarks can require permissions separate from a software license.
Percolator
Percolator is an Apache-2.0 Rust risk-engine research project by Anatoly Yakovenko. It is an initial source candidate, not a completed Forkd EVM port. Its financial invariants, account model, custody, oracle inputs, arithmetic and transaction rollback require careful treatment.
Forkd does not claim that Percolator is audited, ready to hold funds, or endorsed by its author for this use.