Frequently asked questions

INS (Igra Name Service) is the name service native to Igra L2. Every name is an ERC-721 NFT with on-chain SVG art, paid in native iKAS. V2 (live since 2026-05-02) ships two tenures: pick Forever (pay once, no renewals — the brand promise) or Annual (1-year renewable, ~5x cheaper, 30-day grace period). Existing V1 holders keep their names forever and can migrate to V2 Forever for gas only.

Three things: (1) forward resolution — anyone sending you crypto can type alice.igra instead of your 0x… address; (2) reverse resolution — wallets, explorers and dApps display alice.igra wherever they currently show your address; (3) identity — point your name at a website, an avatar, your socials, an IPFS hash, anything you want via the on-chain Resolver.

Depends on the tenure you pick. V2 ships two options at registration:

• · Forever — pay once, no renewals, ever. The contract has no function to charge you again. This is the brand promise; pick this if you want the name for life.
• · Annual — 1-year renewable, ~5x cheaper than Forever per name. Renew any time before expiry (or anyone can renew on your behalf). 30-day grace period after expiry, then the name returns to public availability if you haven’t renewed. You can also upgrade an Annual to Forever at any point by paying the Forever price difference.

V1 holders (legacy mints from before V2 shipped 2026-05-02) keep their names forever — and can migrate to V2 Forever for gas only via the migration banner on /domains.

Tiered by length. Pick Forever (pay once, own for life) or Annual (1-year renewable, 30-day grace). Both in native iKAS:

Length	Forever (once)	Annual (per year)
1-char (ultra-premium)	4,000 iKAS	1,000 iKAS
2-char (premium)	2,000 iKAS	800 iKAS
3-char (rare)	1,200 iKAS	500 iKAS
4-char (uncommon)	800 iKAS	250 iKAS
5–32 chars (standard)	500 iKAS	50 iKAS

Annual is ~5x cheaper than Forever per name and renewable up to 10 years (public dApp surfaces 1-year only — admin can gift multi-year via adminMintAnnual for ecosystem partners). Both tenures use the same on-chain SVG NFT and ENS-compatible namehash surface.

Native iKAS — the gas token of Igra L2. No bridging, no swaps, no stablecoins. If you have iKAS for gas, you have everything you need to mint.

Mint + sale fees stream through an on-chain TreasurySplitter contract that atomically routes every withdrawal:

• · 80% → INS Treasury Safe — a Gnosis Safe multisig that funds grants, integration bounties, and ecosystem spend.
• · 20% → Igra DAO multisig. The splitter contract is built, audited, and tested (41 tests + 4 fuzz × 256 runs); takes effect on launch once Igra confirms their DAO multisig address.

The split is enforced on-chain — it isn’t a promise, it’s a function call. The split percentage is owner-tunable by the Treasury Safe via Safe txs, no redeploy needed. Future-proofed for a deeper DAO handoff: ownership of the splitter itself can migrate to the Igra DAO multisig via the contract’s 2-step ownership pattern.

Sellers pay a flat 2% sale fee. Buyers pay 0%. Optional “featured listing” promotion costs an upfront 1% (refunded if the listing fills). The fee cap is hard-coded at 5% — even a compromised owner key can never extract more.

Yes — the SubnameExtension contract is shipped and tested (27 Foundry tests, all passing). The V2-targeted instance is deployed at 0x7E10…f280 with enabled = false on chain — flipping to true (planned ~3-4 weeks post-V2 launch, once V2 root registrations stabilise) opens the floodgates. When activated, you’ll be able to issue free subnames under any .igra name you own: pay.alice.igra, vault.alice.igra, devs.team.igra, etc.

Yes — once subnames activate, the dApp will surface a one-click “promote to root” flow. You pay the current Forever (or Annual) tier price for that root label and the subname holder becomes the new root NFT owner. Subname stays on the parent for backward-compat unless the parent owner revokes it.

Subnames are issued by the parent name owner, not by INS. They’re free to issue and free to revoke; the parent owner sets resolution targets and can transfer them to other wallets but also retains the ability to reclaim. Root .igra names are permanent, owned outright as ERC-721 NFTs, and can never be reclaimed by anyone — including us.

At the protocol level, yes — via Punycode, the same standard ENS uses. The Registry accepts the ASCII-safe encoded form of an emoji name (e.g. xn--ls8h.igra for 🦄.igra), and IDN-aware wallets & browsers render that back as the original glyph.

The honest caveat: the dApp doesn’t yet have a one-click emoji flow — if you paste a raw emoji into the search box it’s stripped, and we currently display the xn-- form rather than the glyph. To register an emoji name today you’d encode it to Punycode yourself and register that xn--… label. A first-class “type the emoji, see the emoji” experience (with confusable/ homograph protection) is on the roadmap.

When the first-class emoji flow ships, popular single- and double-emoji names will sit on the reserved list and be admin-minted to verified holders only, to stop day-1 sniping. Note that pricing follows the on-chain label length of the xn-- encoding (a single emoji encodes to ~7–9 ASCII characters, so it falls in the standard tier today — not the 1-/2-character premium tiers).

That’s the goal. The cross-chain reverse resolution roadmap covers three layers:

1. Igra-native — already works. Any wallet, dApp or explorer on chain 38833 can read the on-chain reverse resolver and show alice.igra instead of an address.
2. Kaspa L1 — wallet integrations let Kaspa-side tools display .igra identities for the same key.
3. Other EVM chains — bridges that mirror Igra state will allow .igra reverse lookups on chains that hold canonical Igra account proofs.

The first integrations land via the public REST API — wallets call one endpoint and they’re live.

Yes — planned. The Resolver is namehash-compatible with ENS, so adding a CCIP-Read gateway that lets .eth profiles point at Igra wallets (and vice-versa) is mostly a deployment problem, not a contract problem. The aim: register your alice.igra, then attach it to alice.eth so .eth-aware wallets render your Igra identity natively.

Yes. 273 Foundry tests, zero failures across 8 suites (V1 Registry, V2 Registry, Marketplace, Resolver, ReverseResolver, SubnameExtension, TLD-variants, Integration). 1024-run fuzz soak across 15 fuzz tests (15,360 iterations) — no counter-examples. 100% line coverage on Resolver/ReverseResolver, 96–100% on Registry/Marketplace. Full report at TEST_REPORT.md. Reproduce locally with cd contracts && forge test.

A Gnosis Safe multisig at 0x7447…7aA1. The deployer EOA renounced ownership in the same broadcast that deployed the contracts. The Safe can pause the marketplace, adjust tier pricing, and reserve/unreserve labels — but cannot mint names for itself, cannot reclaim user names, and cannot raise the fee cap above the 5% hard limit.

Yes — INS revenue is split with the Igra DAO via an on-chain TreasurySplitter contract. The split is 20% to the Igra DAO and 80% to the INS Treasury Safe on every flush — atomically, no human in the loop, no “we promise we’ll send it later.”

The splitter contract is built, independently security-audited (Ownable2Step admin, send-treasury-first ordering to defeat any gas-griefing recipient), and covered by 41 Foundry tests + 4 fuzz suites at 256 runs each. It takes effect on launch the moment the Igra team provides their DAO multisig address — activation is one forge command + one env var on the production box.

For a deeper handoff later: the splitter’s own ownership can migrate to the Igra DAO via a 2-step transferOwnership / acceptOwnership flow, giving the DAO direct control of the split percentage and recipients. Full runbook + trust model are in docs/TREASURY_SPLITTER.md.

Your name lives on chain — if Igra is down, no one can mint, sell, or transfer. When Igra comes back, your NFT is still in your wallet. Igra L2 is secured by Kaspa BlockDAG; sustained downtime would be a Kaspa-wide event, not an INS problem.

Two recommended paths, in order of effort: (1) hit the free public REST API (https://insdomains.org/api/resolve?name=alice.igra), or (2) read the contracts directly via resolve(label) on the Registry (forward) and primaryName(address) on the ReverseResolver (reverse). A namehash-compatible Resolver also exists for ENS-style tooling, but for production resolution use paths (1) or (2) — full .eth interop ships separately via a CCIP-Read gateway. TS + Python snippets + the namehash caveat are in INTEGRATION.md.

Edge-cached for 30–60 seconds per endpoint, no auth needed. We don’t rate-limit small integrations. If you’re running a high-throughput indexer, please use Path 2 or Path 3 above and read directly from chain.

DM @GoonBoyCrypto on Telegram. If you ship a working integration we’ll add your tile to the homepage Integrations row + the /about Partners section. We can also open a PR into your repo if that’s faster.