The July 2023 financing announcement explains the original combination more clearly than a generic ZK label. Developer p0x labs announced a Series A led by Polychain and Qiming while opening Pacific’s testnet. Kenny Li argued that application cryptography, Celestia data availability and the OP Stack could be assembled into a usable environment. Polychain’s Luke Pearson emphasized access to ZK tooling; Qiming’s Yi Tang emphasized applications and Asian markets. Those are attributed builder and investor expectations.

The financing concerned the developer, separately from the rights attached to MANTA.

Pacific’s mainnet alpha opened on September 12, 2023. The announcement explicitly said that it initially used Ethereum data availability and would adopt Celestia later. Its earlier July testnet had allowed teams to experiment with applications before this production launch. That sequence matters when reading historical claims: an alpha capable of processing transactions was already useful, but it was not the completed architecture envisioned in subsequent roadmaps. The launch promoted Solidity accessibility and Universal Circuits as a way to reuse Manta’s cryptographic work.

Reported testnet wallet totals were the project’s own activity figures, not a count of independently verified paying users.

Universal Circuits addressed a developer problem inside applications. The August 2023 explanation used card shuffling as an example: players need confidence that a deck follows agreed rules without learning its hidden order. A Solidity interface and SDK could make such proof operations easier to call than building the cryptographic circuit from scratch. That is different from proving every Pacific state transition to Ethereum. An application can use zero-knowledge cryptography while the network carrying its transactions has a different validation model.

Builders should identify the circuit, public inputs and verifier used by their application instead of treating the ecosystem’s ZK branding as a universal privacy guarantee.

The current Pacific network directory identifies mainnet as chain 169 and denominates transaction fees in ETH. That identity should be checked before using a wallet or exchange withdrawal route. An ERC-20 MANTA balance on Pacific is not ETH available for gas. Nor is an Atlantic address simply an alternative spelling of an Ethereum address. The Pacific directory separates its mainnet from development networks, making the chain identifier more reliable than a token ticker for choosing a destination.

An explorer balance on another network cannot establish that the same amount is spendable on Pacific, even when a wallet displays a familiar asset name.

Manta’s Celestia documentation explains why the project separated data publication from execution. Celestia specializes in ordering and making data available; sampling lets light clients gather evidence that block data exists, and namespaces help applications locate relevant data. The attraction for Pacific was cheaper publication rather than requiring Ethereum to store every transaction byte. These roles should not be collapsed into a claim that Celestia executes Pacific contracts or settles withdrawals. Some wording on that documentation page still describes the integration prospectively.

Its explanation of the intended division of work is useful, while a current deployment assessment must come from the network’s actual configuration.

The October 2023 roadmap proposed successive stages: an OP Stack alpha, Celestia availability, a transition using Polygon CDK and further circuit improvements. It even discussed an intermediate multi-prover arrangement. These were explicit architectural ambitions, not interchangeable descriptions of an already deployed system. A reader following the token’s history should preserve that distinction because older introductions often repeat the intended zkEVM destination in the present tense.

It does not establish that a present Pacific withdrawal is checked by a Polygon validity proof, or that all the planned transitions occurred.

L2BEAT’s reviewed contract configuration describes Pacific as an OP Stack system without an operating fault-proof mechanism. It relies on permissioned proposers and challengers, uses external Celestia data and permits immediate upgrades. Its review also identifies externally owned account control over critical upgrades. A sequencer fallback through Ethereum does not remove dependence on state proposals: proposer failure can still prevent withdrawals. The same review says Celestia transaction roots are not checked against a Blobstream data bridge on Ethereum.

These are concrete dependencies behind the cheaper execution environment. They limit the stronger interpretation that every withdrawal is already protected by permissionless disputes or validity proofs.

The compatibility documentation highlights differences that application teams must handle even when Solidity code is familiar. Messages from Ethereum contracts use address aliases to prevent impersonation across layers. Transaction fees have more than an execution component, and block parameters need not match Ethereum. Pacific also uses a sequencer-centered mempool rather than exposing the same public transaction queue described for Ethereum. For a builder, these details affect sender authentication, fee estimation and assumptions about transaction ordering.

EVM compatibility reduces the amount of software that must be rewritten; it does not make every cross-chain security assumption or every operational dependency identical.

The official replica guide describes op-node and op-geth containers, Celestia configuration and snapshot-based initialization. Its Ecotone instructions include explicit activation overrides, illustrating why copying an old command without checking the network version is unreliable. The page directs readers to a separate maintained operator document for newer instructions.

Running such a replica may help an application serve its own RPC traffic, but downloading a supplied snapshot and following a sequencer are not, by themselves, evidence of reconstructing the complete network from independently available history.

The native bridge FAQ separates a Pacific withdrawal request, verification on Ethereum and a later completion transaction. It gives an approximate seven-day wait and warns that an initiated withdrawal cannot simply be cancelled. Those instructions are materially different from a marketing promise of a transfer in minutes. The page also notes that third-party bridges may provide faster movement. A faster service is another route with its own terms, rather than proof that the native mechanism has eliminated its waiting period.

Because older announcements and this FAQ describe different durations, the transaction’s current contract state and interface matter more than treating one historical estimate as a perpetual guarantee.

The token documentation records one billion MANTA at genesis, an issuance schedule and allocations to investors, contributors, a foundation, users and ecosystem programs. It distinguishes Atlantic’s native fees and collator delegation from Pacific’s intended governance and ecosystem incentives. For Pacific, the value argument was indirect: sequencer revenue and data-cost savings could finance applications and public goods, which might attract further activity. That is a development thesis, not an unconditional distribution of cash to every holder.

The page retains historical Atlantic and staking language, so its original allocation and design descriptions should not be mistaken for a current guarantee that every listed utility remains operational.

The fast-finality design described two added validation layers. MANTA delegation through Symbiotic would support operators signing state roots; Babylon finality providers would contribute a distinct Bitcoin-staking mechanism. Signatures and relayers would carry those results toward settlement. The same document placed OP fault proofs and ZK dispute proofs in later integration phases. This explains why fast confirmations, restaking and a permissionless execution proof are different claims.

The document is a record of the design, not sufficient evidence that all its components remain active after later policy changes. Its broad security language should be read alongside the explicit staging and subsequent staking notice.

The staking overview now carries a prominent notice that network rewards stopped on May 20, 2026. It permits operators to terminate their nodes and directs delegators to unstake through the dashboard. Older explanations of reward distribution remain below that notice, creating a real risk of reading historical mechanics as a current earning opportunity. The dated sunset takes precedence for that question. Ending an incentive program changes the economic relationship between operators and holders, but the notice alone does not document every resulting contract or infrastructure change.

It would be inaccurate to advertise the old reward formula as today’s APR or assume that a former operator still supplies the same validation service.

The official Atlantic migration portal states that Atlantic has stopped producing blocks. It replaces an on-chain transfer with a signature proving ownership and a claim on Pacific. The advertised window runs from September 17 to November 16, 2026, at 08:00 UTC. This is a migration from an ended ledger, rather than a new Atlantic transaction. Its destination is Pacific, whose native gas is ETH. The notice supersedes older introductions describing two operating networks. The portal does not establish an equivalent recovery path for every non-MANTA asset or exchange-held balance.

The June 2024 EcoFund announcement described a one-year, $50 million allocation split between investment, grants and events. It sought consumer applications across DeFi, games and other sectors, with smaller grants intended to help early teams. The announcement also used the Mantalorians identity to invite a shared building culture. This joins an economic mechanism with a cultural one: financial support could lower a team’s initial costs while events and a common name could make participation socially rewarding.

The announced allocation is not evidence that the full amount was disbursed, that every grantee succeeded, or that the same application window remains open in September 2026.

The April 2024 AI announcement proposed combining Hyperbolic compute infrastructure and ORA’s optimistic machine-learning oracle with Manta’s developer interfaces. It repeatedly described future deployments and extensions. The practical aim was to let applications request inference or training services without building all the surrounding infrastructure themselves. That is an application and service integration thesis. It does not mean Pacific consensus runs an entire AI model, or that an advertised partnership proves production adoption.

Its expansive AGI language went beyond the capabilities established for the named example models.

An April 7, 2026 project announcement scheduled the tenth and final MANTA reward round for CeDeFi users after that day’s snapshot. It expressly said that CeDeFi would remain available. This is a useful example of a lifecycle distinction often lost in token discussions: ending promotional token distributions is not the same announcement as closing a product. It also means that earlier campaign rewards cannot be projected indefinitely. Users assessing the service need to separate its underlying strategy and counterparties from an extra token incentive.