Launch

Token metadata

Name, symbol, description, logo and socials live in a hosted document the creator can update.

A Pinarc token is a plain ERC-20 (PinarcToken): fixed supply, burnable, EIP-2612 permit. Everything cosmetic lives off-chain in a JSON document that the token points at through metadataURI.

Publishing at launch

The launch form posts the document to the app:

POST https://dapp.pinarc.io/api/v1/metadata
{ "name": "Robinhood Chain Doge", "symbol": "ARCD", "description": "…", "website": "https://…", "x": "https://x.com/…", "telegram": "https://t.me/…",
  "image": "data:image/png;base64,…", "creator": "0x…" }
→ { "id": "…", "uri": "https://dapp.pinarc.io/api/v1/metadata/<id>.json" }

The returned uri is passed to createToken and written into the token. Limits: name ≤ 64 characters, symbol ≤ 12, description ≤ 2,000, image PNG/JPEG/WebP/GIF ≤ 400 KB. Only http(s) links are accepted.

Updating later

The creator (the token's metadata authority) can call setMetadataURI at any time; the creator dashboard publishes a new document and sends that transaction for you. The indexer picks up the MetadataUpdated event and refreshes the token page.

transferMetadataAuthority lets the authority hand the keys to another address — the hook a future community takeover will use.

Self-hosting

metadataURI can point anywhere. Any https URL returning the same JSON shape is indexed; the app's hosted endpoint is a convenience, not a requirement.