From 501319f8a24636364b79377cd7eff069d34b7f1f Mon Sep 17 00:00:00 2001 From: Mitchell Cuevas Date: Thu, 17 Oct 2024 15:47:37 +0000 Subject: [PATCH] GITBOOK-200: Signer page updates for new block --- guides-and-tutorials/running-a-signer/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/guides-and-tutorials/running-a-signer/README.md b/guides-and-tutorials/running-a-signer/README.md index 1c48340715..f5c1a1a93c 100644 --- a/guides-and-tutorials/running-a-signer/README.md +++ b/guides-and-tutorials/running-a-signer/README.md @@ -1,9 +1,9 @@ # Run a Signer {% hint style="info" %} -The block for Nakamoto activation has been chosen as Bitcoin block 864,864, which is currently expected on October 9th. This block is subject to change should core developers need additional time for testing or unexpected issues. +The block for Nakamoto activation has been chosen as Bitcoin block 867,867, which is currently expected on October 29th. 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. Ideally, you will have Stacked for Cycle #94 ahead of time, any time now is good. +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. {% endhint %} {% hint style="info" %}