What are the core differences between Manta Pacific and Manta Atlantic?

In a modular blockchain architecture, the execution layer and identity layer are often difficult for a single chain to support optimally at the same time: application deployment demands EVM compatibility and low-cost DA, while compliant identity requires privacy addresses and verifiable credentials. Manta Network positions Pacific as an Ethereum-side ZK application execution chain and Atlantic as a Polkadot-side identity credential chain, creating a complementary structure of "scaling execution + privacy compliance."

From a developer and user perspective, the Pacific side reduces ZK dApp deployment costs through Universal Circuits and Celestia DA; the Atlantic side enables selective disclosure via zkAddress and Prove Key, allowing DeFi, social, gaming, and other scenarios to complete verification without exposing the original identity. Understanding the boundary between these two chains is essential for reading Manta Network technical materials.

What Is Manta Pacific?

Manta Pacific is a modular Layer 2 (L2) network deployed by Manta Network on the Ethereum ecosystem, designed as a scalable, low-cost on-chain execution environment for ZK decentralized applications. Pacific decouples transaction execution, settlement, and data availability (DA), adopting Celestia as the DA layer. It reduces on-chain data costs through Data Availability Sampling (DAS) and Namespaced Merkle Trees (NMT). The execution layer follows an EVM-compatible path, with the target architecture being a zkEVM Validium based on Polygon CDK.

Pacific network gas is denominated in ETH, allowing developers to deploy Solidity contracts in an EVM-compatible environment and add zero-knowledge functionality to applications via Universal Circuits. Fast finality uses a two-layer verification framework combining Symbiotic Restaking and Babylon, compressing finality time to minutes. The Pacific ecosystem now hosts over 200 application projects, covering DeFi, on-chain gaming, social, identity verification, and more.

The table above shows that Pacific's technical focus is on "modular scaling + EVM compatibility + ZK application deployment," rather than underlying on-chain identity credential infrastructure. Sequencer revenue and DA cost savings are partially redirected to ecosystem building. On the Pacific side, MANTA is primarily used for governance, ecosystem incentives, and participating in fast finality through Restaking.

What Is Manta Atlantic?

Manta Atlantic is a ZK Layer 1 (L1) network deployed by Manta Network on the Polkadot ecosystem, positioned as a modular on-chain compliant identity infrastructure. Atlantic prioritizes building a zero-knowledge compliance credential layer, enabling other projects to integrate interoperable identity without having to handle complex cryptographic implementations themselves. zkAddress and zkSBT form the core toolset of Atlantic's identity layer, providing UTXO-style privacy addresses and non-transferable on-chain credentials, respectively.

Atlantic network fees are denominated in MANTA, and security is maintained by collators. The network fee distribution structure is: 72% allocated to ecosystem projects, 18% to the treasury, and 10% awarded to collators. Atlantic supports governance voting and collator staking delegation. The purchase and verification of zkSBT and zkKYC credentials use MANTA as the medium. Atlantic's technical roadmap traces back to Polkadot privacy parachain practices, providing a unified credential standard for cross-project identity verification under an interoperable architecture.

The core value of Atlantic lies in "programmable compliant identity," rather than high-throughput application execution. zkSBT is non-transferable, with its core use being privacy verification rather than asset trading or circulation; zkAddress is oriented toward selective disclosure of compliant identity, fundamentally different from coin-mixing privacy tools in terms of mechanism and purpose.

How Do the Two Chains Divide Labor and Collaborate?

Manta Network employs a dual-chain division-of-labor architecture, splitting heterogeneous requirements across two independent networks: Pacific handles large-scale deployment and modular scaling of ZK applications on the Ethereum ecosystem; Atlantic handles on-chain compliant identity and credential layer construction on the Polkadot ecosystem. The two chains are connected via the Celer bridge for MANTA cross-chain locking and unlocking. They share a genesis total supply of 1 billion MANTA tokens but independently maintain block production, consensus, and security models.

The architectural division follows a complementary logic of "application execution + identity compliance." Pacific addresses the question: "How to run ZK applications at low cost on the Ethereum ecosystem?" Atlantic addresses: "How to complete on-chain compliant identity verification without exposing sensitive information?" Universal Circuits is only available on the Pacific side for ZK development capabilities. The core implementations and credential standards of zkAddress and zkSBT are anchored on Atlantic, and Pacific applications can achieve synergy with Atlantic's identity layer through these credential standards.

Figure 1. Manta Pacific (Ethereum modular L2) and Manta Atlantic (Polkadot ZK L1) architecture division connected via MANTA token bridge.

Pacific has technical dependencies on Celestia, Polygon zkEVM, and the Ethereum settlement layer; Atlantic's interoperability is constrained by the Polkadot parachain architecture. Cross-chain circulation of MANTA between the two chains depends on the security and liquidity of the Celer bridge. These dependencies constitute structural features of the dual-chain architecture: Pacific is responsible for application execution scaling, and Atlantic is responsible for identity credential anchoring. The two chains share MANTA liquidity through the Celer bridge.

How Do Privacy and ZK Capabilities Differ?

The difference between Pacific and Atlantic in zero-knowledge capabilities manifests along two technical paths: "ZK integration at the application layer" and "ZK credentials at the identity layer." Pacific provides Solidity developers with ZK-as-a-Service development libraries through Universal Circuits, allowing contracts to invoke pre-built ZK circuits, supporting scenarios such as compliant privacy payments, identity verification, and zkShuffle. Universal Circuits 2.0 introduces proof aggregation, reducing on-chain verification gas and increasing throughput.

Atlantic's ZK capabilities are concentrated on the identity and credential layer. zkAddress uses UTXO-style privacy addresses that operate in parallel with public accounts. Users can selectively disclose specific credentials using Prove Key without exposing their full identity profile. zkSBT, as a non-transferable on-chain credential, supports decentralized KYC verification; verifiers only learn the qualification result without accessing sensitive personal information. Atlantic's identity layer enables other Polkadot ecosystem projects to integrate interoperable identity without building a complete ZK identity protocol stack from scratch.

The Pacific application layer also supports zkSBT compliance verification. The two chains form synergy on credential standards: Atlantic serves as the underlying anchor for identity and credentials, while Pacific serves as the platform for application execution and ZK function integration. If developers need to embed ZK payment or shuffling logic in dApps, they should target Pacific and Universal Circuits; if they need to build on-chain compliant identity or KYC credential systems, they should target Atlantic and its zkAddress/zkSBT mechanisms.

Which Chain Should Developers and Users Choose?

Pacific is oriented toward Ethereum ecosystem developers and general dApp users. Developers can migrate or create new contracts in an EVM-compatible environment and invoke zero-knowledge functionality via the Universal Circuits SDK, without needing to learn specialized ZK languages such as Cairo or Noir. Typical scenarios include DeFi protocol deployment, on-chain gaming (zkShuffle), social applications, and compliant privacy payments. Users participating in the Pacific ecosystem typically need ETH for gas and need to bridge assets to the Pacific network.

Atlantic is oriented toward project teams, institutions, and users who require on-chain compliant identity. Project teams can integrate the zkSBT credential standard; users manage their privacy identity through zkAddress and disclose credentials on demand. Operations on the Atlantic side revolve around credential minting, Prove Key disclosure, and verification requests. Network governance and collator delegation must be paid in MANTA. Pacific focuses on application execution and ZK function calls; Atlantic focuses on identity establishment and compliance verification. The two chains have different operational processes and gas tokens.

At a Glance: Core Differences Between Pacific and Atlantic

The table below summarizes the core differences between Manta Pacific and Manta Atlantic across eight dimensions, enabling quick comparison of the two chains' positioning and technical characteristics.

Figure 2. Side-by-side comparison of Manta Pacific and Manta Atlantic across ecosystem, layer type, gas token, and core focus.

The comparison shows that Pacific and Atlantic are not two modes of the same network but two independent chains addressing different problem domains. Choosing Pacific or Atlantic depends on participation goals: application deployment and ZK function integration point to Pacific; compliant identity and credential construction point to Atlantic. The two chains achieve ecosystem synergy through the MANTA cross-chain bridge and shared token economics, but their technical stacks, gas mechanisms, and user paths must be understood separately.

Summary

Manta Pacific and Manta Atlantic form the complementary dual-chain ecosystem of Manta Network: Pacific serves as an Ethereum modular L2, leveraging Celestia DA, zkEVM, and Universal Circuits to carry ZK application deployment; Atlantic serves as a Polkadot ZK L1, using zkAddress and zkSBT to carry on-chain compliant identity. Gas denomination (ETH vs. MANTA), technical focus (application execution vs. identity credential), and target users (developers/dApp users vs. identity/KYC users) constitute the three most significant differences between the two chains. Understanding this division of labor helps in selecting the correct participation path and technical stack within the Manta Network ecosystem.

FAQ

What is the core difference between Manta Pacific and Manta Atlantic?

Manta Pacific is a modular L2 on the Ethereum ecosystem, focusing on ZK decentralized application deployment. Gas is paid in ETH, and core technologies include Celestia DA, zkEVM, and Universal Circuits. Manta Atlantic is a ZK L1 on the Polkadot ecosystem, focusing on on-chain compliant identity. Network fees are paid in MANTA, and core technologies include zkAddress and zkSBT.

Why do the two chains have different gas tokens?

Manta Pacific is deployed on the Ethereum ecosystem, and network gas is denominated in ETH, consistent with Ethereum L2 conventions. Manta Atlantic, as an independent L1, denominates network fees in MANTA, its native functional token. MANTA also serves functions such as governance, collator staking, and zkSBT purchases.

Which chain does Universal Circuits belong to?

Universal Circuits is a ZK-as-a-Service development library on Manta Pacific, allowing Solidity developers to invoke pre-built ZK circuits in Pacific contracts. Atlantic does not provide Universal Circuits; Atlantic's ZK capabilities are concentrated on the zkAddress and zkSBT identity credential layer.

Which chain do zkAddress and zkSBT belong to?

The core implementations and credential standards of zkAddress and zkSBT are anchored on Manta Atlantic. Atlantic provides UTXO-style privacy addresses and non-transferable on-chain credentials, supporting selective disclosure and decentralized KYC verification. The Pacific application layer can integrate zkSBT compliance verification, achieving credential standard synergy with Atlantic's identity layer.

How do the two chains connect through MANTA?

Manta Pacific and Manta Atlantic are connected via the Celer bridge for MANTA cross-chain locking and unlocking, sharing a genesis total supply of 1 billion tokens. Cross-chain flows affect the global MANTA circulating supply, but the two chains independently maintain their own block production, consensus, and security models.

How should developers choose between Pacific or Atlantic?

If you need to deploy ZK decentralized applications on the Ethereum ecosystem, call Universal Circuits, or participate in DeFi/gaming scenarios, you should target Manta Pacific. If you need to build on-chain compliant identity, issue zkSBT credentials, or manage zkAddress privacy identities, you should target Manta Atlantic. The two chains have complementary functions and can be used separately or in combination based on project requirements.