Release v1.8.0 (MAINNET)

This release fixes a missing default value in the recent v1.7.0 release. v1.8.0 is scheduled for activation on Friday, Feb 13 2026 @ 10am PST / 1771005600.

Latest Docker Images

• blastio/blast-optimism:mainnet or blastio/blast-optimism:mainnet-v1.8.0
• blastio/blast-geth:mainnet or blastio/blast-geth:mainnet-v1.8.0

Note: op-node requires the following additional CLI flags. Be sure to use the v1.8.0 timestamp of 1771005600 for bpo2Blastblobschedule.

--override.osakablobschedule=prague
--override.bpo1blobschedule=prague
--override.bpo2blobschedule=prague
--override.bpo2Blastblobschedule=1771005600

Or if using environment variables:

OVERRIDE_FUSAKABLOBSCHEDULE=prague
OVERRIDE_BPO1BLOBSCHEDULE=prague
OVERRIDE_BPO2BLOBSCHEDULE=prague
OVERRIDE_BPO2BLASTBLOBSCHEDULE=1771005600

Release v1.7.0 (MAINNET)

This release introduces a number of fixes to the blob fee schedule and and is scheduled to activate on Thursday, Feb 12 2026 @ 10am PST / 1770919200.

Latest Docker Images

• blastio/blast-optimism:mainnet or blastio/blast-optimism:mainnet-v1.7.0
• blastio/blast-geth:mainnet or blastio/blast-geth:mainnet-v1.7.0

Note: op-node requires the following additional CLI flags:

--override.osakablobschedule=prague
--override.bpo1blobschedule=prague
--override.bpo2blobschedule=prague
--override.bpo2Blastblobschedule=1770919200

Or if using environment variables:

OVERRIDE_FUSAKABLOBSCHEDULE=prague
OVERRIDE_BPO1BLOBSCHEDULE=prague
OVERRIDE_BPO2BLOBSCHEDULE=prague
OVERRIDE_BPO2BLASTBLOBSCHEDULE=1770919200

Release v1.7.0 (TESTNET)

This release introduces a number of fixes to the blob fee schedule and and is scheduled to activate on Tuesday, Feb 10 2026 @ 2pm PST / 1770760800.

Latest Docker Images

• blastio/blast-optimism:sepolia or blastio/blast-optimism:sepolia-v1.7.0
• blastio/blast-geth:sepolia or blastio/blast-geth:sepolia-v1.7.0

Note: op-node requires the following additional CLI flags:

--override.osakablobschedule=prague
--override.bpo1blobschedule=prague
--override.bpo2blobschedule=prague
--override.bpo2Blastblobschedule=1770760800

Or if using environment variables:

OVERRIDE_FUSAKABLOBSCHEDULE=prague
OVERRIDE_BPO1BLOBSCHEDULE=prague
OVERRIDE_BPO2BLOBSCHEDULE=prague
OVERRIDE_BPO2BLASTBLOBSCHEDULE=1770760800

Release v1.4.0: Fusaka Hardfork (MAINNET)

This release maintains compatibility with Ethereum Mainnet's Fusaka hardfork.

Latest Docker Images

• blastio/blast-optimism:mainnet or blastio/blast-optimism:mainnet-v1.4.0
• blastio/blast-geth:mainnet or blastio/blast-geth:mainnet-v1.4.0

These images contain the latest updates for mainnet-compatible deployments of Blast Optimism and Blast Geth.

Release v1.4.0: Fusaka Hardfork (TESTNET)

This release maintains compatibility with Ethereum Sepolia's Fusaka hardfork. There will be an analogous release for Blast Mainnet in the near future.

Docker Images

• blastio/blast-optimism:sepolia or blastio/blast-optimism:sepolia-v1.4.0
• blastio/blast-geth:sepolia or blastio/blast-geth:sepolia-v1.4.0

These images contain the latest updates for Sepolia-compatible deployments of Blast Optimism and Blast Geth.

Release v1.3.0: Taiga Hardfork (MAINNET)

The Taiga hardfork for Blast Mainnet activates on Wednesday, May 7, 2025 at 10:05:11 AM UTC (1746612311). This is the same timestamp that the Prague upgrade activates on Ethereum Mainnet. Node operators must upgrade both blast-geth and blast-op-node.

⚠️ Don’t forget to update your rollup.json when upgrading. Alternatively, if you’re using environment variables or CLI flags:

Environment Variable:

OP_NODE_OVERRIDE_TAIGA=1746612311

CLI Argument:

--override.taiga=1746612311

Changelog:

• Support for Prague’s L1 Header format, including the new RequestHash field. Also adds support for the new SetCodeTx type, but does not activate it for use on Blast.
• MaxSequencerDrift is now a fixed constant of 1800 seconds (30 minutes) instead of a configurablerollup.json parameter. (You may leave the old parameter in rollup.json; it will be ignored.)

Latest Docker Images

• blastio/blast-optimism:mainnet or blastio/blast-optimism:mainnet-v1.3.0
• blastio/blast-geth:mainnet or blastio/blast-geth:mainnet-v1.3.0

Release v1.3.0: Taiga Hardfork (TESTNET)

Taiga is an L2 hardfork impacting Blast TESTNET. The fork time for this upgrade is Friday, April 25 2025 @ 2pm UTC / 1745589600 .
Changelog:

1. Activates the optional hardfork pectra_blob_schedule_time . Note: this will only impact TESNET.
2. Increases sequencer drift to 30 minutes (1800 seconds) similar to fjord upgrade on OP Stack chains.

Docker Images

• blastio/blast-optimism:sepolia or blastio/blast-optimism:sepolia-v1.3.0
• blastio/blast-geth:sepolia or blastio/blast-geth:sepolia-v1.3.0

These images contain the latest updates for Sepolia-compatible deployments of Blast Optimism and Blast Geth.

⚠️ Please remember to update the rollup.json configuration when upgrading your node software. The latest version can be found HERE. Failure to update this file may lead to incompatibility or unexpected node behavior.

Release v1.2.3: Bugfix for testnet trace api (TESTNET)

This release fixes a bug with the debug_traceCall RPC endpoint which broke due to the recent changes for Ethereum's Pectra hard fork. Note: this is a testnet-only release.

Deployment instructions

You can find prebuilt docker images for this release at the usual deployments repo.

For advanced users who wish to build their own images from source, refer to these docs here.

Release v1.2.2: Bugfix for testnet estimate gas (TESTNET)

This release fixes a bug with the estimate gas RPC endpoint which broke due to the recent changes for Ethereum's Pectra hard fork. Note: this is a testnet-only release.

Deployment instructions

You can find prebuilt docker images for this release at the usual deployments repo.

For advanced users who wish to build their own images from source, refer to these docs here.

Release v1.2.1: L1 Pectra hard fork bugfixes (TESTNET)

This release includes bug fixes to the previous set of changes that added support for Ethereum's Pectra hard fork. Note: this is a testnet-only release.

Deployment instructions

You can find prebuilt docker images for this release at the usual deployments repo.

For advanced users who wish to build their own images from source, refer to these docs here.