Epoch 3.4 Testnet hard fork (roughly 1700 UTC March 26, 2026)

Epoch 3.4 is scheduled to activate on testnet at block 159350, which is roughly 1700 UTC March 26th.

If you’ve already upgrade to the rc1 release, be sure to upgrade to rc2

All testnet node operators are required to upgrade nodes by then to ensure they are compatible with the hard fork.

Additionally, a configuration update is required for this update. In the stacks-node configuration file, ensure this section is added to the bottom of the config file (immediately after the [[burnchain.epochs]] 3.3 section):

[[burnchain.epochs]]
epoch_name = "3.4"
start_height = 159350

Binary releases are available at Release Release 3.4.0.0.0-rc2 · stacks-network/stacks-core · GitHub

If running a testnet signer, the release candidate of the stacks-signer is required for this version, available here: Release Release signer-3.4.0.0.0.0-rc2 · stacks-network/stacks-core · GitHub.

Docker images are published at:
stacks-node: stacks-core versions · stacks-network · GitHub

stacks-signer: stacks-signer versions · stacks-network · GitHub

For node operators running an API, there is an update that will be required for this release.

Docker Image: Image Layer Details - hirosystems/stacks-blockchain-api:8.15.1

This release implements the following SIPS:
SIP-039: SIP-039: Clarity 5 and Epoch 3.4 by brice-stacks · Pull Request #256 · stacksgov/sips · GitHub
SIP-040: SIP-040: SIP for improved post-conditions by brice-stacks · Pull Request #257 · stacksgov/sips · GitHub
SIP-042: SIP-042: Removal of `at-block` by francesco-stacks · Pull Request #262 · stacksgov/sips · GitHub

Ref: Chain State Pruning and `at-block` Proposed Change

1 Like