A MetaMask Snap that lets a person type name.agt in the send field and pay the name's on-chain address. It resolves AGT Registry records on Polygon (the name's declared payment wallet, and its owner account when that differs) and answers on the major EVM networks.

Install

Until the Snap is allowlisted in the MetaMask Snaps Directory it installs in MetaMask Flask only. From a dapp or the browser console on a page connected to MetaMask:

await window.ethereum.request({
  method: "wallet_requestSnaps",
  params: { "npm:@agtnames/snap": {} },
});

Then open MetaMask, start a send on Polygon, Ethereum, Base, Arbitrum, Optimism, BNB Chain or Avalanche, and type a name such as launchpad.agt. The resolved address appears with the label AGT Registry.

What it resolves

Network	Entry	Label
Polygon	`agentWallet` (the payment address the owner set)	`AGT Registry`
Polygon	`addr` (the owner account), only when it differs	`AGT Registry (owner account)`
Polygon, no `agentWallet`	`addr`	`AGT Registry`
Ethereum, Base, Arbitrum, Optimism, BNB, Avalanche	`addr(coinType)` for that chain when set (ENSIP-11), else `addr`	`AGT Registry`

Off Polygon, addr is reused only when it is a key-controlled account on Polygon (no code, or an EIP-7702 delegation): a Safe or smart account is not the same account on another chain, so nothing is offered. The payment wallet is a Polygon address and is never offered elsewhere. Lapsed, unregistered or record-less names show nothing, and so does any read failure: the Snap never guesses. Other resolver Snaps may return a legacy record for the same name; look for the AGT Registry label. Reads go straight to Polygon public JSON-RPC endpoints through @agtnames/resolver (two batched round trips, no third-party API). Address → name (reverse lookup) is planned for the next version.

Permissions

endowment:name-lookup for .agt on the seven EVM chains above.
endowment:network-access to reach Polygon JSON-RPC.

No accounts, keys, state or UI. Source: github.com/agtnames/agt (packages/snap).

Development

npm ci
npm run build          # mm-snap build → dist/bundle.js, updates the shasum in snap.manifest.json
npm test               # builds, then jest (@metamask/snaps-jest); AGT_LIVE_TEST=1 adds a mainnet read
npm start              # mm-snap watch + local server on :8023 for Flask (`local:http://localhost:8023`)
npm run manifest:check # fails if the committed shasum does not match the bundle

Releases: tag snap-v* in agtnames/agt; every new version must be re-submitted to the Snaps Directory before non-Flask users can install it.