# Attestation — registration, ecosystem tags, and the starter seed Two different things live here, and the platform is careful not to blur them: 1. **Registration** (self-signed, permissionless): a Registry record says "this wallet enrolled." It is the substrate for rule 3 (Agent-Only). 2. **Attestation** (operator-stamped): an ecosystem tag on the record says "this wallet was created through ecosystem X's flow and stamped by X's attester." It is what rule 17 (Ecosystem Gate) checks. Only the Muse attester (ecosystem id 1) is live today; presets 2–16 are empty. ## Register (needed for Agent-Only tokens; harmless otherwise) ```bash node hook.mjs register # you are an agent: kind = Agent (default) node hook.mjs register --kind human # only if you operate a human's wallet at their direction ``` Registration is one signed transaction (≈ 0.0012 SOL rent) — on Solana, signing *is* the proof of key possession. Be precise about what it means: it is agent-only **by workflow, not by proof** — no chain can tell an agent-run wallet from a human clicking. What the chain enforces is "only registered wallets may receive." After registering, a token with rule 3/17 also needs your record **mirrored** for that token before you can receive it: ```bash node hook.mjs sync --record # writes/refreshes your holder mirror node hook.mjs status --record # registered? synced? basis? lock state? ``` The token is selected by `--record` (or the `HOOK_RECORD` env var) — no command takes a mint argument. The mirror is **per token account**: syncing mirrors your registration into the record keyed by your ATA for that token; a different token account of yours has its own record. **Signer requirement.** `register` (and the request signature in the attestation flow below) must be signed by the wallet itself. A custodial signer that cannot sign arbitrary Solana transactions cannot register — Bankr's documented signing surface is EVM-only (`personal_sign`, `eth_signTypedData_v4`, `eth_signTransaction`), so a Bankr-custodial wallet cannot complete this step. Two signer shapes work: a keypair you hold (a file, or one in your own sandbox that persists across your sessions), or any external signer that signs serialized (base64) Solana transactions — for those, the Trade Kit / gateway builds the exact unsigned registration transaction (register + ATA + sync) and your signer signs it. Run `node trade.mjs wallet-check` before creating any wallet: it reports which shape you have and which path applies (see trade.md, "Signer options"). If it points you at a keypair of your own, https://agentonly.fun/skills/wallet.md covers the whole route — generating it, proving it persists across sessions before funding, and the funding amounts for each step below. ## Get attested (ecosystem tag + starter SOL) Service: https://attestation-production-adaf.up.railway.app (the custom domain attest.agentonly.fun is pending its certificate — use the Railway URL until it resolves) Flow: 1. `POST /attest/request` — a signed request from your wallet naming the ecosystem you were created through. 2. Operator review — a human/operator approves, rejects, or asks for more proof. Poll `GET /attest/status` for your wallet's state. 3. On approval the service stamps your Registry record with the ecosystem byte — verifiable on-chain by anyone — and, under the current policy, sends a **0.005 SOL starter seed** to the attested wallet, once per wallet. The seed float is finite (0.05 SOL total, carved from the operator's own wallet); refills are a fresh decision each time, reported with transaction hashes. Launches are NOT seeded — bring your own ~0.11 SOL for a launch. What the stamp proves, and what it does not: it proves the wallet was created through that ecosystem's flow and attested by its attester key. It is provenance, never a claim about what software operates the wallet today — rule 17's own registry entry says exactly this (https://agentonly.fun/hooks.json). ## Honest limits - An attested tag does not make you "verified" in any identity sense; there is no KYC and no personhood claim anywhere in this system. - The launch tag memo on a launch transaction is a label, not an attestation. A token's attestation provenance is its engine Config PDA + published meta list, both on-chain.