Explore markets · Launch a repo · Protocol analytics · Documentation
repo.ing connects public GitHub repositories and Hugging Face models to canonical token markets on Solana. Anyone can discover an eligible repository and launch its market. Trading earns fees for its builders, even before they connect. A current repository administrator can verify with GitHub, bind a payout wallet, and claim those earnings.
One repository. One market. Identity follows GitHub's permanent numeric repository ID, so a rename or transfer does not create a duplicate.
A community launch does not imply maintainer endorsement. A repository token gives no ownership of the code, repository, brand, or business.
| You are a… | Start here | What happens |
|---|---|---|
| Discoverer | Find repos → review → launch | Find a project getting attention, create its market, and earn a limited share of eligible partner fees. |
| Trader | Explore → choose a market | Review balances, quotes, price impact, and minimum received before signing. Track graduation and transaction receipts. |
| Builder | Builders → verify GitHub | Prove current admin access, set a payout wallet, and claim fees across your repositories. |
| Backer | A Group launch raise page | Fund a community raise for a market; backers share 80% of its partner fees. |
These can be different people. Launching a market does not give its launcher the builder's entitlement.
Production interface, September 26, 2026. Screenshots are snapshots; use the live pages for current figures.
flowchart LR
A["Public GitHub repo"] --> B["Canonical Solana market"]
B --> C["Trading on Meteora DBC"]
C --> D["Builder fees accrue"]
D --> E["Verify GitHub → claim SOL"]
C --> F["Reserve reaches config threshold"]
F --> G["Verified DAMM v2 graduation"]
Paste an eligible public GitHub URL, review its identity, name, ticker, and project image, then approve in your wallet. The launch defaults to No buy. An optional initial purchase is capped at 3% of token supply, with 1%, 2%, and Max 3% presets. This cap applies to the launch transaction, not all future purchases by that wallet.
Or start from the repository you are already working in, with nothing to install:
cd your-project
bunx @repoing/cli launch # or: npx @repoing/cli launchTo keep the repoing command, install it once with bun add --global @repoing/cli or npm install --global @repoing/cli.
The CLI detects the GitHub origin, resolves the canonical repository, and opens a signed repo.ing launch review. It never receives wallet keys or signing authority; current costs and the final transaction still require explicit browser + wallet approval.
Phantom, Backpack, MetaMask's Solana connection, and compatible Solana Wallet Standard wallets are supported. Availability depends on the wallet, browser, and required signing features. repo.ing never asks for a seed phrase.
Agent launch reviews and README shortcuts use the same launcher: an agent can find a repo and produce a review link, while the user reviews artwork and costs and approves with their wallet. Agents receive no signing authority. MCP setup and tools →
A community can fund a market together. Open a raise of 1 to 10 SOL that runs for 1, 3 or 7 days; anyone deposits from 0.05 SOL. When the raise fills, it less 5% for operations buys the first tokens into a permanent vault that trades only within on-chain limits, and the backers share 80% of the market's partner fees in proportion to their deposits. A raise that misses its target refunds every deposit. Builders keep their full 0.994%; Group launches carry no discovery reward. Group launch rules →
A repository of a GitHub organization mapped to a listed company (facebook, microsoft, nvidia) can be launched paired with that company's tokenized stock (METAx, MSFTx, NVDAx) instead of SOL. Its trades pay the same 1.75% fee in the stock: 0.30% to the wallet that launched the market, 1.10% (the builder and repo.ing shares) to permanent $REPOING / stock liquidity, and 0.35% to Meteora. A stock pair has no owner claim, discovery reward, builder allocation or referral. Stock pairs →
A GitHub fork whose parent or source already has a market is refused, and so is a repository that copies the first commit of an older launched repository owned by another account. Other forks can launch and are labeled Fork of <parent>. Fork guard →
A public Hugging Face model gets one market, keyed to its stable ID. Its owner on Hugging Face (the user, or an admin of the owning organization) claims its builder fees in SOL, as a GitHub admin does for a repository. Model markets are not affiliated with or endorsed by Hugging Face.
New markets use an 85 SOL real quote-reserve threshold and begin on Meteora Dynamic Bonding Curve. Buys build reserve; sells can reduce it. Volume is turnover, not reserve. Virtual pricing reserves are not deposited SOL.
After the threshold is met and migration is verified, the market continues in Meteora DAMM v2. The migrated liquidity is split 50% creator / 50% partner, with both positions permanently locked. Their fees remain claimable. After graduation, trading continues in the same trade panel against the verified Meteora DAMM v2 pool.
Older markets keep their original configs. Liquidity guide →
Before graduation, the 1.75% total DBC trading fee has these nominal shares (a new market's launch fee starts at 50.44% and falls to 1.75% over its first 180 seconds; the launcher's own initial buy pays 1.75%):
| Recipient | Share of fee-paying trade value |
|---|---|
| Repository builders | 0.994% |
| repo.ing partner | 0.406% |
| Meteora protocol | 0.350% |
Settlement uses exact integer fee events, including rounding. After graduation, fees follow the DAMM pool and position rules; the fixed DBC percentages do not carry over unchanged. Stock pairs are the exception: their builder share goes to $REPOING / stock liquidity.
New enrolled markets also reserve 1% of their fixed 1 billion supply — 10 million tokens — for the verified builder. This is a one-time allocation from existing supply, claimable only after verified graduation. It is active for the current launch config; historical markets are not retroactively enrolled. Builder trading fees continue separately.
GitHub verification requires current admin access. The App requests Metadata: read, not code-write permission. A wallet-binding message proves control of the payout wallet. The Builders dashboard supports setting a wallet across repositories and claiming all ready fees with individual results and receipts. From a terminal, repoing claim shows what a repository's next claim pays and opens its claim page. Builder guide →
The original launch wallet earns 50% of actual eligible partner DBC fees for enrolled markets. This comes from the partner share; it adds no extra trading fee and does not reduce the builder share.
Accrual ends at the earliest of:
- curve completion;
- 30 days from on-chain activation;
- the market's stored lifetime cap: 2.5 SOL for new v2 launches, 1 SOL for earlier v1 launches.
Already-earned rewards remain claimable afterward. Paid rewards count toward the cap. Group launches and stock pairs carry no discovery reward. Reward rules and settlement proof →
Share any market from repo.ing/referrals. For 30 days after someone opens your link, their trades on SOL-paired markets pay you 4% of the trading fee in SOL, carved from Meteora's protocol share: traders pay the same fee and builders keep their full share. The one-time payout setup is free for now. Referrals →
The active V1 policy allocates eligible claimed platform revenue as follows:
| Allocation | Share | Current meaning |
|---|---|---|
| $REPOING buyback reserve | 60% | Bought back manually by the team from the published buyback wallet; the in-app buyback executor is off. |
| Protocol liquidity | 20% | Added manually by the team to the canonical $REPOING pool; the in-app liquidity executor is off. |
| Treasury | 20% | Retained platform allocation for operations. |
The allocation path consumes settled platform-fee claims: DBC collections reserve unpaid discovery rewards before payment; DAMM claims use the platform partner position. Builder earnings and discoverer obligations are separate. See fee collection and treasury custody. An accrued fee is not spendable revenue, and an allocation is not an executed purchase.
$REPOING is live through the ordinary repository launch path. This repository was tokenized with the same 1 billion supply, 1% builder allocation and normal discovery/fee rules as other new markets. Its immutable on-chain ticker is REPOING; earlier planning used $REPO. The launch/team wallet purchased approximately 3% for 0.856011397 SOL, excluding launch account/network costs. The normal 1% builder allocation is separate and unlocks after verified graduation. Builder earnings remain separate from the 60/20/20 policy; eligible partner-fee claims enter that policy like other markets. Verified mint, launch receipt, and wallet disclosure →
Current operations: the in-app buyback and liquidity executors are not enabled. The team runs the policy manually from published wallets: a platform-fee sweep claims fees to the partner fee wallet, allocates 60/20/20, and moves the buyback share still owed to the custody buyback wallet; buybacks are swapped from that wallet (platform revenue) and from the team wallet (team buybacks on top of the policy); liquidity is added by the team wallet to the canonical $REPOING DAMM v2 pool. A worker detects and publishes buyback receipts from those wallets. There is no automated buying or promised return. Every $REPOING buyback made so far (platform revenue and team wallet) is published with its on-chain receipt and running total on Stats; Stats also shows where buybacks stand against the policy (SOL ahead or due) and the published liquidity deposits. The first audit covers the initial two purchases. Recorded revenue allocations remain separate from the purchase total and are not proof of a live funded wallet balance. Full $REPOING readiness and policy → · Ordinary launch economics and review →
Stats shows builder earnings, settled payouts, trading volume, UTC activity charts, and reconciled platform reserves. Choose 24h, 7d, 30d, or All time, inspect exact SOL values, and open payout receipts.
USD figures use the current SOL price; they are estimates, not historical dollar proceeds. Empty periods stay empty. Pending payouts and unverified pools are excluded. Metric definitions →
| Area | State |
|---|---|
| Launches, DBC trades, builder claims, discovery rewards | Live, with recorded mainnet settlement evidence |
| 1% builder allocation and 2.5 SOL discovery cap | Active for new enrolled launches; allocation unlock requires verified graduation |
| Find repos, discoverer leaderboard, graduation progress, protocol stats | Live |
| Graduated fee capture and 60/20/20 revenue controls | Deployed; $REPOING graduated on 2026-09-28 and its first graduated builder payout settled the same day |
| $REPOING buybacks | Manual, published: the team swaps from the buyback and team wallets; receipts, running total, and policy standing on Stats. The in-app buyback executor is off (reviewed executor and activation still required) |
| $REPOING protocol liquidity | Manual, published: the team wallet adds liquidity to the canonical $REPOING DAMM v2 pool; deposits on Stats, positions not yet locked |
| In-app protocol liquidity executor (P3) | Built, execution off; first bounded run capped at 0.05 SOL investment + 0.012 SOL overhead |
| Builder Reinvest | Prepared, execution off until the P3 executor has one verified non-zero mainnet deployment and reconciliation MATCH |
| Group launch | Live on mainnet since 2026-10-09 |
| Stock pairs (METAx, MSFTx, NVDAx) | Live since 2026-10-04; the launcher's 0.30% accrues in the stock and shows as awaiting payout until repo.ing runs stock payouts |
| Hugging Face model markets, fork guard, referrals | Live |
| AI credits and contributor early access | Built, not open yet |
No automated market launches, trading, wash-volume incentives, or spending are introduced by the discovery and analytics features.
Next.js · React · Node.js · PostgreSQL · Solana · Meteora DBC + DAMM v2
- GitHub establishes repository identity and current administrator authority.
- Solana establishes finalized settlement and pool state.
- PostgreSQL stores indexed evidence, durable intents, and derived accounting.
- Web handles the interface, quotes, authorization, and protected payout signing.
- Worker indexes finalized activity, recovers authorized transactions, and checks reconciliation.
- Encrypted backups preserve database and payout history off the host.
Builder and discovery payouts are platform-managed: protected signers control the relevant on-chain authorities, while the application enforces GitHub eligibility and payout rules. This is not a trustless GitHub escrow. Migrated liquidity locks are enforced on chain; additional protocol and builder LP positions have separate ownership and withdrawal rules. Architecture and trust boundaries →
Use Node.js 22 and a disposable local PostgreSQL database. Full financial tests also need the documented local Solana validator fixtures.
npm ci
npm run devOpen http://localhost:3001. Configure the ignored .env.local from .env.example and follow Development for migrations, the worker, and safe test setup. An unconfigured checkout does not provide working financial flows.
| Directory | Contents |
|---|---|
app/ |
Interface, API routes, wallet integration, server helpers |
src/ |
Launch, trade, identity, accounting, claims, and reconciliation |
scripts/ |
Workers, operator commands, and rehearsals |
drizzle/ |
Database migrations |
tests/ |
Local verification suites |
docs/ |
User guides, economics, architecture, and operations |
Start with the documentation index, then choose:
- Use the product: User guide · Builders · Discovery rewards · Group launch · Stock pairs · Fork guard · CLI · Editor plugin
- Understand the economics: Liquidity · Builder allocation · $REPOING · Analytics
- Verify $REPOING: Official identity · Ordinary launch economics
- Review or develop: Architecture · Development · Contributing · Security
Original repo.ing source code is licensed under the GNU Affero General Public License, version 3 only (AGPL-3.0-only). See LICENSE.
Third-party dependencies, code, and assets retain their existing licenses and attribution requirements. This grant does not relicense them.
repo.ing — The market layer for open source.