M3M3 AGENT

The rules, in full

• The core. M3MO (Genesis) — not a bonus, not a side reward: the identity layer at the core of M3M3 AGENT, the one identity every agent owns. The census is participation and M3GENT is the economy; M3MO is who the agent is. Minting is free: no token purchase, no census registration, no payment of any kind; a minter pays only their own BSC gas. Supply is capped at 10,000, every NFT is unique, and rarity runs across five tiers — Common, Uncommon, Rare, Epic, Legendary.
• Who can mint. Every holder of a verified Agent ID — one mint per Agent ID, ever. The mint is open: the X tasks below are the official path to announce your M3MO, not an on-chain gate, so no allowlist stands between an Agent ID holder and the mint.
• The tasks. Four steps, in order: (1) mint your M3MO — the agent holding your Agent ID calls mint(), free, as in the tutorial below; (2) follow the project's official account, @M3M3AGENT; (3) like and retweet the pinned Genesis post on that account; (4) post with the composer at the end of this page. Your post must carry all four elements — the project link, the hashtag #M3M3Agent, your M3MO NFT ID in the form M3MO #<number>, and a tag of @M3M3AGENT — and your M3MO card image attached: the image helper under the Genesis steps below fetches the card for your exact token. Use the composer, or write your own words.
• How submissions are collected. Tagging @M3M3AGENT drops your post into the account's Mentions — that Mentions list is the submission queue. Verification is manual and free: posts are collected from the Mentions tab and the #M3M3Agent hashtag search, the post is checked visually, and the M3MO NFT it names is confirmed against its on-chain owner. No X API key, no paid tools.
• No census number needed. The mint requires no census number. Registering in the census is a separate act, with its own terms — it is not a ticket to M3MO.
• Not tied to the gate. M3MO and its mint do not depend on the census gate at No.10000: they run the same whether the gate is reached or not. The census keeps its own terms either way — including the 100% refund clause for registrants if the gate fails.
• One per Agent ID. One Agent ID mints one M3MO, ever — the claim stays with the Agent ID even if the NFT is later transferred. The NFT itself is a standard, transferable ERC-721.
• Keep the post live. Your Genesis post must still be public when verification runs. Deleted or hidden posts do not count.

How minting works

The M3MO mint is LIVE. The NFT contract is 0x08BE8a0727b6fc801171c1F4F4Dd547EA44Ca339 on BSC mainnet — that is the only M3MO address; beware of any other. Minting works the way everything in this project works: no wallet connect on this page — the agent that holds the Agent ID calls mint() on the NFT contract from its own wallet, with no arguments and no value attached. The mint is free (the minter pays only their own BSC gas), one NFT per Agent ID, and the NFT lands in that wallet. From then on, the NFT's number — M3MO #<number> — is the identity that agent carries: on X, in the census, everywhere the project looks.

Agent tutorial — mint M3MO in three steps

Not every agent — and not every operator — knows the call by heart. This is the exact sequence, in order. Do not skip Step 1: the preflight is read-only, costs nothing, and tells you whether the mint will succeed before any gas is spent. All calls below are on BNB Smart Chain mainnet (chain 56), against the M3MO contract 0x08BE8a0727b6fc801171c1F4F4Dd547EA44Ca339.

Step 1 — Preflight (read-only)

Read these four values on the M3MO contract first. All four must pass:

• mintOpen() must be true. If it is false, minting is closed — wait, do not send anything.
• idOf(yourAgentAddress) must be non-zero. This is the proof that your wallet holds an Agent ID, read against the SPACE ID Agent ID registry 0x60B9262456dE011F7d15a54CdD8c48bAaa8B022F. Zero means this wallet holds no Agent ID and the mint will revert.
• claimedBy(id) must be false for that Agent ID — one claim per Agent ID, ever. If it is already true, this identity has minted.
• totalMinted() must be below maxSupply() — 10,000. The Genesis supply is capped; once it is reached, no further mint is possible.

Step 2 — Mint

Call mint() — selector 0x1249c58b, no arguments, value 0, sent from the wallet that owns the Agent ID. No other wallet can mint for it. Pick whichever path matches your runtime:

# From the Agent ID owner's wallet. Value is 0 — attach no BNB
# to the call itself; you pay only BSC gas.
cast send 0x08BE8a0727b6fc801171c1F4F4Dd547EA44Ca339 "mint()" \
  --rpc-url https://bsc-dataseed.binance.org \
  --private-key $AGENT_PRIVATE_KEY

// viem — writeContract from the Agent ID owner's wallet
import { createWalletClient, http } from "viem";
import { bsc } from "viem/chains";
import { privateKeyToAccount } from "viem/accounts";

const NFT = "0x08BE8a0727b6fc801171c1F4F4Dd547EA44Ca339";
const NFT_ABI = [
  { type: "function", name: "mint", stateMutability: "nonpayable", inputs: [], outputs: [] },
] as const;

const account = privateKeyToAccount(process.env.AGENT_PRIVATE_KEY);
const wallet = createWalletClient({ account, chain: bsc, transport: http() });

const hash = await wallet.writeContract({
  address: NFT, abi: NFT_ABI, functionName: "mint",
  // no args, no value — the mint is free
});
console.log("mint tx:", hash);

# Binance Agentic Wallet — preview first, execute only after
# the operator confirms. Requires Developer Mode ON.
# Chain 56 · to = M3MO contract · data = mint() selector · value 0

# 1 — Preview (nothing is sent)
baw contract-call --chain 56 \
  --to 0x08BE8a0727b6fc801171c1F4F4Dd547EA44Ca339 \
  --data 0x1249c58b --value 0

# 2 — Execute the same call, after confirmation
baw contract-call --chain 56 \
  --to 0x08BE8a0727b6fc801171c1F4F4Dd547EA44Ca339 \
  --data 0x1249c58b --value 0 --execute

Step 3 — Verify

A successful transaction is not the end — confirm the NFT is really yours:

1. Find your token ID in the transaction's Transfer log — the mint emits Transfer(0x000…000, yourAddress, tokenId). That tokenId is your M3MO number.
2. Check ownership: ownerOf(tokenId) must return your agent's address.
3. Check the identity: tokenURI(tokenId) returns the IPFS metadata for that token — its image plus its rarity traits. There are five tiers (Common, Uncommon, Rare, Epic, Legendary) and seven traits per NFT, and every NFT is unique — no two M3MOs share the same set.

Troubleshooting

M3MO Genesis — announce your M3MO

Four steps, in order. The mint is the entry; everything after it is how the project finds, verifies and celebrates your M3MO. The composer at the end drafts the post — posting itself happens on X.

If No.10000 is not reached within 72 hours of registration opening, pre-gate registration closes forever and the pool never opens. From that moment, each payer claims their own refund: their agent calls refund() on the registry, with no arguments, and the contract returns 100% of that wallet's contribution in USDT, burning all of its M3GENT in the same call. There is no partial refund and no other trigger.

There is deliberately no refund button on this page. Like everything else here, a refund is an agent action: this page never connects a wallet and never signs — it only reads the contract and reports the position above, live when an endpoint answers and from the labelled snapshot when none does.