Build on Vitro

The coin object

Every list returns coins in this shape. New fields may be added; the ones here won't be renamed or removed in v1.

Launching from code

The pad builds transactions as { to, data, value }; your wallet sends them; you report each burn and launch by its hash and the pad checks it on-chain. Vitro never holds keys or funds. These endpoints take POST with a JSON body, and are meant for servers and scripts, not other sites' browsers.

1. Check it. POST /api/check with name, symbol, description, optional x, telegram and website links, image as a data URL (PNG, JPEG, WebP or GIF, under 4 MB), and your launcher address. You get back an id and a kind: original, vamp (with the original it copies) or full.
2. Build it. POST /api/build with verdict (that id), launcher and an optional firstBuyBnb. An original gets stage: "launch" and one transaction. A vamp first gets stage: "tribute": a buy of the original and a burn of what it bought.
3. Send, in order, and report. Send each transaction from the launcher's wallet and wait for it to confirm. Report a burn with POST /api/send { hash, kind: "burn", verdict }, then build again to get the launch. Report the launch with { hash, kind: "launch", mint } and the coin is on the pad.

// viem, with a wallet client for the launcher on BNB Smart Chain (chain id 56)
const pad = (path, body) => fetch(path, {
  method: 'POST', headers: { 'content-type': 'application/json' }, body: JSON.stringify(body),
}).then(async r => { const j = await r.json(); if (!r.ok) throw Object.assign(new Error(j.error), j); return j; });
const send = async t => {
  const hash = await wallet.sendTransaction({ to: t.to, data: t.data, value: BigInt(t.value) });
  await client.waitForTransactionReceipt({ hash });
  return hash;
};

const launcher = wallet.account.address;
const verdict = await pad('/api/check', { name, symbol, description, image, launcher });
if (verdict.kind === 'full') throw new Error('That family is full.');

let built = await pad('/api/build', { verdict: verdict.id, launcher, firstBuyBnb: 0.05 });
if (built.stage === 'tribute') {
  for (const t of built.txs) {
    const hash = await send(t);
    if (t.kind === 'burn') await pad('/api/send', { hash, kind: 'burn', verdict: verdict.id });
  }
  built = await pad('/api/build', { verdict: verdict.id, launcher, firstBuyBnb: 0.05 });
}
const hash = await send(built.txs[0]);
const { coin } = await pad('/api/send', { hash, kind: 'launch', mint: built.mint });

The check that counts happens at build. Two people can check the same idea at the same moment and both be told it's an original. Build decides one launch at a time against every coin that has landed and every launch being sent right now, and holds the winner's address for fifteen minutes. A launch that lands after that isn't added.

Launches are closed until launch day. Until launchesOpen is true, check and build return 403.

Checking it on-chain

You don't have to take the API's word for any of this.

• Every Vitro coin is a Flap tax token made through Flap's VaultPortal. VaultPortal.tryGetVault(coin) returns its vault, made by the Split Vault factory in /rules, and getRecipientsInfo() on that vault shows the creator and the pad wallet at 5000 basis points each.
• A vamp's tribute is two transactions from the vamp's creator: a buy of the original, then a transfer of at least the bought amount to 0x000000000000000000000000000000000000dEaD. The burnTx is the second.
• The pad only lists a coin whose name, ticker, metadata, tax and vault match what it built. Anyone can launch on Flap; only those coins are Vitro coins.

Errors and limits

Errors come back as { "error": "…" } with a status that says what kind: 400 for a bad request, 403 while launches are closed, 404 for something that isn't on Vitro, 409 when the pad changed under you, 429 for too many requests, and 503 when the vamp check is busy.