Protocol principle
Wallet-controlled access
Connection happens through the user’s own injected EVM wallet. Private keys, recovery phrases, and custody remain outside this interface.
BOT Chain interface
Make the networklegible.
Mutilprotocol is a browser interface for establishing wallet context and moving deliberately into BOT Chain Mainnet.
Open Relay is deployed on BOT Chain at 0xc43f21d0a519274a7f3fb9f6abb08ae3ffcc21d2. Its source is verified in BOTScan, but has not been independently audited. Artwork and all 334 metadata files are IPFS-pinned and byte-verified; metadata is irreversibly frozen at ipfs://bafybeih2fnbpkycdf7f53eqc5iv4lua3fmd7lcfz4fslmq5g4n4idihofu/. The public mint was activated in block 19,295,008 and is live at 0 BOT plus BOT Chain network gas, with 333 tokens maximum and one lifetime mint per wallet. The interface does not custody assets or hold private keys.
Wallet accessBOT Chain
Wallet-held authorityInjected EVM provider
Network-aware contextBOT Chain · 677
Explicit wallet requestSwitch or add network
Scope, not spectacleNon-custodial browser clientBOT Chain Mainnet · 677Network metadata is inspectable
Protocol thesis
A deliberately narrow starting point.
The interface is designed around a simple rule: users should be able to see their context before they are asked to do anything with it.
Protocol principle
Context before action
The active account and chain are established before a wallet action is prepared. Open Relay public mint is live on BOT Chain at 0 BOT plus network gas, with 333 tokens maximum and one lifetime mint per wallet. Its IPFS metadata is irreversibly frozen.
Protocol principle
Verifiable scope
A capability is described as live only when its boundary can be inspected. Today that boundary includes wallet context, BOT Chain configuration, and a live public mint backed by verified source and frozen metadata. Verified source is not an independent security audit.
Mutilprotocol Paper
Current capability, stated without ambiguity.
Read the product and network entry brief for the current boundary, the live public-mint rules, and the risks that remain outside the interface.
Reference architecture
A narrow trust boundary by design.
The wallet remains the signing authority. Mutilprotocol reads context, submits explicit network requests, and presents the deployed collection state without taking custody or approving transactions for a user.
Architecture layer
Access is the focus.
Connect an injected EVM wallet and request a move to BOT Chain Mainnet. The wallet remains the approval boundary for every transaction; the interface never holds private keys or approves requests on a user’s behalf.
EIP-1193 provider · user approval requiredInterface boundary: Open Relay is deployed at 0xc43f21d0a519274a7f3fb9f6abb08ae3ffcc21d2 on BOT Chain. Its source is verified, but has not been independently audited; its artwork and all 334 metadata files are IPFS-pinned and byte-verified, the contract points to ipfs://bafybeih2fnbpkycdf7f53eqc5iv4lua3fmd7lcfz4fslmq5g4n4idihofu/, and metadata is irreversibly frozen. Public mint is live at 0 BOT plus network gas, capped at 333 tokens and one lifetime mint per wallet. No bridge, exchange, or custody flow is available.
Network reference
BOT Chain, presented as a configuration.
The wallet utility uses the published Mainnet metadata below. Network choice and approval remain in the user’s wallet.
- Network
- BOT Chain Mainnet
- Chain ID
- 677 · 0x2a5
- Compatibility
- EVM-compatible
- Native gas asset
- BOT
- Explorer
- scan.botchain.ai
Open Relay collection
A single relay, prepared in the open.
Mutilprotocol — Open Relay is a fixed ERC-721 collection shaped around network context, explicit authority, and a boundary that stays visible before any claim can begin.
- Inspectable termsSupply, limit, owner, plus IPFS-pinned, byte-verified, and irreversibly frozen metadata are disclosed.
- Wallet-held actionsEvery deployment or mint request is approved in the user’s wallet.
Open RelayDeveloper entry
Build against facts, not promises.
Mutilprotocol is documenting the network boundary first. Future integrations will be described only after their sources, dependencies, and permissions can be independently checked.
Network setup
Use the published BOT Chain metadata.
Open official quick guideChain inspection
Verify public chain state in the explorer.
Open BOTScanDocumentation
Read the disclosed interface direction.
Read Mutilprotocol PaperDirectional roadmap
Progress is a series of disclosed boundaries.
These stages describe direction, not a delivery guarantee. A future capability moves forward only when its technical and security conditions can be made public.
Foundation
Public scope, injected-wallet connection, and BOT Chain Mainnet switching.
- Mutilprotocol interface
- EVM wallet context
- Network configuration disclosure
Verifiable context
Read-only ecosystem information with clear source and explorer references.
- Network reference layer
- Source provenance
- Developer information architecture
Transaction safety
Open Relay public mint is active at 0 BOT plus network gas. Its IPFS artwork and 334 metadata files are byte-verified, the pinned metadata root is live on-chain, and metadata is irreversibly frozen. Supply is capped at 333 with one lifetime mint per wallet.
- Human-readable action previews
- Published addresses and ABI versions
- Permission and risk disclosure
Open interface
Documentation and interface primitives for ecosystem builders, subject to a public specification.
- Builder documentation
- Composable interface standards
- Change-proposal process
Mutilprotocol Paper
Start with the boundary.
The paper explains what this interface does, what it does not do, and what must be verifiable before its scope expands.