Pre-mainnet — ire-1 is a public testnet with one validator. Do not put real value on it.

Create

Launch pad

Four inscription recipes. Fill the form, copy a local ired command, and broadcast from your machine. Carrier is a self-send of 1uire. This host will not relay broadcast_tx.

Launch a token

Deploy an ire-insc tick. The JSON is the inscription; the send is only the carrier. This is not CW20 — wasm is not in the running binary.

Tick NINJ is the inscribed mapping for Ninjaagent ERC-20 0x5Ce837Cf242e763F9b0E9A87AA7907C3f5DD083C on Robinhood EVM. It is not the bridged asset and not a minted IRE denom. See BRIDGE.md.

  1. Pick a 4-letter tick.
  2. Copy the command.
  3. Run it with ired, then watch Mempool and Wallet.

Inscribe art

Small SVG or text only. Cosmos memo is 256 characters; we stop you around 180 of payload after the prefix. There is no IPFS path.

  1. Give it a title and paste SVG or text.
  2. If it fits, copy the command.
  3. Run ired, then check Mempool.

Inscribe a file / video

Honest: the bytes cannot live in a 256-character memo. What you inscribe now is a catalog record — name, mime, size. The video itself is not stored. A later inscription module is required for the payload.

  1. Name the file and set mime + byte size (optional local picker fills those fields only — nothing is uploaded).
  2. Copy the catalog command.
  3. The record is on-chain after ~5s. Full video bytes are not, and will not be, until the module exists.

This page never reads file bytes and never sends them to Netlify.

Inscribe a game

Same catalog pattern as video: op:game with a name and mime. The playable bytes are not in the memo. Do not pretend the game is stored on chain yet.

  1. Set a name and mime.
  2. Copy the catalog command.
  3. Run ired. The catalog is on-chain; the game payload needs the later module.

Catalog only. Wasm / CW20 is not live in this binary.