Nakamoto Activation Update: Core Developers Ship Release Candidate 2, Adjust Hard Fork Block Selection
Hey Stackers, here’s the latest from the Core Developers:
After the successful hard fork of the Nakamoto Testnet last week they further updated the test net with the latest stacks-core software Release Candidate 2 which contains improvements and fixes from this past week. As they continue to work with builders, Signers, and others, they have decided to wait on picking a new block this week and instead plan to select one next week after they hard fork the Primary Stacks Testnet with this same rc2.
After the successful hard fork of the Nakamoto Testnet last week they further updated the test net with the latest stacks-core software Release Candidate 2 which contains improvements and fixes from this past week. As they continue to work with builders, Signers, and others, they have decided to wait on picking a new block this week and instead plan to select one next week after they hard fork the Primary Stacks Testnet with this same rc2.
New Hard Fork Block Selection
The decision to wait just a bit in selecting a new hard fork block for the Nakamoto activation is primarily based on the following two reasons:
Given the extensive months of testing—including apps that participated in the incentivized testnet program run during the Instantiation step, ongoing fuzzing and pen testing by full-time Stacks Residents, multiple audits, and the onboarding of new auditors—core developers are confident in the release and are happy to support any builders, Signers, or others that would like to continue working with the testnet. Builders are encouraged to reach out if they would like support beyond the documentation.
- Release Candidate 2 shipped today and core developers would like to see it live on Nakamoto Testnet over the weekend before forking the Primary Testnet. While there isn't a significant amount of new code, they still want to observe a minimum period of stability as they would with any new RC.
- A number of builders have expressed a desire to work with the testnet longer and to see the primary testnet upgraded before the mainnet hardfork block is picked.
Given the extensive months of testing—including apps that participated in the incentivized testnet program run during the Instantiation step, ongoing fuzzing and pen testing by full-time Stacks Residents, multiple audits, and the onboarding of new auditors—core developers are confident in the release and are happy to support any builders, Signers, or others that would like to continue working with the testnet. Builders are encouraged to reach out if they would like support beyond the documentation.
Timeline
Make sure you’re prepared for the hard fork
- 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 already, but you have until the end of cycle #93 to participate in the next cycle. 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.
Thank you, Core Devs!
We want to continue to extend our thanks to the core developers who have worked tirelessly to bring Nakamoto to life. Their dedication, late nights, and commitment are the backbone of this effort, ensuring that the Stacks ecosystem continues to evolve securely and seamlessly.