Bitcoin knots update 29.4.2

Bitcoin
1

Bitcoin knots update 29.4.2

if you agree with the changes you should update as soon as possible.

I’m lazy so I’ll just put below the description of the update from lazarus pool.

“From block 973440 (~22 Sep) to 979920 (~5 Nov) every newly mined coinbase must wait 45 days before it can be spent, instead of 100 blocks. It is temporary, and it exists to make hit-and-run mining unprofitable and give miners who stay an edge. Payouts, shares and the split do not change; coins from those blocks just unlock at block 979920 (make-goods too). Lazarus supports it and our nodes switch at block 973400. DATUM gateway operators run their own node, so the choice is yours: to support it, run Knots 29.4.2 before block 973440.”

4 Likes
2

Also, the latest version of Bitcoin Knots (BLAKE2b) Companion is built from this release, so update it if you are running it.

Note that the companion nodes are pruned by default, so if you wait for too long to update and the block height that 001 mentioned passes out of the window, you will have to reindex after updating (which is a full IBD on a pruned node).

So update sooner than later.

6 Likes
3

I updated my Start9 knots just before the 973440 block via Registry: start9.mempool.guide to knots:29.4.2:3 which I assume came from the latest non-RC version Release v29.4.2.knots20260508 · Retropex/knots-startos · GitHub as apposed to the RC Prerelease Release v29.4.2.knots20260508rc2 · Retropex/knots-startos · GitHub . Everything went very smoothly no issues.

1 Like
4

MY Start9’s Bitcoin Knots (BLAKE2b) Companion from you is updated but why does the Electrs Pruned keep syncing and re-syncing. Is it not stable?

5

How is it configured?

1 Like
6

I configured it the way you said in your notes!

7

We have discussed several configurations, so I honestly have no idea how your server is currently set up. Which node currently is it configured to point to (Actions & Config > Select Node)?

1 Like
8

Bitcoin Knots (BLAKE2b) Companion

9

Great. And has Bitcoin Knots (Blake2b) Companion completed the IBD and all of the health checks green?

If you watch Bitcoin Knots (Blake2b) Companion a few minutes, does it restart, or stay stable and running?

Did you have Electrs Pruned pointed at another node long enough for it to complete indexing before you pointed it at Bitcoin Knots (Blake2b) Companion?

Please DM me the full downloaded log (as a .txt file attachment, not as a wall of text in the message) from Electrs Pruned soon after it has the problem.

1 Like
10

Update to the latest release, and let me know if you are still seeing the problem.

1 Like
11

Fully synced. Thanks. Also updated Bitcoin (Pre-RDTS) from the Community registry. Deleted Bitcoin SHA256 Companion.

So, what next to start mining Blake2b/XBT?

12

First yes: 1):
" Health Checks

|Name|Status|
| — | — |
|RPC|The Bitcoin RPC Interface is ready|
|Chain|Following the BLAKE2b chain (974057)|
|Blockchain Sync|Bitcoin is fully synced|
|I2P|Inbound and outbound connections|
|Tor|Inbound and outbound connections|
|Clearnet|Outbound only. Publish an IP address to enable inbound.|
|RPC Proxy|The Bitcoin RPC Proxy is ready|

Uptime

2Days

18Hours

55Minutes

13Second"

2). No, it is stable all the time:
" Bitcoin Knots (BLAKE2b) Companion 1.0.0:37"

I might have had Electrs Pruned pointed at another node at first yes, till I changed it to Blake2b companion.

<redacted for privacy> (1.8 MB)
Here goes the log file for Electrs Pruned just now:
It seems to be stable enough this time after the update.
Loooking forward to hearing from you. Thanks.