Forkd.
Docs & economics

Abandoned upstream. Alive downstream.

Open source rarely dies cleanly. Maintainers move on, and the people who needed the code keep it running in forks that nobody upstream ever sees. Forkd finds those families, helps them reunite their best work, and gives every generation a share.

01 · The tracer

How a lineage is traced

For any public repo, Forkd lists up to 100 forks, ignores the ones nobody ever pushed to, and picks the most promising candidates by recency and stars.

Each candidate is compared against the upstream default branch to count commits ahead and behind, and to read its newest divergent commits.

Fork vitality (0–100) blends divergence (40), push recency (30), following (20) and how current the fork is with upstream (10). The highest-vitality fork is the heir.

The lineage score rewards a quiet upstream (40%), a vital family (45%) and breadth: how many forks are actually ahead (15%).

02 · The council

Four agents, one milestone

Tracker reports the facts. Grafter proposes which fork work to reunite. Auditor challenges the plan on license, conflicts and consent. Gardener narrows it to one reviewable milestone.

With ANTHROPIC_API_KEY set, the council runs on Claude using only the traced evidence. Without a key, a deterministic council reasons from the same data.

A graft is a proposal. Maintainers of the upstream and the heir decide whether anything lands.

03 · The lineage split

10% treasury · 45% roots · 45% branches

These percentages apply to creator fees only, not trading volume, token supply or the launcher's buy.

10% funds the agents' model and API costs. 45% is split equally among up to five top human contributors to the upstream. 45% is split among up to five fork keepers that are ahead of upstream with vitality ≥ 25, weighted by vitality.

If no fork qualifies, the originals receive the full 90%. If the upstream has no human contributors, the fork keepers do. The split is computed in basis points and must total exactly 100% to launch.

Only personal GitHub accounts are paid: forks owned by organizations are skipped, and someone who is both an original author and a fork keeper is counted once. pump.fun allows ten fee recipients per coin, so a split never exceeds the treasury plus nine developers.

04 · On-chain

How a launch works

Coins launch on pump.fun. Each developer's share is paid to a pump.fun social fee account derived from their numeric GitHub user ID. They don't need a wallet in advance: they claim on pump.fun by signing in with GitHub.

Your wallet approves twice. The first approval registers any GitHub fee accounts that don't exist yet and an address lookup table, which is needed to fit ten recipients into one transaction. The second is the launch itself.

The launch transaction is atomic. It creates the coin, routes its creator fees to a sharing config, writes the split, revokes the admin so nobody can ever change it, and makes your initial buy. Either all of it lands or none of it does.

Forkd only lists a coin after reading the chain and confirming the sharing config holds exactly the split you reviewed, with the admin revoked. Anyone can press Distribute on a coin page to push accrued fees out to the recipients.

The mint keypair is generated in your browser and never leaves it. Forkd's server builds transactions but never holds a key that can sign for you.

05 · After launch

The graft board

Each coin has a public graft board. Anyone with a connected wallet can propose the next milestone and state a success check that a newcomer could verify.

Upvotes surface what the community wants grafted next. A coin never implies the endorsement of any author or fork keeper.

Running it yourself
  • GITHUB_TOKEN: raises the GitHub limit from 60 to 5,000 requests/hour
  • ANTHROPIC_API_KEY: runs the council on Claude
  • ANTHROPIC_MODEL: optional model override
  • PLATFORM_TREASURY: wallet that receives the 10% treasury share (required to launch)
  • SOLANA_RPC_URL: dedicated RPC, e.g. Helius or Alchemy free tier
  • SOLANA_RPC_FALLBACK_URL: optional second RPC
  • PINATA_JWT: optional; stores coin metadata on IPFS instead of serving it from this site
  • SITE_URL: the site's public address, used in each coin's metadata and website link
Start tracing