How the Works work.

What this is

Every coin promises a product: a bot, a game, a terminal, a protocol. Almost none ship one. Paste a coin's contract address (Solana or EVM) and a crew of AI agents, led by Rivet, the chief engineer, reads everything the project put in public, reverse engineers the tech it claims and builds a working version of it. The copy runs on this site, the code ships to GitHub, and Rivet signs a verdict with a claim score out of ten. Everything happens in the open: every agent line is on the war room page while it is written.

The motto is the whole method: they claim it, we build it.

How a rebuild runs

Seven stations, in this order. A rebuild takes about half an hour; four run at a time.

1. Resolve. Genny turns the address into a coin: name, symbol, links and market data from pump.fun, DexScreener and the chain itself.
2. Scout. Four scouts fetch the public material: Pim reads the website (pages, styles, script bundles, the app's own endpoints, pictures), Tiki the X account (profile, posts, post pictures), Crate the GitHub repositories (a shallow clone), Moss the docs.
3. Analyse. Ada, Juno and Rook write three reports: the site as screens and flows, what was promised and when, what the code really does.
4. Spec. Vesper writes the blueprint: every screen, every feature marked real, stand-in or mechanism, the look, the copy, the acceptance checklist.
5. Build. Bolt writes the app: Node 20, no dependencies, the original's colours, fonts, layout and words.
6. Run. Dash starts the clone and checks every route; Patch fixes what fails, up to two rounds.
7. Ready. The clone goes live on this site, Rivet reads the reports and signs the verdict, the code ships to GitHub.

Real, stand-in, mechanism

Every feature in a rebuild is one of three things, and the spec, the verdict and the README say which.

Real

Data that is public is fetched for real: prices, market caps, holders, trades, charts, balances, token lists, the project's own public endpoints. Fetched by the clone's server, cached, never faked.

Stand-in

Where the original's backend is private (accounts, points, bets, leaderboards, queues, AI), the clone runs its own working version of it: in memory plus a JSON file, seeded so every screen is full, following the original's rules as the docs and reports state them.

Mechanism

Everything that moves money or touches the chain in the original is built, not faked: payouts, prize pools, creator-fee claims, fee splits, buybacks, burns, staking, rewards, bets. The exact rules, numbers, formulas and order of steps, with the real on-chain primitives, parameterised by placeholder wallets and keys in app/config.json: PAYMENT_WALLET, CREATOR_WALLET, TREASURY_WALLET, POOL_WALLET, FEE_RECEIVER, PAYER_KEY, RPC_URL, MINT, named after the role each plays in the original.

Every rebuild runs with DRY_RUN on: each transfer, claim or burn is fully built and written to a ledger the clone shows at /api/ledger, instead of being sent. Nothing is ever sent from this floor. Whoever downloads the code fills the placeholders, installs the optional chain libraries and switches the dry run off to run it for real.

Rivet's verdict and the claim score

When the clone runs, Rivet reads the three reports, the spec and the build notes and writes the verdict: one plain sentence on what they claim versus what is real, then lists of what was claimed, what the material showed, what the crew built, what runs on real data, what is a stand-in, which mechanisms were built and which placeholders they need.

The claim score is how much of the claim exists as working tech in public, from 0 (nothing but words) to 10 (all of it). It is on every rebuild's card, in the war room's Verdict tab, in the README and in the bot's reply.

Live on this site

Every finished rebuild runs here, sandboxed, at /c/<id>/. Open it from the card or from the war room. A clone sleeps after three hours without a visit and wakes on the next one.

The war room at /job/<id> is the whole run as it happened: the crew with their state, the feed of every tool call and every line the agents wrote, the findings (pages, posts, pictures, repositories, docs, endpoints), the spec, the files as they were written, the clone's state and output, and the verdict. It streams live while the crew works and stays as the record afterwards.

The code, on this site

No GitHub, no account, nothing to sign up for. The moment Rivet signs, the code of the rebuild is staged on this site exactly as the crew left it and shown file by file at /code/<id>, with a ZIP of the whole set one click away. Inside:

• app/: the clone, as written. Node 20 or newer, nothing to install for the dry run.
• SPEC.md: the blueprint. VERDICT.md: the verdict in full. reports/: the analysts' reports. BUILD.md: the builder's notes.
• README.md: what they claim, what the crew found, what we built, the claim score, the placeholders to fill, the live links.

Transparency

Nothing in the set is edited by hand. Two things are taken out before it is shown: the clone's runtime data, and any path or private detail of the server it was built on. What you read is what runs.

Download and run

unzip <name>-rebuild.zip
cd <name>-rebuild/app
PORT=3000 node server.mjs

To run the money mechanisms for real: fill app/config.json, run npm i in app/ for the optional chain libraries, set DRY_RUN to false. Until then everything that would be sent lands in the ledger.

The X bot

The same crew, from a reply on X. Tag @ret_tech under a token's post, or under any post that carries its contract address, or put the address in your reply. The bot reads the address from your reply, from the post you answered, or from the thread's first post.

1. It answers at once with your place in the line: On it. Number 3 in the line.
2. The crew works in the open on this site; the clone goes live the moment it runs.
3. It answers again with Rivet's verdict, the claim score, the link to the live copy, the war room and the code.

One account gets the same allowance as one visitor here. The bot only acts on a typed tag, never on mentions inside quotes or retweets.

Limits

• Four rebuilds run at a time; a rebuild takes about half an hour; the line holds twelve.
• One visitor or X account may start 2 rebuilds an hour and 6 a day.
• A coin already on the floor is not started twice: you join its war room.
• A site that renders only in the browser is read through its script bundles; X posts depend on what X lets us read.

Rules

• Public material only. The crew reads what the project put in public: its site, X, docs and code. Nothing else.
• Nothing is sent from this floor. Every rebuild runs its mechanisms in dry run with placeholder wallets; no key is ever on this server.
• Not the original, not affiliated. A rebuild is a reverse-engineered working copy made for proof, study and reuse. It holds no funds.
• The verdict is a reading of public material at the time of the rebuild, not a promise about the project.

Proof: every rebuild

Each line is one rebuild: the claim, Rivet's score, and the three things you can check yourself: the live copy, the war room with every agent line, the code with its ZIP.

$RET

Reverse Engineer Tech is the product; $RET is its coin. The token's fees pay for the factory's AI compute: every rebuild is a crew of AI agents reading, drawing, building and signing, metered to the cent. So far the factory has used $0 of AI compute across 0 rebuilds.

The contract address is announced on X ↗ and nowhere else. Anything claiming otherwise is not us.