Docs

Overview

Flaggies is a collection of 5,555 pixel art characters, one family drawn for all 195 countries. Each character wears its country's colors and stands in front of a landmark from home.

Each Flaggie's traits name its Base (Male, Female, the robot's finish, or the animal's species, in gold for a Legendary) and its Tier. Each of the 95 countries with a Legendary has exactly one, so they carry Tier 1/1.

The contract is a standard ERC-721 on BNB Chain with ERC-2981 royalties and ERC-4906 metadata updates. Every image is 32 × 32 pixels, stored at 1024 × 1024 on IPFS.

What you need

• A Binance Agentic Wallet. Minting is a contract call made by your AI agent through this wallet.
• A .ai Agent ID in that wallet. The contract checks that the calling wallet holds an Agent ID from the SPACE ID collection. The Agent ID is soulbound, so it cannot be borrowed for a mint.
• Developer Mode turned on in the Binance app. The wallet needs it for any contract call.
• A little BNB for gas, plus the mint price: ???.

Install

The easiest route is to hand your agent the skill file. It tells the agent which commands to run and when to ask you first. The skill and the Flaggies CLI are published when the mint opens, with the SHA-256 of each release so you can check the file before installing it. Follow @flaggies_world to hear first.

The wallet side you can set up now:

npm i -g @binance/agentic-wallet

The Flaggies CLI never holds keys. It reads the chain and prepares calls, and every signature goes through your Agentic Wallet.

Commands

Every command prints JSON. A good agent turns it into plain language for you.

Mints and reveals always go preview, then your confirmation, then execute. A preview expires after about five minutes.

Mint rules

• Price: ??? The price is fixed in the contract and cannot be changed.
• ??? per wallet, counted by mints. Selling a Flaggie does not give the wallet room for another.
• Tokens mint in order: 1, 2, 3 and so on. Your token id says nothing about the artwork it will show.
• Overpayment comes back in the same transaction. The CLI sends the exact cost anyway.
• The mint can be paused and reopened by the owner until it closes. Once it closes, it is closed for good.

The reveal

Until the reveal, every token shows the same silhouette. The artwork is dealt in one step, for all tokens at once.

1. The mint closes. Either the last Flaggie is minted, or the owner calls endMint. From then on nobody can mint, the owner included.
2. The reveal block is set five blocks ahead. Its hash does not exist yet when the mint closes, so nobody can know it.
3. Anyone calls reveal() once that block has passed. The block hash fixes a random offset, and token t shows original artwork (t − 1 + offset) mod 5555 + 1.

The hash stays readable for 8,191 blocks, about an hour on BNB Chain. If nobody calls reveal() in that window, the next call arms a new reveal block instead of guessing. There is no fallback seed, because any value known in advance could be gamed by whoever closes the mint.

After the reveal, originalIdOf(tokenId) on the contract tells you which image file your token shows.

Market

Flaggies has its own market contract, built for agents. Every action is one contract call, so the same preview, confirm, execute flow as the mint applies.

• Every sale pays the royalty that Flaggies reports (???) and sends the rest to the seller. The market itself charges nothing.
• Offers hold their BNB in the market until they are accepted or cancelled. Every offer expires, after 90 days at most, and anyone can then refund it to its bidder.
• Closing the mint resets the book. About two seconds after the close, anyone can work out which token got which artwork, before the reveal is on chain. So listings and offers made before the close (while the mint is open, paused or not yet open) stop working at the close, and the market takes nothing new until someone runs flaggies reveal. List or offer again after that. BNB in an old offer comes back at any time with cancel-offer (flaggies market --mine shows the id), or anyone can refund it.
• Every listing expires, after 90 days at most. To stop a sale sooner, unlist it. Don't rely on moving the token or revoking approval: if either comes back before the expiry, so does the listing.
• A listing only works while the seller holds the token. If it moves, the listing can't be bought, and anyone can clear it.
• Buyers send the exact listed price. If the price changes while a purchase is pending, the purchase fails instead of paying a different amount.
• The market has no owner. Nobody can pause it, change its rules or touch the BNB it holds for offers. The only pause is the one above, between the close and the reveal, and it is written into the contract.

The live book is on the Market page. Flaggies are standard ERC-721 tokens, so other BNB Chain marketplaces can list them too.

Verify the art

The contract was deployed with a provenance hash of all 5,555 images in their original order. The images go public at the reveal, under an IPFS folder address (CID) published here. Then anyone can recompute the hash:

curl -o images.car "https://ipfs.filebase.io/ipfs/<images CID>?format=car"
npx ipfs-car unpack images.car --output images
cd images
for i in $(seq 1 5555); do sha256sum "$i.png" | cut -c1-64; done | tr -d '\n' | sha256sum

The result must equal the provenance() value on the contract:

3830c2b685170b48a3d22ac15cbc0dd37c31da3901417b2f4b5559f13166abf9

Any IPFS gateway or node works in place of the one above, since the folder is addressed by its content.

Owner powers

The contract has an owner. Here is everything the owner can do, and the limits the contract puts on it.

The owner cannot change the price, the supply or the provenance hash, mint for free, choose the reveal offset, or move anyone's token.

The revealed metadata lives on IPFS and the owner sets its address. Anyone can rebuild the expected metadata from the on-chain offset and the provenance-checked images, and compare it before the metadata is frozen.

Errors

Addresses

The contract addresses are published here when the mint opens. Until then, an address that claims to be Flaggies is not ours.

Provenance

0x3830c2b685170b48a3d22ac15cbc0dd37c31da3901417b2f4b5559f13166abf9

Chain

BNB Chain, id 56