Builder guide

1. Claim. On /verify, connect the wallet that will own your builder, enter your GitHub repo or domain, and sign a plain-text claim. Signing is free and sends nothing.
2. Publish the proof. Put the signed file in your repo or on your domain (see below). Only you can publish there, so it proves the project is yours.
3. Register. One small transaction on Arc mainnet from your wallet, or choose “we register it for you” and the Registrai Safe does it for free.
4. Onboarding. Your card appears in the gallery as Onboarding. Nothing else is needed from you: Registrai reviews the claim and onboards your builder in its next batch.
5. Verified. Onboarding issues your Verified Builder Badge: a soulbound NFT in your wallet, numbered in the order builders are verified. Your card turns Verified.

Every proof is re-checked when the gallery loads, and by Registrai's keeper every 10 minutes. Keep the file published: if it disappears, the project shows as Lapsed until it is back.

GitHub repo: the file is .registrai.json (with the leading dot) in the root of the repo, on its default branch. The repo must be public. In the browser: Add file → Create new file → paste → commit to the default branch.

Domain (your code can stay private): the file is served at https://yourdomain/.well-known/registrai.json over https. With Next.js, Vite, Vercel, Netlify or Cloudflare Pages, put it in public/.well-known/. On GitHub Pages also add an empty .nojekyll file. On WordPress or cPanel, upload it into public_html/.well-known/.

Step 4 of /verify shows the exact address for your project, with a recipe per host and a live check.

For when you still control the old wallet.

1. Connect the old wallet on /verify and open Move to a new wallet. Enter the new address and send one transaction. The new wallet must not already hold a builder.
2. Connect the new wallet on /verify and click accept ownership.
3. Every project's proof still names the old wallet: re-sign each one with the new wallet on /verify and replace the published file. No transaction is needed for that. Until you do, your projects show as Lapsed.
4. Your badge follows by itself: within about 10 minutes it moves to the new wallet, keeping its number. Future builder income goes to the new wallet.

1. Email [email protected] with your builder number (on your gallery card) and your new wallet address. We may ask you to prove the project is yours, e.g. by a commit to your repo or a file on your domain.
2. The Registrai Safe starts a recovery of your builder to the new wallet.
3. A 7-day waiting period follows, during which the current owner wallet can cancel. It protects every builder from a wrong or malicious recovery.
4. After 7 days, connect the new wallet on /verify and click finish recovery. Then re-sign your projects' proofs with it, as above. The badge moves to the new wallet by itself.

If someone else holds your old key and keeps cancelling, tell us: the Safe can deactivate the builder and revoke its badge, so a stolen wallet cannot keep showing as verified.

Deployers (for domain projects) are the wallets that deploy your contracts. They are part of your signed proof file, not stored on-chain. To change them, make the claim again on /verify for the same domain with the new list, have each deployer sign, and replace /.well-known/registrai.json. The project is already registered, so there is nothing to send and no gas. Deployers do not change your verified status.

A new repo or domain is a new project: add it on /verify (connected with your builder wallet) and publish its proof there. Then remove the old project from your builder panel on /verify. A builder holds up to 16 projects, and removed projects still count toward that limit.

Remove a project from your builder panel on /verify (one transaction), or simply delete its proof file: the project then shows as Lapsed. With no verified project left, your builder shows as Lapsed and so does your badge. A badge's number is never given to anyone else; if you publish a valid proof again, you are verified again.