Skip to main content

Status Updates

Get the latest updates from the Gate Chain team.

Gate Layer Execution Client to Be Upgraded from Geth to Reth (2026-07-14)​

To improve Gate Layer node performance, operational stability, and client diversity, Gate Layer plans to smoothly upgrade its current execution-layer client from Geth to Reth. Reth is a high-performance Ethereum execution client written in Rust. It supports the execution-layer operating mode of OP Stack chains and works together with op-node through the Engine API.

This upgrade is a node infrastructure upgrade. It does not change GateLayer's chain ID, account system, contract addresses, transaction format, RPC API compatibility, or asset state. Regular users and application developers generally do not need to perform any asset migration, nor do they need to redeploy contracts.

Schedule​

Please complete the replacement before the release times listed below.

  • Mainnet switchover time: 2026-07-14 11:00 (UTC+8)
  • Mainnet switchover window: 2026-07-14 11:00 to 2026-07-14 12:00 (UTC+8)

Upgrade Impact​

  • Chain ID, block explorer, contract addresses, and historical state remain unchanged.
  • Standard JSON-RPC methods remain compatible, including common interfaces such as eth_sendRawTransaction, eth_call, eth_getLogs, and eth_getBlockByNumber.
  • During the upgrade window, there may be brief RPC jitter, transaction confirmation delays, or WebSocket reconnections.
  • If you run a self-hosted node, please follow this document's operating guide to switch the execution client to Reth.
  • If you use the official RPC, no changes to business code are required; we recommend adding transaction retries and RPC health checks before and after the upgrade window.

Notes​

  • During the mainnet switchover window, some nodes or RPC services may be temporarily unavailable. Transaction submissions may fail, be delayed on-chain, or experience unstable state queries.
  • We recommend that users and application providers avoid sending transactions, deploying contracts, or performing large-value asset operations during the switchover window as much as possible.
  • Please wait until the switchover window ends, RPC services are stable, and node sync status is normal before sending transactions or resuming automated business processes.

Risk Control​

Gate Layer will adopt a blue-green switchover approach: the existing op-node + Geth will continue to run as the production path, while op-reth + shadow op-node are launched in parallel to catch up on blocks and validate. Once the Reth node has caught up and passed consistency checks for RPC, transactions, block height, and logs, sequencer / RPC production traffic will be switched over during a maintenance window. After the switchover, the Geth data and services will be retained as a rollback path until the observation period ends.

Recommendations for Developers and Node Operators​

  1. If you only use the official RPC, please confirm that your application has RPC timeout retries, automatic WebSocket reconnection, and transaction status polling in place.
  2. If you run a self-hosted RPC node, please deploy the Reth node, download a snapshot, and complete syncing in advance. Do not start syncing from scratch during the switchover window.
  3. Do not delete the Geth datadir before the switchover is complete; schedule cleanup only after the observation period is confirmed stable.

FAQ​

Do users need to migrate assets?

No. This is an execution client replacement, not a chain change, state reset, or contract migration.

Will contract addresses change?

No. Contract addresses are determined by chain state; replacing the execution client does not change existing state.

Does RPC code need to be modified?

Standard JSON-RPC calls generally do not need modification. We recommend that applications retain timeout retries, idempotent transaction submission, automatic WebSocket reconnection, and receipt polling.

Can I delete the Geth data directly?

Not recommended. Wait at least until the observation period after the switchover ends, and confirm that Reth production is stable and rollback is no longer needed before cleaning up.

Can Reth reuse the Geth datadir?

No. Reth and Geth use different database formats, so you must use a separate datadir and re-sync or import a snapshot.

Are Reth P2P peers and op-node P2P peers the same thing?

No. The enode of Reth/Geth belongs to the execution-layer P2P; the peer ID of op-node belongs to libp2p. The key to following OP Stack unsafe payloads lies in op-node P2P, not merely adding execution-layer peers to Reth.

Gate Layer Mainnet Upgrade v1.1.0 (2026-03-12)​

Gate Layer is scheduled to complete the v1.1.0 version upgrade at 16:00 (UTC+8) on March 12, 2026. This is an important upgrade iteration that will optimize network performance, add core features, and enhance architectural stability.

Upgrade Deadline​

March 12, 2026, 08:00 (UTC)

Key Upgrades for v1.1.0​

1. Node Program and Configuration File Update​

2. Introduction of Jovian Version Core Capabilities​

  • Support the configuration of Minimum Base Fee (default value: 12 Gwei for now)
  • Add capabilities related to DA Footprint Block Limit
  • Complete the update of Operator Fee rules
  • Optimize the overall system performance and architectural stability

3. Restructuring and Optimization of Chain Head Synchronization Logic​

  • Conduct a full restructuring of the core chain head synchronization logic
  • Optimize the network synchronization process and improve synchronization stability
  • Accelerate block processing speed and enhance the overall transaction processing efficiency

4. Event System Restructuring​

  • Integrate the originally decentralized event processing logic of each module into a unified event system
  • Improve the decoupling of each functional module and reduce coupling risks
  • Optimize the overall maintainability and future functional scalability of the system

5. Compatibility Support for Ethereum Fusaka Upgrade​

  • Complete the full compatibility development and support for the Ethereum Fusaka upgrade
  • Lay the underlying technical foundation for the subsequent technical upgrades and ecological integration of Gate Layer

Upgrade Requirements​

  • All node operators must complete the binary update by the deadline
  • The ./l1-chain-config.json file must be added
  • Nodes that fail to complete the upgrade by the deadline will face the following consequences:
    • Inability to participate in the Gate Layer network consensus
    • Automatic removal from the node cluster by the network
    • Failure to synchronize new block data after the upgrade

Important Reminders​

  • It is recommended to complete the upgrade in advance and restart the node for testing
  • Back up all relevant data before the upgrade
  • Do not perform centralized operations near the upgrade time to avoid network congestion or operational risks

We would like to thank all node operators and partners for their support and cooperation with the Gate Layer network. For any questions, please provide feedback through official channels in a timely manner.

Gate Chain Mainnet Upgrade v1.2.1 (2026-02-11)​

Overview​

The Gate Chain consensus protocol will be upgraded to v1.2.1, adding support for EIP-7702. All nodes participating in consensus must upgrade their node binaries to ensure compatibility with the new version.

Scheduled Upgrade Date: 2026-02-11

Changelog​

Gate Chain Version Upgrade​

  • Block version updated to v21.
  • Consensus version updated to v1.2.1.

EVM Version Upgrade​

  • Upgraded to the Prague version, introducing support for EIP-7702.

EIP Compatibility Updates​

  • EIP-7702: Allows Externally Owned Accounts (EOAs) to temporarily function as smart contract wallets during a transaction, enabling features such as batch transactions and Gas sponsorship.

RPC Interface Improvements​

  • Transaction-related interfaces now support return fields for setCodeTx transaction types.

Geth Client Upgrade​

  • Geth upgraded to v1.16.1.

BlobStore S3 Support​

  • Added S3 storage support to BlobStore, enabling Blob data to be stored and persisted in S3.

Important Notice​

Please download and upgrade to the latest version promptly to avoid disconnection of consensus accounts.

Gate Layer Mainnet Launch (2025-09-25)​

Overview​

Gate Layer, a high-performance Layer 2 network built on the Optimism OP Stack Isthmus upgrade version, has officially launched on mainnet. As an integral part of the Gate Chain ecosystem, Gate Layer is fully compatible with the Ethereum Virtual Machine (EVM), leveraging Gate Chain as its secure settlement layer and integrating native Blob-based data availability to provide developers with scalable, reliable, and cost-efficient infrastructure.

Core Features​

1. High Performance​

  • Ultra-High Throughput: Peak TPS of 5,713, delivering excellent performance
  • Fast Block Time: 1-second block time ensuring rapid transaction confirmation
  • High Capacity: 120M block gas limit supporting high-load scenarios

2. Cost Advantages​

  • Ultra-Low Fees: Million transfer cost of only $30
  • Stable Rates: More stable gas fees compared to other L2 solutions
  • Cost-Efficient: Significant cost advantages among similar L2 solutions

3. Technical Architecture​

  • OP Stack Foundation: Built on the mature Optimism OP Stack Isthmus upgrade version
  • EVM Compatibility: Fully compatible with Ethereum Virtual Machine, supporting existing toolchains
  • Secure Settlement: Leverages Gate Chain as settlement layer, secured by GT staking
  • Data Availability: Integrated native Blob storage providing efficient data availability

4. Ecosystem Support​

  • Diverse Applications: Supports meme ecosystems, perpetual exchanges, gaming, DeFi, and social platforms
  • Cross-Chain Interoperability: LayerZero integration enabling native multi-chain interoperability
  • Developer-Friendly: Open, permissionless environment with familiar EVM toolchain

Network Information​

Gate Chain Mainnet Upgrade v1.1.9 & v1.2.0 (Cancun & EIP-4844) (2025-09-13)​

Overview​

The Gate Chain consensus version will be upgraded to v1.2.0, with the core feature being the addition of support for Blob transactions (EIP-4844). This will provide low-cost data availability for L2 solutions like Gate Layer. All nodes participating in consensus must upgrade their node binaries.

Changelog​

1. Core Upgrades​

  • Gate Chain Version Upgrade: The block version number is upgraded to v20.
  • EVM Version Upgrade: The EVM is upgraded to the Cancun version, introducing several of Ethereum's latest improvements.
  • EIP-4844 Compatibility: Support for Shard Blob Transactions (Proto-Danksharding), adding a new Blob transaction type and a related gas fee mechanism to lay the foundation for L2 data storage and transaction optimization.

2. EIP Compatibility Updates​

  • EIP-1153: Introduces transient storage opcodes to optimize temporary data handling in transactions.
  • EIP-2565: Reduces the gas cost of the ModExp operation, improving the efficiency of large number arithmetic.
  • EIP-2929: Increases the gas cost of state-access opcodes (like SLOAD) to enhance on-chain security.
  • EIP-2930: Adds optional access lists to optimize transaction gas calculations.
  • EIP-3198: Returns the block BASEFEE, facilitating transaction fee calculation and smart contract optimization.
  • EIP-3529: Reduces gas refunds for EVM operations to improve the rationality of the fee model.
  • EIP-3541: Prohibits deploying contract bytecode starting with 0xEF to enhance contract security.
  • EIP-3651: Warms up the COINBASE address to optimize block reward payments and gas consumption.
  • EIP-3855: Adds the PUSH0 instruction to save bytecode space and gas.
  • EIP-3860: Limits and meters the size of contract initcode to prevent attacks from oversized contracts.
  • EIP-5656: Adds the MCOPY memory copying instruction to improve EVM memory operation efficiency.
  • EIP-6780: Restricts SELFDESTRUCT to be called only within the same transaction, enhancing the predictability of contract execution.

3. RPC Interface Improvements​

  • Added new RPC interfaces related to Blob transactions.
  • Adjusted and optimized the eth_hash return value.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Mainnet Upgrade v1.1.8 (2025-08-20)​

Overview​

Gate Chain completed the mainnet upgrade to v1.1.8 on August 20, 2025, at 10:00 (UTC+8).

Changelog​

  • Gate Chain Version Upgrade: The block version number is upgraded to v18.
  • Bug Fix: Fixed an issue where some successful transactions were incorrectly reported as 'out of gas', causing their status to show as 'failed'.

Important Notice​

All relevant external nodes are advised to be aware of and upgrade to version v1.1.8.

Gate Chain Mainnet Upgrade v1.1.7 (2025-08-11)​

Overview​

  1. The Gate Chain consensus version will be upgraded to v1.1.7. All nodes participating in consensus need to upgrade their node binaries.
  2. Planned upgrade date: 2025-08-18
  3. For details, please refer to the Gate Chain Documentation.

Upgrade Mechanism​

The Gate Chain consensus upgrade process is as follows:

  • When consensus nodes use the new version binary to assemble a block, a network-wide upgrade vote will be triggered.
  • After a round of block generation, once the vote count exceeds the threshold, the new protocol consensus will take effect across the network.
  • At this point, any consensus node that has not upgraded to the latest version will be unable to participate in consensus.

Changelog​

  1. Gate Chain Version Upgrade:
    • The block version number is upgraded to v17.
  2. Transaction Fee Check:
    • Standard transaction fees must be greater than the base fee.
    • The GasRemaining method is added to GasMeter for querying remaining Gas.
  3. EVM Transaction Adjustments:
    • The initial nonce for EVM accounts is corrected to 0.
    • A fixed 21000 gas fee is now deducted by default for EVM transfers.
  4. Block Production Mechanism Adjustment:
    • The gasFeeThreshold mechanism is introduced to prevent low-value, invalid transactions from farming staking rewards.
  5. RPC Interface Improvements:
    • An LRU cache mechanism is introduced in the API layer to optimize access efficiency.
    • New RPC interfaces have been added.
  6. Various Fixes and Optimizations:
    • Fixed an issue where a node could wait indefinitely if a transaction ran out of gas.
    • Fixed a concurrent map read panic.
    • Fixed precision issues in RPC interface returns.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Mainnet Upgrade v1.1.6 (2024-08-19)​

Overview​

  1. The Gate Chain consensus version will be upgraded to v1.1.6. All nodes participating in consensus need to upgrade their node binaries.
  2. Planned upgrade date: 2024-08-26
  3. For details, please refer to the Gate Chain Documentation.

Upgrade Mechanism​

The Gate Chain consensus upgrade process is as follows:

  • When consensus nodes use the new version binary to assemble a block, a network-wide upgrade vote will be triggered.
  • After a round of block generation, once the vote count exceeds the threshold, the new protocol consensus will take effect across the network.
  • At this point, any consensus node that has not upgraded to the latest version will be unable to participate in consensus.

Changelog​

  1. EVM Version Upgrade
  2. Minimum GasPrice Adjustment:
    • Increased from 5NANOGT to 10NANOGT.
    • Block Gas Limit set to 150M.
  3. EIP-2718 Compatibility:
    • Added support for multiple EVM transaction types.
  4. EIP-1559 Compatibility:
    • Implemented dynamic network fees.
    • Introduced a base fee burning mechanism.
  5. RPC Interface Improvements:
    • Process optimization.
    • Bug fixes and stability enhancements.
  6. Compilation and User Experience Enhancements:
    • Added support for creating local accounts with a default password.
  7. General Improvements:
    • Various bug fixes and optimizations.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Mainnet Upgrade v1.1.5 (2022-12-14)​

Overview​

  1. The Gate Chain consensus version will be upgraded to v1.1.5. All nodes participating in consensus need to upgrade their node binaries.
  2. Planned upgrade date: 2022-12-20
  3. For details, please refer to the Gate Chain Documentation.

Upgrade Mechanism​

The Gate Chain consensus upgrade process is as follows:

  • When consensus nodes use the new version binary to assemble a block, a network-wide upgrade vote will be triggered.
  • After a round of block generation, once the vote count exceeds the threshold, the new protocol consensus will take effect across the network.
  • At this point, any consensus node that has not upgraded to the latest version will be unable to participate in consensus.

Changelog​

  1. EVM Module Enhancements:
    • Added functionality for reinvesting staking rewards.
    • Added a feature for all consensus nodes to withdraw rewards with a single click.
  2. Protocol Compatibility:
    • Compatible with the EIP-1989 proposal.
  3. Consensus Improvements:
    • Optimized the loyalty factor growth scheme for committee-elected consensus nodes.
  4. General Improvements:
    • Various bug fixes and optimizations.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Mainnet Upgrade v1.1.4 (2022-11-02)​

Overview​

  1. The Gate Chain consensus version will be upgraded to v1.1.4. All nodes participating in consensus need to upgrade their node binaries.
  2. Planned upgrade date: 2022-11-03
  3. For details, please refer to the Gate Chain Documentation.

Upgrade Mechanism​

The Gate Chain consensus upgrade process is as follows:

  • When consensus nodes use the new version binary to assemble a block, a network-wide upgrade vote will be triggered.
  • After a round of block generation, once the vote count exceeds the threshold, the new protocol consensus will take effect across the network.
  • At this point, any consensus node that has not upgraded to the latest version will be unable to participate in consensus.

Changelog​

  1. Node Improvements:
    • Added the ability for users to edit the fee rates of consensus nodes.
    • Implemented a "debug trace" feature for EVM transactions.
  2. System Enhancements:
    • Added batch digital rollback capability to the Gatemint engine.
  3. General Improvements:
    • Various bug fixes and optimizations.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Mainnet Upgrade v1.1.3 (2022-05-13)​

Overview​

  1. The Gate Chain consensus version will be upgraded to v1.1.3. All nodes participating in consensus need to upgrade their node binaries.
  2. Planned upgrade date: 2022-05-17
  3. For details, please refer to the Gate Chain Documentation.

Upgrade Mechanism​

The Gate Chain consensus upgrade process is as follows:

  • When consensus nodes use the new version binary to assemble a block, a network-wide upgrade vote will be triggered.
  • After a round of block generation, once the vote count exceeds the threshold, the new protocol consensus will take effect across the network.
  • At this point, any consensus node that has not upgraded to the latest version will be unable to participate in consensus.

Changelog​

  1. System Upgrades:
    • Upgraded consensus version to v1.1.3.
    • Enhanced the ledger snapshot feature.
  2. Performance Improvements:
    • Implemented gas fee suggestions.
    • Added sorting of transactions by gas price.
    • Added caching for EVM transaction signatures to improve efficiency.
  3. Module Enhancements:
    • Optimized the subscription push module.
    • Fixed the timing of computing power updates in EVM staking.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Mainnet Upgrade v1.1.0 (2021-09-14)​

Overview​

  1. The Gate Chain consensus version will be upgraded to v1.1.0. All nodes participating in consensus need to upgrade their node binaries.
  2. Planned upgrade date: 2021-09-15
  3. For details, please refer to the Gate Chain Documentation.

Upgrade Mechanism​

The Gate Chain consensus upgrade process is as follows:

  • When consensus nodes use the new version binary to assemble a block, a network-wide upgrade vote will be triggered.
  • After a round of block generation, once the vote count exceeds the threshold, the new protocol consensus will take effect across the network.
  • At this point, any consensus node that has not upgraded to the latest version will be unable to participate in consensus.

Changelog​

  1. Version Upgrades:
    • Upgraded consensus version to v1.1.0.
    • Upgraded EVM version to v1.10.8.
  2. System Improvements:
    • Implemented caching for transactions with large nonces.
    • Enhanced API debug_traceTransaction to support debugging of failed transactions.

Important Notice​

Please download and upgrade to the latest version promptly to prevent consensus accounts from being disconnected.

Gate Chain Launches Today (2020-06-29)​

Overview​

Gate Chain is a next-generation public chain focused on on-chain asset security and decentralized trading. With its uniquely designed vault account, Gate Chain provides a remarkable clearing mechanism for handling abnormal transactions, addressing the challenges of asset theft and private key loss. It will also support core functions such as decentralized trading and cross-chain transfers.

Last updated on 2026/07/13