Summary: INTMAX is a privacy-focused Ethereum Layer 2 whose official materials consistently frame it as a stateless, transfer-optimized network rather than a general-purpose smart-contract platform. The homepage, docs, ePrint paper, and GitHub repos all point to the same shape: INTMAX pushes most data and computation client-side, uses block builders and proof infrastructure instead of a classic sequencer-heavy rollup stack, and is optimized for low-cost private token transfers, batch payments, and privacy-preserving payment applications.
What it does:
Provides a stateless Ethereum L2 for private token transfers, batch transfers, and payment-style applications
Uses zero-knowledge proofs and decentralized / permissionless block production to minimize onchain data and computation requirements
Publishes user guides, a developer hub, and infrastructure docs for builders running block builders, validity provers, withdrawal services, and related components
Exposes SDK, CLI, wallet-integration, and repository surfaces for dapps, wallets, and infrastructure operators
Positions products like Privacy Mining, wallet flows, and merchant / payment use cases on top of the core network
Key claims:
The homepage calls INTMAX an “Ultimate Payment Protocol” and describes it as a stateless, privacy-centric Layer 2 on Ethereum built for fast, low-cost, confidential transactions
The docs overview says INTMAX specializes in efficient token transfers, can send multiple tokens to different recipients without extra fees, and intentionally does not center general-purpose smart-contract capability
The Developers Hub emphasizes block builders, validity provers, withdrawal infrastructure, a WebAssembly client SDK, wallet SDK, and payment-lifecycle docs, which is a strong signal that this is operational transfer infrastructure rather than a generic L2 marketing shell
The IACR ePrint paper describes Intmax2 as a ZK-rollup with stateless and permissionless block production that shifts most data and computation costs to the client side
The GitHub org and repo layout corroborate the multi-service architecture with separate repos for the protocol, SDKs, gateway, docs, and supporting proof components
Whitepaper: Yes. INTMAX links to an IACR ePrint paper, “Intmax2: A ZK-rollup with Minimal Onchain Data and Computation Costs Featuring Decentralized Aggregators,” and a local copy is saved as ../whitepapers/intmax-intmax2-eprint-2023-1082.pdf. Current primary-source notes are in ../whitepapers/intmax-primary-sources-2026-04-27.md.