Release notes
We maintain a record and brief explanation of Linea Security Council transactions.
Beta v4.4
Linea Mainnet: 3 December 2025
Linea Sepolia: 1 December 2025
- Upgraded Linea to Fusaka (Ethereum's latest EVM upgrade), detailed in the upgrade guide.
Beta v4.3
Linea Mainnet: 17 November 2025
Linea Sepolia: 10 November 2025
- Upgraded to limitless prover, enabling higher throughput and lower gas fees.
- Increased throughput to 100 Mgas/s.
Beta v4.2
Linea Mainnet: 5 November 2025
Linea Sepolia: 31 October 2025
- Updated the burn mechanism to include LINEA tokens. Details and percentage breakdown in the burn mechanism guide.
Fusaka
Linea will be implementing upgrades to bring the network into line with the latest updates to the Ethereum network, referred to as the Fusaka upgrade.
Beta v4.1
Linea Mainnet: 30 October 2025
Linea Sepolia: 30 October 2025
- Boost prover performance by reducing proving time by 33%, supporting scaled trading, consumer, and institutional use cases.
Beta v4.0
Linea Mainnet:
- Paris: 22 October, 2025, block 24787631
- Shanghai: 10am UTC, 23 October, 2025
- Cancun: 10am UTC, 28 October, 2025
- Prague: 10:10am UTC, 28 October, 2025
Linea Sepolia:
- Paris: 24 September, 2025
- Shanghai: 29 September, 2025
- Cancun: 30 September, 2025
- Prague: 7 October, 2025
Pectra hard fork
This release will see Linea implement approximately four years' of Ethereum protocol upgrades in a matter of weeks: from the London hard fork beforehand this release, all the way through to Prague. Due to the complexity of this process, the upgrade will occur in stages, progressing through hard forks according to the release schedule above.
For Linea users, the upgrade will enable new use cases and experiences through EIP-7702 (coming in Beta v6.0), unlocking access to apps that rely on this capability.
For builders, Linea becoming even more strongly Ethereum-aligned will make the developer experience
more streamlined and closely resemble Ethereum. The upgrade adds support for several opcodes and
precompiles, such as PUSH0 and MCOPY, considerably shortening the list of Linea's
differences with Ethereum.
EIP-7702 will only be activated in Beta v6.0.
Maru consensus client
Beta v4.0 introduces a new consensus client, Maru, replacing the existing Proof-of-Authority sequencer mechanism, Clique. Maru introduces a QBFT consensus mechanism, and will support Linea's future transition to decentralized sequencing. Initially, only a single Maru node operated by Linea will produce blocks.
Beta v3.1.1
Linea Mainnet: 6 October, 2025
- Made Linea's prover 2x more efficient, reducing the cost of running the Linea infrastructure. In future, this additional efficiency will increase ETH and LINEA burn
Beta v3.1
Linea Mainnet: early/mid-August 2025 (target)
Linea Sepolia: late July 2025 (target)
- Remove sequencer limits. These are no longer required because of the limitless prover introduced in Beta v3.
- Increase throughput
Beta v3.0
Linea Mainnet: early August 2025 (target)
Linea Sepolia: late July 2025 (target)
- Limitless prover: Eliminates the need for the sequencer to enforce module limits, as the prover
can handle complex workloads. This unlocks:
- Higher throughput and TPS
- Stabler gas fees during high-traffic periods
- Faster transaction confirmation during activity peaks.
Note that the higher throughput will not enabled until the sequencer limits are removed in Beta v3.1.
Beta v2.0
Linea Mainnet: June 9, 2025
Linea Sepolia: mid/late May 2025
- 100% proven: 100% of EVM operations will be covered by our zero-knowledge proofs, guaranteeing the integrity of all onchain data when sequencing is decentralized. Linea is the first zkEVM to be completely proven.
- Reworks prover limits to reduce infrastructure costs and reduce instances of transactions reverting due to exceeding limits.
- Upgrades the dictionary to improve compression and reduce the costs of L1 data availability by 7.5%.
- Improves Security Council configuration, and onboards the first cohort of members to stage 1, supporting future decentralization and security.
Beta v1.0
Beta v1 on Linea introduces new arithmetization. The overall objective of the Linea Beta is to prove 100% of the zkEVM specification, an objective currently scheduled to be completed in Beta v2.
Beta v1.4
Linea Mainnet: April 28, 2025
Linea Sepolia: April 7, 2025
- Adds the
eth_sendBundleRPC method, enabling apps to protect users against MEV and improve UX in various ways. - Introduces state recovery, enabling anyone to recover and audit Linea state, reducing the risk of having a centralized sequencer.
Beta v1.3
Linea Mainnet: March 3, 2025
Linea Sepolia: February 18, 2025
- Raises the block gas limit to 2B.
Beta v1.2
Linea Mainnet: with Beta v2
Linea Sepolia: February 4, 2025
- Full implementation of new arithmetization, with all modules from the Linea specification except the hub's consistency arguments.
- Proof of all the activated modules (i.e. excluding the hub consistency arguments).
Beta v1.1
Linea Mainnet: with Beta v2
Linea Sepolia: September 26, 2024
- New arithmetization, with selected modules activated from the Linea specification.
- The transition to generating traces with Besu.
Alpha v4.2
Mainnet: March 26, 2025
Linea Sepolia: March 18, 2025
- Improvements to the Linea bridge:
- New UI for improved user experience
- Update Linea native bridge to use the Circle CCTP for USDC transfers
- Add new bridging aggregators for faster transfers and greater chain selection
- Integrate Onramper for seamless fiat onramping to Linea only (live on April 3)
- Transition to native USDC, seamless for Linea users
Alpha v4.1
Mainnet: February 4, 2025
Linea Sepolia: January 28, 2025
- Add automatic claiming for L1 → L2 bridging on the Linea native bridge.
- Introduces the Linea Token API at alpha stage.
Alpha v4.0
Mainnet: December 16, 2024
Linea Sepolia: November 27, 2024
This update upgrades several key contracts. Some updates prepare the protocol for the ability to reconstruct the Linea state, while others add granularity to available roles, better preparing them for any required pauses. Many of the contract modifications have also resulted in gas optimizations.
Additionally, we are removing the finalizeBlocksWithoutProof function, and adding functionality
that enables any address to send blob submission and finalization transactions through a call
forwarding contract if no finalization occurs for more than six months. This effectively allows L1
finalization, enabling withdrawal of potentially locked funds.
Code in the upgrade has been audited by:
- OpenZeppelin, whose report is available here,
- Diligence, whose report is available here, and;
- Cyfrin, whose report is here.
Changes in this release:
- Adjust blob submission and finalization events to be state reconstruction-compatible
- This is a breaking change for the event structures. The new structures are below:
/**
* @notice Emitted when compressed data is being submitted and verified successfully on L1.
* @dev The block range is indexed and parent shnarf included for state reconstruction simplicity.
* @param parentShnarf The parent shnarf for the data being submitted.
* @param shnarf The indexed shnarf for the data being submitted.
* @param finalStateRootHash The L2 state root hash that the current blob submission ends on. NB: The last blob in the collection.
*/
event DataSubmittedV3(bytes32 parentShnarf, bytes32 indexed shnarf, bytes32 finalStateRootHash);
/**
* @notice Emitted when L2 blocks have been finalized on L1.
* @param startBlockNumber The indexed L2 block number indicating which block the finalization the data starts from.
* @param endBlockNumber The indexed L2 block number indicating which block the finalization the data ends on.
* @param shnarf The indexed shnarf being set as currentFinalizedShnarf in the current finalization.
* @param parentStateRootHash The parent L2 state root hash that the current finalization starts from.
* @param finalStateRootHash The L2 state root hash that the current finalization ends on.
*/
event DataFinalizedV3(
uint256 indexed startBlockNumber,
uint256 indexed endBlockNumber,
bytes32 indexed shnarf,
bytes32 parentStateRootHash,
bytes32 finalStateRootHash
);DataSubmittedV2becomesDataSubmittedV3,DataFinalizedbecomesDataFinalizedV3(DataFinalizedV2was skipped to align version numbers).- The change also introduced gas optimizations for blob submission and finalization.
- Create granular roles for contracts
LineaRollup,L2MessageServiceandTokenBridge:LineaRollup: Introduce more granular pausing and an additional verifier unsetting roleL2MessageService: Introduce more granular pausingTokenBridge: Previously, all administration functions were managed by a single owner (multisig) role. The update adds role-based access with more granular roles per function, particularly for pausing.
- Remove
finalizeBlocksWithoutProoffunction- The function enabled finalization without proofs. This allowed network activity to continue while fundamental changes, such as changing the state management hashing mechanism, were being made. This is the only time the function was used, and it was primarily retained as a contingency.
- Allow any address to finalize blocks if no finalization has occurred in the last six months
- Add functionality to the
LineaRollupcontract to allow any address to submit valid blobs and valid finalization proofs, generated by running the Linea stack locally, to withdraw funds from L2. The mechanism only works if no finalization has happened for six months. The system is intended as a contingency. - The change enables the
LineaRollupcontract to grant a "fallback operator" theOPERATOR_ROLErequired to submit the blobs and finalization proofs. The "fallback operator" is a message forwarding contract enabling any address to submit this data.
- Add functionality to the
- Bump L1 Solidity version to v0.8.26. Introduces slight gas optimizations.
- Optimize message and new token creation hashing, making it slightly cheaper to send and claim messages.
- Address non-critical findings from previous audit rounds
- Generally clean up error management and interfaces.
Alpha v3.6
Block size changes
Mainnet: September 25
Linea Sepolia: September 25
Increase block limit to 30M units of gas. The transaction limit remains at 24M. Block time also remains the same, at 2 seconds.
Alpha v3.5.2
Transaction exclusion API
Mainnet: September 23
Linea Sepolia: September 18
Introduces an API that can be used to check whether a transaction was rejected because it exceeded the sequencer's trace limits.
Alpha v3.5.1
Linea native bridge UI v2
Mainnet: September 18
Linea Sepolia: September 18
Upgrades the Linea bridge UI.
Alpha v3.5.0
finalized tag
Mainnet: October 9
Linea Sepolia: September 17
Adds support for the finalized tag to the blockParameters strings that can be used in various
JSON-RPC API calls. The tag enables you to confirm whether or not a block has been finalized on L1.
See our guide for more.
Alpha v3.4.1
Reactivate linea_estimateGas
Mainnet: September 30
Linea Sepolia: September 9
Reactivates linea_estimateGas, disabling compatibility
mode.
Alpha v3.4
Mainnet and Testnet: July 30
ENS on Linea
Adds support for Linea Names domains, including a frontend app for users to register and manage their domains. The Linea Names system is comparable to ENS on Ethereum Mainnet, except that domains are limited to one per account and registering requires completion of Proof of Humanity. As the system leverages CCIP Read, which enables L1 to trustlessly query the Linea Names registry through an offchain gateway, Linea Names domains resolve on L1.
Read more about ENS in the user guide here.
CCIP Read
One of the building blocks of ENS on Linea is a custom implementation of CCIP Read, which uses the gateway system introduced in EIP-3668 to enable Linea Names domains to resolve on L1. The key contracts created by ENS have been adjusted by the Linea team to ensure they work with Linea's Sparse Merkle Tree system.
The CCIP Read functionality can be applied to any context where a L1 protocol may benefit from securely querying data on Linea. See our page on CCIP Read for more information and guidance on how to use the relevant contracts.
The Linea repository containing the relevant contracts is here.
Consensys Diligence carried out an audit on Linea Names, available here.
linea_estimateGas mainnet activation
Available on Linea Sepolia on July 31; available on Mainnet from August 1.
Activates the linea_estimateGas endpoint for use on Mainnet in compatibility mode.
See our reference page for more information and usage.
Alpha v3.3
Testnet: June 3
Mainnet: June 11, 10:00 UTC
Breaking change: block time and block size reduction
Reducing block time to 2 seconds, with a target block size of 24M gas.
The change will increase transaction throughput by approximately 20%, improving user experience by making Linea faster and more responsive.
We recommend you adjust your node configurations to ensure any submitted transactions are handled in line with the sequencer.
Besu:
In the besu-sequencer plugin, adjust:
plugin-linea-max-tx-gas-limitto24000000plugin-linea-max-block-gasto24000000
Geth:
- In the config
.tomlfile, set[Eth]RPCGasCapto24000000- Or use
—-rpc.gascapin the command line, again specifying24000000
- Or use
Alpha v3.2
Testnet: May 28
Mainnet: June 4
Smart contract gas optimization
Upgraded smart contracts to achieve gas optimizations in several areas:
- Major gas optimizations in blob submission, primarily in
LineaRollup.sol - Finalization
- The token bridge.
The upgrade commit is available here.
Code in the upgrade has been audited by:
Bridge to a different recipient
May 29: Fully functional on testnet; ETH and USDC supported on mainnet.
June 4: Fully functional on mainnet.
The Linea bridge has been upgraded to enable recipient addresses to always be able to claim bridged funds. Bridge transfers to alternative recipients (i.e. an address that isn't the sender's address) now appear on the recipient's "Recent transactions" list, enabling them to claim.
These changes have been audited by OpenZeppelin and Cyfrin.
Alpha v3.1
Mainnet: May 14
- Introduces dynamic L1 Gwei thresholds for submitting data to L1 for finalization.
- Adds the
eth_sendRawTransactionmethod, available only via Besu endpoints.
Alpha v3.0
Summary
The main objective of Alpha v3 is to implement EIP-4844 on Linea, following its introduction to Ethereum mainnet with the Dencun upgrade on March 13.
Features
March 26: EIP-4844
Begin using blobs to post compressed L2 data to L1, with the aim of reducing data availability
costs. Blobs represent a transient data storage mechanism and an alternative to calldata, and
can be significantly cheaper in L1 ETH costs depending on market demand.
Learn more about EIP-4844
EIP-4844's arrival on Ethereum Mainnet enabled Ethereum L2s to start using a new transaction type
that transports L2 transaction and messaging data to L1 in "blobs". Blobs are a considerably
more cost-efficient alternative to the existing method of posting L2 transaction and messaging data
to L1, which involves sending calldata embedded in a transaction.
With Alpha v3, L2 transaction data is added to blobs. The savings generated by using blobs rather
than calldata mainly derive from avoiding the highly competitive L1 gas fee market.
Since transactions containing calldata have to compete with regular L1 transactions for
block space, L2s are vulnerable to L1 network congestion and the fee spikes it can generate.
Before the transition to using blobs, L1 data availability—i.e. the cost of posting data to L1
in calldata—made up more than 95% of the gas costs on Linea.
Conversely, blobs have their own fee market, completely separate to the regular gas fee market on L1. As a result, L2s like Linea now have an alternative to paying regular gas fees, and can instead compete for blob space.
Due to having an entirely new market designed for L2 data availability, the cost of using blobs
will be a fraction of the cost of using calldata.
L1 and L2 smart contracts have been updated and deployed for Alpha v3. The contract addresses are:
- New verifier contract
- Sepolia (L1): 0x5ca5dBf7Cb8F3f3c92E04B16FF5fCA1cdf147f79
- Ethereum Mainnet: 0x8AB455030E1Ea718e445f423Bb8D993dcAd24Cc4
- New L1 message service contract
- Sepolia (L1): 0xB218f8A4Bc926cF1cA7b3423c154a0D627Bdb7E5
- Ethereum Mainnet: 0xd19d4B5d358258f05D7B411E21A1460D11B0876F
- New L2 message service contract
- Linea Sepolia: 0x971e727e956690b9957be6d51Ec16E73AcAC83A7
- Linea Mainnet: 0x508Ca82Df566dCD1B0DE8296e70a96332cD644ec
Smart contract updates will be executed by the Linea Security Council using the Safe multi-sig procedure.
Additionally, all contracts have been audited by OpenZeppelin. You can find the report here.
March 27
- Block time reduced to 3 seconds. This change increases the throughput of the network to avoid any potential L2 execution bottlenecks from increased Linea activity.
- Gas fee reductions. After EIP-4844 was implemented on March 26, we monitored data for 24 hours before reducing gas fees for all users on March 27.
Breaking changes
None.
February 2024
February 19
Testnet:
- Released a higher priced version of
linea_estimateGas(this will change once the endpoint is fully functional)
Mainnet:
- Released a higher priced version of
linea_estimateGas(this will change once the endpoint is fully functional)
February 12
Testnet:
- Updated Bridge UI to v0.5.4 to support the new claiming method via Linea SDK v0.2.1
Mainnet:
- Updated Bridge UI to v0.5.4 to support the new claiming method via Linea SDK v0.2.1
February 5
Testnet:
- Deployed Linea Gas API to estimate how much gas is necessary to be included and published on Ethereum.
Learn how to use the Linea Gas API here.
Alpha v2
| Network | Target Release Date |
|---|---|
| Mainnet | February 13th, 2024 |
| Testnet | January 24, 2024 |
Summary
This release focuses on reducing L1 costs, enabling lower prices for end users.
L1 costs are primarily driven by the following:
-
Proof verification, which is essentially a fixed cost for every batch submission.
-
Hashing the batch submission data to produce the public input of the Plonk verifier.
-
Calldata costs, driven by the size of the batch submission data. This includes all the transaction data from L2, as well as messaging data (one hash per L2 to L1 message).