Hello, I have a friend who wants to install the RDTS flavor of Bitcoin Knots on their Start9 Image. I’ve read here that it was pulled from the main Market Place and that a copy of sp9k lives on Github somewhere. Which Github link houses the 0.4.0 version of Knots-20260508?
I wish to help them get it installed.
Edited:
Options should be made available to operators regardless of Start9’s staff’s “personal” choices.
TThanks, Stu. Just to make sure I understand the situation correctly:
There was already an RDTS version of Knots built for 0.4.0 in the Marketplace, correct? I understand that Start9 has made the decision to remove that version from the Marketplace, but that still leaves an important question for operators who want to make their own choice.
On the GitHub page, it isn’t clear to me which of the available .sp9k files corresponds to the RDTS version. Was that .sp9k removed from GitHub as well, or is it still available there?
If it was removed from both the Marketplace and GitHub, is the expectation now that an operator who wants RDTS has to build the .sp9k package themselves?
I’m asking because removing the Marketplace option doesn’t necessarily mean the underlying fork or chain has failed. Chess has an opening, a middle game, and an endgame. We’ve played the opening from both sides, but we’re nowhere near knowing how the middle game plays out. There are still miners and pools operating outside the Wall Street-built ecosystem, and a slower chain isn’t necessarily a failed chain.
I’m simply trying to understand whether this is a technical limitation, or a deliberate decision to limit the operator’s available choice.
There was no separate RDTS version of Knots. Normal Knots was and still is on a forked chain and will likely stay there.
“Pre-RDTS” is Knots on the Bitcoin chain, doing everything Knots did but without signalling BIP-110.
Normal Knots has been removed from the marketplace so that people don’t install it and then ask support why nothing works, not because of any ideological/political choice. If anyone specifically wants to have nothing work for now as is OK with that, be on Bipcoin rather than Bitcoin and wait for PoW changes, they would need to sideload Knots proper.
So in your friend’s case, he’d download Knots 29.3.1 and run that. But he won’t be able to anything meaningful. No transactions, etc.
Stu, thanks for clarifying. I understand the distinction you’re making between the chain, the Knots client, and the marketplace decision.
The part I’m still trying to reconcile is the statement that:
“The s9pk remains published on GitHub for anyone who chooses to sideload it.”
I’ve followed the GitHub link in the August 9 status update, but I’m not finding an actual RDTS/“Knots proper” .s9pk artifact there. I can see the repository/build material and the pre-RDTS references, but not the installable package itself.
This also seems relevant to your earlier comment that someone wanting to run “Knots proper” would need to sideload it and that, in the example you gave, they’d “download Knots 29.3.1 and run that.”
Could you point me to the exact GitHub path or release asset for the .s9pk you’re referring to?
I’m not challenging the characterization of the fork or the current state of the RDTS chain here. I’m just trying to locate the actual package you said remains available for sideloading.
Thank you. BTW, The fork isn’t about “Bitcoin” versus “not Bitcoin.” It’s about honest chains and dishonest chains. One enforces the original rules. The other bends them to accommodate data, spam, and conjured digits.
The links Stuart provided in his second response are present on the page he linked to, in his first response. It’s your server. Please run whatever you like. The official Start9 registry only includes software that we recommend and specifically support. This will always be very limited. But that does not, in any way, speak to what YOU should run on your server. That is 100% up to you. It’s a fully open ecosystem. Anyone is free to package software for StartOS. We have made every effort to encourage such endeavors. Please see our service packaging guide:
