# 6. Infrastructure and Security #### 6.1 Why Monad? Monad is a purpose-built, high-performance Layer 1 blockchain designed to support real-time, on-chain applications with unmatched speed and efficiency: * Up to 10,000 transactions per second (TPS), greatly surpassing traditional EVM chains * 1–second block times with single‑slot finality, ensuring speedy and reliable confirmation * Optimistic parallel execution, enabling concurrent transaction processing and retrying if conflicts arise * Server-grade efficiency, allowing operation on modest hardware through MonadDB’s optimized storage * EVM compatibility, supporting existing Solidity contracts and Ethereum tooling with no code changes This stacked architecture—high TPS, rapid confirmation, low cost, and full EVM compatibility—makes Monad uniquely suited to power MAI’s real-time betting and prediction markets with the responsiveness of Web2 platforms while preserving decentralization and trustlessness. #### 6.2 Fully On‑Chain Execution MAI leverages Monad’s performance to run all gameplay logic, betting, settlement, and market resolution directly on-chain. There are no off-chain servers, hidden order logic, or private balances. Every interaction is recorded on-chain, auditable, and trust-minimized. #### 6.3 Security Model * Multiple Security Audits: All smart contracts are independently audited prior to deployment. * Bug Bounty Program: Incentivized vulnerability disclosure alongside mainnet launch. * Transparent Upgrades: Governance-controlled and time-locked, with clear versioning. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.maiprotocol.com/litepaper/6.-infrastructure-and-security.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.