Nakamoto Activation: Core Developers Have Selected A Hard Fork Block
Drum roll Stackers, it’s time to meet the Nakamoto hard fork block. 🟧

Selecting the block for the hard fork to occur is the 3rd step in the Nakamoto Activation Sequence (pictured below), meaning we now know just about when we can expect fast blocks and Bitcoin finality.

Before we get right to it, please understand there are important caveats, direct from the core developers themselves. First and foremost, all core contributors are committed to a safe, secure launch. As such, if anything surprising (even suspicious!) comes up, they reserve the right to select a new hard fork block should they require more time to investigate.

Broadly speaking, issues could include:
  • Testnet hard fork complications
  • Bugs found in ongoing testing
  • Unexpected or new Signer/miner needs
  • Glitches in the matrix
  • Crud in the capacitor
  • …you get it.
With all that understood, let’s…
Meet our 🟧:
Lucky Bitcoin block number #864864, is currently expected on Wednesday, October 9th.
Countdown
So you always know 'wen Nakamoto?'
Key aspects of this hard fork:
  • STX will not be unlocked
  • Sync from genesis is not required
  • If you do not upgrade on time, your node will be dropped from the network
Testnets
A hard fork on the Nakamoto Testnet is expected the week of September 23rd. Primary Testnet, following a successful fork of Nakamoto Testnet the week before, will occur the week of September 30th. The Nakamoto Testnet hard fork must be smooth and not surface additional bugs to proceed to the hard fork of the Primary Testnet. Again, any unexpected issues on these testnets could warrant selecting a later hard fork block.

The most helpful thing you can do is support testnet by using it, especially Signers!
How to handle the hard fork:
First, all node operators should upgrade their nodes! Binaries will be provided roughly a week before the hard fork. The hard fork/upgrade should be relatively straightforward, you can follow your usual steps for upgrading your nodes and rebooting.

If you are not signed up to receive release updates via email, we recommend it.

  • Signers: Make sure you’re running the latest Signer binary and have upgraded any nodes you are running. Ideally, you will have Stacked for Cycle #94 ahead of time, any time now is good.
  • This will ensure the stacking min by weight.That’s it, reach out to your ecosystem point of contact if you need any support.
  • Miners: Upgrade to the latest release following your normal procedure.
  • Exchanges: Upgrade following your normal procedure - this upgrade does not require a sync from genesis.
  • Developers (App Builders): Make sure your app is ready to work with fast blocks and many blocks between Bitcoin blocks!
  • Stackers: No action required. If you are Stacking, your funds will remain Stacking, no-Restacking required.
  • Users/Holders: No action required, your funds will remain safe in your wallet, no token transfers or redemptions are necessary.
  • Everyone: Buckle your seatbelts for fast blocks

Very exciting times; I want to thank the core developers for their radical efforts as well as transparency. In a truly decentralized ecosystem like Stacks, everyone gets a front-row seat to the nitty gritty of a rollout like this whereas other ecosystems might just drop something out of a black box. Here’s to supporting them in delivering a safe launch in this home stretch! Stay tuned for further updates and keep that Naka•mojo!
~
The Nakamoto Activation Sequence: