Abstract
Context before execution.
Web3 interfaces often ask users to act before they can inspect what is connected, which network is active, or where an action will lead. Mutilprotocol starts from the opposite premise: context comes before execution.
The interface is intentionally narrow. It establishes a user-controlled wallet connection, identifies the active network, and can ask the wallet to switch to BOT Chain Mainnet through an explicit approval flow. The Open Relay collection is deployed on BOT Chain at 0xc43f21d0a519274a7f3fb9f6abb08ae3ffcc21d2. Its source is verified in BOTScan, but has not been independently audited. Its artwork and all 334 metadata files are IPFS-pinned and byte-verified, the contract base URI is irreversibly frozen at ipfs://bafybeih2fnbpkycdf7f53eqc5iv4lua3fmd7lcfz4fslmq5g4n4idihofu/, and public mint is live at 0 BOT plus BOT Chain network gas. Supply is capped at 333 with one lifetime mint per wallet.
Design principles
Claims follow evidence.
Wallet sovereignty
Private keys and recovery phrases remain with the user’s wallet. Mutilprotocol never asks for either.
Context before action
Network, account, permissions, and future contract interactions should be visible before a user is asked to approve anything.
Progressive disclosure
A capability is not described as live until its implementation, dependencies, and risk surface can be plainly stated.
Verifiability over narrative
Published addresses, source verification, review scope, and explorer references matter more than untestable claims.
Current capability and scope
A deliberately small permission surface.
The core interface requests only the permissions needed to establish account and network context. Open Relay public mint is live, but the interface never signs on behalf of a wallet: every mint requires an explicit wallet confirmation and BOT Chain gas. Connecting a wallet alone does not move funds or grant Mutilprotocol custody.
Collection configuration
Rules are published for the live mint.
Mutilprotocol — Open Relay is a deployed ERC-721 collection on BOT Chain Mainnet 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. The contract base URI is irreversibly frozen at ipfs://bafybeih2fnbpkycdf7f53eqc5iv4lua3fmd7lcfz4fslmq5g4n4idihofu/, and public mint is live at 0 BOT plus BOT Chain network gas.
Public mint is active at a contract price of 0 BOT; the user still pays BOT Chain network gas. The 333-token supply and one-lifetime-mint-per-wallet rule are enforced by the contract, but an address limit does not prevent participation through multiple wallets.
Reference architecture
A narrow trust boundary by design.
The wallet is the signing authority and approval boundary. Mutilprotocol acts as a browser client: it requests account access, reads the active chain, can request that the wallet switch to or add BOT Chain, and presents the disclosed state of the deployed collection. The wallet—not Mutilprotocol—controls whether any request is accepted.
Network parameters align with the BOT Chain Quick Guide .
Security model
Security is a practice, not a badge.
Private-key separation
Mutilprotocol does not store, transmit, or request private keys, recovery phrases, or wallet passwords.
Permission minimisation
The core interface is limited to wallet connection, network context, disclosed collection state, and the public mint. Every mint requires explicit confirmation in the user’s wallet and BOT Chain gas.
Published release boundary
The source is verified but not independently audited. The IPFS artifacts are byte-verified, the pinned metadata root is irreversibly frozen on-chain, and the public mint is active at 0 BOT plus network gas with published supply and wallet limits.
Verify the domain, inspect every wallet prompt, and never share a recovery phrase. A wallet prompt is an approval request, not a guarantee of safety.
Directional roadmap
Capability expands only with public evidence.
Foundation
Public scope, EVM wallet connection, BOT Chain network switching, and baseline security disclosure.
Verifiable context
Read-only network context, official-source references, integration provenance, and developer information architecture.
Transaction safety
Open Relay is deployed with verified source, IPFS-pinned byte-verified artwork and metadata, and an irreversibly frozen on-chain metadata root. Public mint is active at 0 BOT plus network gas, with a maximum supply of 333 and one lifetime mint per wallet.
Open interface
Builder documentation, composable interface primitives, and a published process for protocol-change proposals.
The roadmap describes direction, not a delivery guarantee. Dates and features may change as technical, security, and ecosystem dependencies are evaluated.
Disclaimer
Read this as a product brief, not financial advice.
This paper is provided for informational and product-design purposes only. It is not an offer, solicitation, recommendation, or advice to buy, sell, hold, or use any digital asset.
Mutilprotocol does not provide custody, brokerage, investment, legal, or tax services. The browser interface never holds credentials or signs on behalf of a wallet. 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; the contract base URI points to ipfs://bafybeih2fnbpkycdf7f53eqc5iv4lua3fmd7lcfz4fslmq5g4n4idihofu/, and metadata is irreversibly frozen. Public mint is active at 0 BOT plus network gas, capped at 333 tokens and one lifetime mint per wallet. Deployment and source verification do not constitute a security audit or a recommendation to interact. Interactions with third-party wallets, RPC endpoints, explorers, and ecosystem applications remain subject to their own terms, security models, and availability.
Never share a wallet recovery phrase or private key with any person, website, or application.