# Mantle: newest node and prover software releases

Pages read on 2026-10-27, between 14:20 and 14:40 UTC. I got release data from the GitHub REST API for each repository's releases and tags. I also checked the releases HTML page for mantle-v2, and its "Latest" badge and published datetime match the API. Published dates are the `published_at` value GitHub shows, in UTC.

Note: the candidate URLs under `github.com/mantlenetworkio/` (`mantle-v2`, `op-geth`) now redirect. GitHub answers "Moved Permanently", and the repositories now live under the **`mantle-xyz`** organization: https://github.com/mantle-xyz/mantle-v2 and https://github.com/mantle-xyz/op-geth. The `mantlenetworkio` org has no `op-succinct` fork. The fork is at https://github.com/mantle-xyz/op-succinct.

## Software

- **Rollup node (consensus/derivation, batcher, proposer):** `mantle-v2`, maintained by Mantle (GitHub org `mantle-xyz`). https://github.com/mantle-xyz/mantle-v2. It is Mantle's own OP Stack codebase and is not marked on GitHub as a fork of `ethereum-optimism/optimism`. The release notes for v1.6.3 say it "Uses `op-geth v1.6.3`, based on upstream `go-ethereum v1.17.3`" (https://github.com/mantle-xyz/mantle-v2/releases/tag/v1.6.3). The Docker images it ships are `mantlenetworkio/mantle-op-node` and `mantlenetworkio/mantle-op-geth` (https://github.com/mantle-xyz/networks/blob/main/docker-compose-mainnetv2-upgrade-beacon.yml).
- **Execution client:** `op-geth`, Mantle's fork. GitHub marks it as a fork of `ethereum-optimism/op-geth`. https://github.com/mantle-xyz/op-geth. Its v1.6.3 notes say it is "Based on upstream `go-ethereum v1.17.3`" and "Retains Mantle-specific BVM_ETH, fee accounting, preconfirmation, deposit, and fork behavior on top of that upstream base" (https://github.com/mantle-xyz/op-geth/releases/tag/v1.6.3).
- **Prover:** `op-succinct`, Mantle's fork. GitHub marks it as a fork of `succinctlabs/op-succinct`. https://github.com/mantle-xyz/op-succinct
- **Verdict:** Mantle runs **its own forks** of OP Stack software, not unmodified upstream binaries.

## Newest node release

**mantle-v2 (op-node and related components)**
- Repository: https://github.com/mantle-xyz/mantle-v2 (releases: https://github.com/mantle-xyz/mantle-v2/releases)
- Tag: `v1.6.3`
- Title: "1.6.3 Elysium"
- Published: 2026-09-21T03:38:19Z (https://github.com/mantle-xyz/mantle-v2/releases/tag/v1.6.3)
- Release URL: https://github.com/mantle-xyz/mantle-v2/releases/tag/v1.6.3
- Change: it introduces the Elysium codebase so that Mantle derivation, batch submission and cross-chain messaging keep working when Ethereum L1 activates Glamsterdam. The L2 EVM stays on Arsia/Osaka rules. It also turns on eager next-block construction for the sequencer and ships CrossDomainMessenger 1.6.0.
- Pre-release: **no**. It is not a draft, and the releases page marks it "Latest".
- Tags page: newer-looking tags exist with no GitHub release attached. The newest is `mantle-v1.6.3` under a new tag prefix; the other v1.6 tags are `v1.6.2`, `v1.6.1-rc0` and `v1.6.0` (https://github.com/mantle-xyz/mantle-v2/tags). I found no release published after v1.6.3. The previous non-pre-release was `v1.5.4` "v1.5.4 Mainnet Arsia", published 2026-04-08T07:49:53Z (https://github.com/mantle-xyz/mantle-v2/releases/tag/v1.5.4).

**op-geth (execution client)**
- Repository: https://github.com/mantle-xyz/op-geth (releases: https://github.com/mantle-xyz/op-geth/releases)
- Tag: `v1.6.3`
- Title: "1.6.3 Elysium"
- Published: 2026-09-21T03:25:25Z (https://github.com/mantle-xyz/op-geth/releases/tag/v1.6.3)
- Release URL: https://github.com/mantle-xyz/op-geth/releases/tag/v1.6.3
- Change: the Elysium execution client, rebased on go-ethereum v1.17.3, compatible with L1 Glamsterdam. Amsterdam EVM rules are present but not activated on Mantle L2.
- Pre-release: **no**, and not a draft.
- Tags page: v1.6 tags are `v1.6.3`, `v1.6.2-rc0`, `v1.6.1` and `v1.6.0`. Only v1.6.3 has a GitHub release (https://github.com/mantle-xyz/op-geth/tags). The previous release was `v1.5.5` "v1.5.5 Patch for Arsia", published 2026-04-21T10:37:44Z (https://github.com/mantle-xyz/op-geth/releases/tag/v1.5.5).

## Newest prover release

**Mantle's fork of op-succinct (ZK prover)**
- Repository: https://github.com/mantle-xyz/op-succinct (fork of https://github.com/succinctlabs/op-succinct)
- Tag: `mantle-v1.6.1`
- Title: "mantle-v1.6.1"
- Published: 2026-09-16T12:28:26Z (https://github.com/mantle-xyz/op-succinct/releases/tag/mantle-v1.6.1)
- Release URL: https://github.com/mantle-xyz/op-succinct/releases/tag/mantle-v1.6.1
- Change: a hotfix on top of `mantle-v1.6.0` for a consensus divergence. Deposit `eth_value`/`eth_tx_value` were truncated to `u128`. The guest ELFs were rebuilt, and both on-chain verification keys (`rangeVkeyCommitment`, `aggregationVkey`) changed. The fix pins `mantle-xyz/mantle-v2` at `mantle-v1.6.3` and `mantle-xyz/revm` at `v107-mantle-arsia.2`.
- Pre-release: **no**, and not a draft. The API reports it as the latest release.
- Previous release: `mantle-v1.6.0`, published 2026-09-02T06:54:27Z (https://github.com/mantle-xyz/op-succinct/releases/tag/mantle-v1.6.0).
- Tags page: it also has tags with no release, such as `v3.8.1-mainnet-mantle-arsia.2` and `v2.2.4-mainnet.5-rc1` (https://github.com/mantle-xyz/op-succinct/tags). Tags carry no dates, so I can't say whether these are newer than mantle-v1.6.1.

**Upstream op-succinct (for reference only; Mantle runs the fork above)**
- Repository: https://github.com/succinctlabs/op-succinct
- Newest release: tag `v4.9.3`, title "v4.9.3", published 2026-10-27T10:14:52Z, not a pre-release (https://github.com/succinctlabs/op-succinct/releases/tag/v4.9.3). Change: it moves to SP1 6.10.0, Hokulea 1.4.2 and SP1 cluster client 2.9.0, with fault-proof state recovery and bond-handling updates.
- The parallel v3 line released `v3.14.3` at 2026-10-27T09:07:31Z (https://github.com/succinctlabs/op-succinct/releases/tag/v3.14.3).

## Operator docs version

- **Mainnet:** I found no mainnet deployment guide for v1.6.3. The newest mainnet guide in Mantle's docs is "mainnet-v1.5.4" (https://docs.mantle.xyz/network/for-node-operators/deployment-guides/mainnet-v1.5.4). Its Docker guide sends operators to the `mantle-xyz/networks` repo and names no version itself (https://docs.mantle.xyz/network/for-node-operators/deployment-guides/mainnet-v1.5.4/deploying-a-rollup-verifier-replica-node-from-docker). The mainnet compose file in that repo pins `mantlenetworkio/mantle-op-geth:v1.5.4` and `mantlenetworkio/mantle-op-node:v1.5.4` (https://github.com/mantle-xyz/networks/blob/main/docker-compose-mainnetv2-upgrade-beacon.yml; the `...-upgrade-da-indexer.yml` file pins the same versions). So **for mainnet, the docs currently tell operators to run v1.5.4**, not v1.6.3.
- **Sepolia testnet:** the docs have a "testnet-v1.6.3" deployment guide (https://docs.mantle.xyz/network/for-node-operators/deployment-guides/testnet-v1.6.3). The changelog "mantle-v2 v1.6.3 Elysium upgrade" says Mantle Sepolia operators must upgrade op-node and op-geth to **v1.6.3**, with the Sepolia upgrade scheduled for "Tue, 06 Oct 2026, 13:53:36 UTC" (https://docs.mantle.xyz/network/for-node-operators/network-updates/changelogs/mantle-v2-v1.6.3-elysium-upgrade). That page has no mainnet date. The Sepolia compose file pins `mantle-op-geth:v1.6.3` and `mantle-op-node:v1.6.3` (https://github.com/mantle-xyz/networks/blob/main/docker-compose-sepolia-upgrade-beacon.yml). The latest commit in the networks repo is "sepolia: bump op-geth/op-node to v1.6.3 (#136)", dated 2026-09-21T06:23:29Z (https://github.com/mantle-xyz/networks/commits/main).
- Tension to flag: GitHub labels v1.6.3 the "Latest" release, but the docs and compose files for mainnet still say v1.5.4. They name neither op-geth `v1.5.5` "Patch for Arsia" nor op-geth/mantle-v2 v1.6.3.

## Not found

- **Upgrade date for mainnet v1.6.3 (Elysium):** I found no mainnet changelog or deployment guide. Checked the docs sitemap (https://docs.mantle.xyz/network/sitemap-pages.xml), where the only v1.6.3 pages are for testnet/Sepolia, and the changelog page above.
- **Prover version in operator docs:** Mantle's docs do not say which op-succinct prover version Mantle mainnet runs. The fork's latest GitHub release is mantle-v1.6.1, but I did not confirm that version on-chain or in the docs.
- **Releases for tags:** `mantle-v1.6.3` (mantle-v2), `v1.6.2-rc0`/`v1.6.1` (op-geth) and `v3.8.1-mainnet-mantle-arsia.2` (op-succinct fork) are tags with no GitHub release page, so they have no release date.
- **Dead docs URL:** https://docs.mantle.xyz/network/for-node-operators/node-software-releases returns "Page Not Found".
- **Dead candidate URLs:** the candidate repositories under `github.com/mantlenetworkio/` redirect to `mantle-xyz`, and the `mantlenetworkio` org has no op-succinct fork (https://github.com/mantlenetworkio).