Join Nostr
2026-06-09 15:42:06 UTC

Cyph3rp9nk on Nostr: If anyone has X, would you be so kind as to forward this message to start9? ...

If anyone has X, would you be so kind as to forward this message to start9?
quoting


I have been reviewing the Bitcoin Knots (pre-RDTS) package for StartOS and I think there is something important that needs clarification.

In the UI it appears installed as:

`Bitcoin Knots (pre-RDTS)`

but in the package source code `#knotsprerdts:29.3:10` I can see that the `manifest` builds with:

`VERSION: "29.3.knots20260508"`

And the README itself says that this flavor:

> “ships the same Bitcoin Knots binary as #knots without the Activate RDTS critical-task gate”.

In addition, the migration notes state that `#knots` and `#knotsprerdts` use the same upstream binary, and that switching to this flavor removes `consensusrules=rdts`.

The issue is that, on startup, the log still shows:

`This version of Bitcoin Knots applies the BIP110 (RDTS) network upgrade`

and also:

`This node will STILL enforce them`

This leads me to think that the flavor called **pre-RDTS** is not actually using a binary without RDTS, but rather the same RDTS binary, only without the critical confirmation task in StartOS.

If that is correct, the name **pre-RDTS** could be misleading: removing `consensusrules=rdts` would not prevent RDTS from being applied; it would only remove the explicit confirmation step.

Can Start9 clarify whether `Bitcoin Knots (pre-RDTS)` actually runs a binary without RDTS support, or whether it simply removes the activation gate/task?

I think it is important for users to know exactly which rules their node is enforcing.
Author Public Key
npub1lnms53w04qt742qnhxag5d6awy7nz6055flnmjkr6jg39hm86dlq7arrnt