Nakamoto Activation Guide for Signers
The block for Nakamoto activation has been chosen as Bitcoin block 867,867, which is currently expected on October 28th. This block is subject to change should core developers need additional time for testing or unexpected issues.
Binaries will be provided roughly a week in advance and your normal upgrade procedure should apply here, you’ll want to be running the latest node and Signer software. Note that if you do not upgrade ahead of the hard fork, your nodes will be dropped from the network.
Testnet Activation Window (August 19)
This initial phase focuses on testing Signer 3.0 readiness in a testnet environment (Primary Testnet).
Action Required:
Update stacks-node to version 3.0.0.0.1 (here)
Update signer to version 3.0.0.0.0.1 (here)
Run a Primary Testnet node alongside your Signer
Create a testnet wallet address
Complete the provided form (here)
Await testnet STX delegation from our team
The goal(s) of this phase is to: monitor for issues, implement fixes, and test Signing and Signer hand-off for multiple Epoch 2.5 cycles.
Moving forward, please report any Signer-related bugs, issues or feature requests using the issue template in the stacks-core repo (here)
Mainnet Activation Window (Starting August 28)
Pending successful testnet phases, we will initiate the mainnet activation window.
Action Required:
ALL Mainnet Signers must update to the latest Stacks-Core and Signer binary versions (specifics to be confirmed)
We will test for at least 1.5 Stacking Cycles to ensure stability.
Key Points
Your participation in all phases is crucial
Report any issues or unexpected behavior immediately
Stay alert for further communications
Conclusion
Your dedication to the Stacks network's security and efficiency is invaluable. We appreciate your prompt attention to these critical steps and your ongoing support.
For any questions or concerns, please don't hesitate to reach out.
Thank you for your commitment to the Stacks ecosystem.
Last updated