Planned access uses a registered .ai identity on the minting wallet.
BOTBLOCK GENESIS
4,096 blocks.
One Genesis.
Five block sculptures. A planned 4,096-piece edition on BNB Smart Chain, designed for .ai agents.
NETWORK VIEWGenesis / 01
ILLUSTRATED PREVIEW
Rendering district
56 / GENESIS / 0001
BOTBLOCK NETWORK
CoreRelayPrismMonolithSingularity
LIVE CHAIN STATUS / CONCEPT NETWORK
Five planned rarity tiers. One original mint per eligible wallet.
At launch, an agent prepares the call for your wallet approval.
Final traits and token assignment are revealed after mint closes.
GENESIS / COLLECTION PREVIEW
The collection.
Explore the five forms, then browse their planned editions.
GENESIS / EDITION DESIGN
Built to be collected.
4,096 planned pieces. Five rarity tiers. Five distinct forms.
GENESIS COLLECTIONLEGENDARY / 128
Singularity.
Legendary.3D ART STUDY
Legendary.3D ART STUDY
MAXIMUM EDITION4,096ERC-721 / BNB Smart Chain
Planned counts for the full catalog. If fewer than 4,096 are minted, the revealed circulating counts will differ. Tiers describe this collection’s design, not a marketplace rank.
THE FIVE FORMSOriginal artwork by rarity
Common2,048
Uncommon1,024
Rare640
Epic256
Legendary128
Shape. Material. Core.
Each tier has its own silhouette: Core, Relay, Prism, Monolith, and Singularity. Materials, construction, and detail change with the form.
Mint first. Reveal later.
Agents will mint an unassigned NFT. The planned reveal assigns the final artwork and rarity after mint permanently closes.
The final set gets locked.
The contract fixes the manifest hash and metadata URI at deployment. Local reveal tests pass; production content-addressed metadata still needs to be published and verified.
Five original artworks define the rarity tiers. Catalog slots in the same tier share its artwork. Final metadata and token assignments are not committed yet.
Browse previewAGENT ACCESS / PREVIEW
Made for .ai agents.
See how agent access is planned to work. Mint is closed.
Mint stays closed.
Project statusThis page is for preparation. No launch date or price is set, and this website cannot sign or submit a transaction.
BOTBLOCK / AGENT SESSIONBSC 56
COLLECTIONGENESIS / 4,096
Ask your agent to explain the preview. This brief does not request a mint.
Skill and contract interface +
- Skill
- /agent/skill.md
- Preview configuration
- /config.json
- Genesis source
- BotblockGenesis.sol
- Read-only preflight
- genesis-preflight.mjs
- Target mint call
- mint() · not deployed
- Signing
- Agentic Wallet confirmation
PLANNED FLOW / AVAILABLE AFTER LAUNCH
01
Verify
Read deployment, .ai eligibility, price, and supply.
02
Simulate
Simulate the collection mint and estimate gas.
03
Approve
Review the exact call in your Agentic Wallet.
NETWORK & OWNERSHIP
Network activity.
Public BSC data refreshes automatically. Mint records require the live contract and indexer.
Mint & transfer records
NO DEPLOYMENT| TOKEN | EVENT | WALLET | CHAIN BLOCK |
|---|
No on-chain blocks yet.
The contract is not deployed. This view will use confirmed chain events, not sample activity.
PROJECT STRUCTURE
The project guide.
The collection, agent access, and what comes next.
A collection built around the block.
BOTBLOCK explores five sculptural forms: Core, Relay, Prism, Monolith, and Singularity. Graphite, glass, gold, and light give each rarity its own shape.
5Artwork forms
4,096Planned editions
BSCTarget network
Can I mint right now?
No. We are building the website and refining the collection. Mint is closed. A launch date and price have not been set.
Are there 4,096 different images?
The current preview contains five artworks, one for each rarity. Pieces in the same tier share that artwork. The 4,096 figure is the planned edition size, not a count of unique images. The final artwork set is still to be decided.
Why does BOTBLOCK use Agent ID?
The planned mint flow runs through an agent using a wallet with a registered .ai identity. The on-chain check verifies identity ownership; it cannot prove that an AI made the decision. There is no browser mint button.
Can an agent choose a rarity?
No. Under the planned reveal, minting comes first and rarity is assigned after mint permanently closes. The rarity page shows the proposed full-edition distribution.
Does the network view show owned NFTs?
It is an interactive illustration. The modules are not land plots, reservations, or proof of ownership. Real ownership records need the deployed collection and its event indexer.
Do I need to connect a wallet to explore?
No. Gallery, rarity, and project information are public. The optional Agent ID lookup only needs a public wallet address and requests no signature.
Six parts. One mint flow.
01WebsiteNetwork, artwork, status
02Agent skillInstructions and preflight
03Agentic WalletIdentity and confirmation
04NFT contract.ai gate and ownership
05IndexerConfirmed event records
06Network stateToken and owner display
On-chain and local state
The collection plan separates catalog slots from minted tokens. The Genesis contract stores ownership and mint quotas, then assigns committed metadata through its one-shot reveal. Gallery IDs are preview references; they are not minted token IDs.
Indexer implementation +
The existing Worker and D1 implementation is a prototype. Its event schema must be updated for the collection contract before deployment. A dedicated log-capable BSC RPC will supply confirmed mint and transfer records; RPC keys stay in the backend.
Mint through the agent.
There is no browser mint or browser transaction signing. At launch, your agent will read the skill, check your .ai wallet, simulate minting, and use the official Agentic Wallet contract-call flow. You approve in your wallet. While deployment is pending, the agent must stop before preparing a transaction.
The on-chain rule is .ai ownership. A registry check is an identity gate; it does not independently prove that an AI made the decision.
Wallet compatibility
Binance Agentic Wallet custom calls require Developer Mode and explicit confirmation. Plain-text wallet signatures are not part of BOTBLOCK's flow.
- Target entry point
- mint() · locally tested
- Identity gate
- Configured .ai NFT registry
- Quota
- One original mint per eligible wallet
- Chain
- BNB Smart Chain, 56
- Funds
- Exact published mint fee plus gas
Building the website first.
The website is public. Mint is deliberately closed while the collection and visitor experience are refined. There is no announced launch date.
WEBSITEPublic preview
Design and interactions are being refined.
MINTClosed
No transactions or reservations.
Next decisions
Finalize the artwork editions, usage rights, mint terms, and official community channels. Technical deployment comes after those decisions.
Launch requirements
Collection gallery & planned rarityBUILT
Final collection metadata & artwork commitmentNOT COMMITTED
Collection mint & reveal contractLOCALLY TESTED
VRF mock, reveal & allocation testsPASSED
Registry verification on target chainREQUIRED
Mint price, treasury & opening timeNOT SET
Verified BSC deploymentNOT DEPLOYED
Indexer RPC, database & serviceNOT DEPLOYED
Public skill & configurationAVAILABLE
LOCAL VALIDATION / GENESIS V1
16 / 16Contract scenarios passed
4,096Unique local mint wallets
12,384Assignment comparisons
0 BNBSpent on public chains
Mock reveal and read-only BSC-state fork checks passed. The successful fork mint uses an explicitly mocked identity. This is not a live collection or a security audit.
The website and agent reference files are public. Mint remains unavailable until the verified BSC deployment, final metadata, and production mint terms are published.
The new Genesis implementation has passed local integration tests. The old profession-based contract remains a legacy reference. Local results do not establish live VRF delivery, Agentic Wallet approval or an external security audit.
Official sources.
Binance Agentic WalletMPC wallet, Developer Mode, supported signingAgent ID and Binance AI Pro.ai claim, wallet binding, identity rulesERC-8004Agent identity, reputation, and validationBNB Smart Chain RPCPublic endpoints and event-indexing limitsOpenSea metadataArtwork and visual trait formattingChainlink VRF 2.5Reveal inputs, request handling, and randomness safetyBOTBLOCK skillProject instructions and deployment checks