---
name: botblock
description: Read BOTBLOCK Genesis deployment status and use its read-only preflight. Minting remains blocked while production deployment or committed metadata is missing. Never execute the retained legacy class-based ABI.
---

# BOTBLOCK Genesis agent interface

Read `/config.json` from this exact origin first. **While status is preview or the live collection address, verified runtime hash, production metadata or actual mint terms are absent, stop with `deployment_pending`.** Do not prepare, simulate, sign, submit or claim a public-chain mint from the local test results.

The new `BotblockGenesis.sol` implements a 4,096-item collection using payable **`mint()` with no arguments**. Source: `/agent/BotblockGenesis.sol`; ABI: `/agent/genesis-abi.json`; selectors: `/agent/genesis-interface.json`; read-only CLI: `/agent/genesis-preflight.mjs`, with its companion `/agent/crypto.mjs`. Local validation results are `/agent/local-validation.json`. This implementation is not deployed, externally audited, or proven against actual oracle delivery and wallet approval.

The website is read-only. Five rarity artworks define Core, Relay, Prism, Monolith and Singularity. Slots sharing a rarity share its artwork. Catalog IDs are metadata editions, not minted token IDs. The local preview catalog uses localhost image URLs and must not be committed as production metadata.

## Live mint verification, once deployment is published

1. Require BNB Smart Chain, chain ID 56, a matching verified deployed runtime, the new no-argument ABI and independently verified registry/coordinator provenance. Never use `/agent/BotblockWorkshop.sol`, `/agent/abi.json`, `/agent/interface.json` or `/agent/preflight.mjs`: those are legacy prototype references.
2. Use `genesis-preflight.mjs` with only the public signing-wallet address and the public launch configuration URL. It reads immutable price, timing, cap, treasury, registry, metadata commitment and VRF parameters. It downloads the manifest, checks its actual byte hash against the contract/config, verifies 4,096 ordered editions, exact rarity quotas and content-addressed artwork references. Content availability and image hash provenance must also be independently verified before launch.
3. Recheck `.ai` ownership, unconsumed wallet quota, sale opening/closure, remaining supply, exact native mint fee and available gas balance. Simulate `mint()` and estimate the exact call. No ERC-20 approval or NFT operator approval is required.
4. Show the exact recipient, chain, native value, gas estimate and irreversible reveal rules. Obtain explicit approval through the official Agentic Wallet flow before submission. Copying instructions is not approval. Recheck state if approval is delayed.
5. Confirm the receipt and owner of the actual minted token. Do not infer a chosen rarity or equate its token ID with a preview catalog ID.

The supported Binance claim-status check is `baw wallet agent-id --json`; a service error is not proof of no identity. A `.ai` name is claimed in the Binance App. The contract checks the actual signing wallet's NFT balance, not website login, unique human identity or independent AI reasoning. Custom wallet calls require the user's supported official approval flow; never change Developer Mode, wallet controls or spending limits on their behalf.

## Reveal boundary

No rarity is selected at mint. Mint closes automatically at sellout or the immutable deadline. Anyone may request one reveal only after closure and nonempty supply. The fixed coordinator's matching asynchronous callback records a single seed, including zero. The deterministic eight-round Feistel permutation maps token IDs to ordered manifest slots. Full-catalog quotas are Common 2,048, Uncommon 1,024, Rare 640, Epic 256, Legendary 128; a partial-sale subset can have different counts.

The request uses Chainlink VRF v2.5 interfaces with a custom immutable-coordinator adapter, not the migratable official ConsumerBase. There is no owner reroll, cancel, seed setter, reopen or coordinator migration. VRF subscription funding is external to mint revenue. An unavailable coordinator or an accepted unfulfilled request has no administrative reroll fallback. Any future request transaction requires its own wallet preview and approval; do not silently request randomness or invent a seed.

The CLI never signs or sends. Never request private keys, seed phrases, cookies, credentials, token approvals or activation payments. The website and reference endpoints are publicly accessible. If a required endpoint returns a login gate or permission error, stop rather than borrowing the user's login. Public website access does not authorize minting before a verified collection deployment.

References: [Agentic Wallet](https://web3.binance.com/en/dev-docs/products/agentic-wallet/introduction), [Agent ID status](https://github.com/binance/binance-skills-hub/blob/main/skills/binance-web3/binance-agentic-wallet/references/agent-id-claim-status.md), [VRF security](https://docs.chain.link/vrf/v2-5/security).