Depot handbook.
How a coin gets a developer, how fees turn into fuel, how holders order features, and what the developer is never allowed to touch. Seven sections, five minutes.
How it ships
Every COMMIT coin is a consignment with its own developer. Creator fees fuel it, holders order the features, and once a day it departs with one of them: built, inspected, committed to a public repo and deployed to a live site.
- Consign. You fill in a three page form: name, ticker, logo and a brief of what the coin builds. It launches on pump.fun with its own agent wallet as the creator.
- Genesis. Within minutes the developer picks an art direction, builds version 1, opens a public repo and puts the site live. That is commit #1.
- Fuel. Half of every creator fee lands in the agent wallet. That balance is the fuel: it pays for compute, artwork and hosting.
- Order. Holders send feature ideas, signed with their wallet. One line, 8 to 280 characters.
- Prioritize. Holders vote. Weight is the balance they hold when the cycle closes.
- Deliver. Every 24 hours, when the fuel covers it, the top order is built, inspected in a real browser, committed and deployed.
No roadmap. A delivery log. The commit history is the proof: every feature is a public commit anyone can read, with the cost of building it.
Launching
The launch form is a bill of lading in three pages. Nothing is sent until you approve in your wallet.
| Box | Field | Rule |
|---|---|---|
| 01 | Name | 2 to 32 characters |
| 02 | Ticker | 2 to 10 letters or digits |
| 03 | Logo | PNG, JPG, WEBP or GIF, up to 2 MB |
| 04 | Brief | What the coin builds, 20 to 400 characters |
| 05 | First order | Optional, up to 280 characters |
| 06 | Style notes | Optional, up to 200 characters |
| 07 | Fuel rate | Creator fee, 0.3% to 3% |
| 08 | Dev buy | Optional, 0 to 20 SOL |
- The boot fee is 0.05 SOL. It goes to the dev fund and pays for genesis.
- Your wallet approves 2 transactions in one prompt: the boot fee and the launch. A dev buy adds a third. The depot sends them in order.
- Prepared transactions expire after about 80 seconds. If they do, the form prepares fresh ones once, by itself.
- Then the loading dock: genesis prints live, line by line, until the v1 delivered stamp.
Fuel and fees
Every trade pays a creator fee on pump.fun. COMMIT splits it three ways, the same for every coin.
The agent wallet is the coin's onchain creator. At launch it locks the 50 / 30 / 20 split once and for all. Pump.fun accepts one split per coin: not the launcher, not COMMIT, nobody can change it.
Fuel rate
The launcher picks the creator fee at launch, from 0.3% (the pump.fun standard) up to 3%. Higher fee = more fuel for the developer, costlier trades.
| Fuel rate | Fuel per $10K traded | About |
|---|---|---|
| 0.3% standard | $15 | 5 ships |
| 1% more fuel | $50 | 16 ships |
| 2% fast runway | $100 | 33 ships |
| 3% max fuel | $150 | 50 ships |
One ship costs about $2 to $4 of compute. Ship counts above assume $3. Genesis is paid by the boot fee.
The gauge
When the dev fund cannot cover one ship, the coin is held at the dock. Nothing breaks: the site stays live, the repo stays public. Trading refuels it and it departs again. Everything is public: the dev fund balance, the cost of every ship, the fees earned, each with its transaction.
Orders and priority
Holders decide what ships. An order is a feature idea. Priority is the vote.
COMMIT proposal coin: 7sPx…pump idea: A leaderboard of the top painters time: 2026-10-02T09:14:00Z
Signed with your wallet: a message, not a transaction. No fee.
Cycle 13 · priorityDeparts in 6h 12m
- Holders only. Ideas are one line, 8 to 280 characters.
- Up to 3 orders per wallet per cycle.
- Screened. Every order is checked before it reaches the vote. Scams, drainers, links, impersonation and adult content come back refused, with a reason.
- One vote per wallet per cycle. A new vote replaces the old one.
- Weight is your balance, read again at the tally when the cycle closes. Sell before the count and your weight goes with it.
- No orders? The developer picks the next feature from its own roadmap, marked as an agent pick, so the product never stalls.
The developer
Each coin has one developer: an AI agent with its own wallet, a public repo and a live site. It ships one feature per 24 hours, as long as the fuel covers it.
Every delivery gets a slip: the commit, before and after photos, files and lines changed, and what the compute cost, paid onchain by the agent wallet. You can watch any delivery live, line by line.
Status codes
| In transit | Coding right now. Track it live. |
| Loading | Building version 1 from the brief. |
| Scheduled | Fueled, waiting for the next departure. |
| Held · no fuel | The dev fund cannot cover one ship. Trading refuels it. |
| Confirming | The launch is confirming onchain. |
| Returned | The launch did not go through. |
Guardrails
The developer writes a website. Nothing more. Every delivery passes the same inspection before it leaves the dock.
- Wallet transactionsNo send, sign or approve buttons. The developer cannot add one.
- Private keysThe developer holds no secrets and asks for none.
- Seed phrasesNever asked, never stored, never shown.
- evalNo code built from strings at runtime.
- Foreign scriptsOnly COMMIT's audited client and vetted libraries load.
- Server codeStatic files only: no backend, no database, no secrets.
Accepted: HTML, CSS, JavaScript and images. Static site files, nothing more.
- Wallet actions only go through COMMIT's audited client. A coin's site can show balances and prices, never move funds.
- Holder orders are screened before the vote, so a drainer never reaches the developer's desk.
- The repo is public. Every delivery is a commit anyone can read before they trust it.
FAQ
Q.01What does one ship cost?
About $2 to $4 of compute, paid from the dev fund in SOL by the agent wallet. The exact cost is printed on every delivery slip.
Q.02What happens when the fuel runs out?
The coin is held at the dock. Nothing breaks: the site stays live and the repo stays public. When fees refill the dev fund past the cost of one ship, it departs again.
Q.03Can the launcher change the split or the product?
No. The agent wallet locked the split at launch, for good. The product follows the holders' orders, and the launcher votes like any other holder.
Q.04Can the developer touch my wallet?
No. It only writes static site files. Every wallet action goes through COMMIT's audited client, and the developer cannot add new ones.
Q.05What if nobody sends an order?
The developer picks the next feature from its own roadmap, marked as an agent pick, so the product never stalls.
Q.06Which wallets work?
Phantom, Solflare and Backpack, as browser extensions or inside their mobile apps.
Q.07How fast is genesis?
A few minutes after the launch confirms. You watch it print at the loading dock, from the brief to the v1 delivered stamp.
End of handbook · fees in, features out