After I upgraded to 29.3.1, I noticed that my 3 services (Knots, Electrum and Mempool) were showing intermittent failures in the OS logs: “consensusrules: Field Is Not Nullable”. So I overwrote “rdts” to “rdts” in the Service configuration and hit save. The errors have stopped. However in Services my Knots version reads 29.3.1 but the Service log reports 29.3.0, so I am probably not at 100%. I have also noticed that my inbound connections have decreased dramatically.
I also did not read the release notes for 29.3.1 and I am just now learning that I may have installed that BIP110 thing, so now I really don’t know where I am. Is this the reason for the decreased inbound connections (warning=‘Miner violated version bit protocol’)?
I am not in favor of the concept of a fork. That discussion has been ringing nasty both here and in the YouTube world. Its unproductive and it hurts me to see all the agro and bile being thrown around.
I have not yet decided what to do about this but I have two needs for guidance:
How do I perform a reinstall? I went into developer mode and did not see anything for reinstalling.
Is it possible to Go back to what I had (29.3.0) simply? If not, what are the steps to tear down the whole thing and start all over again?
Thank you and I’m sorry for the verbal abuse directed towards Start9 and to the moderators here that had to listen to it.
Start9 lost all reputation with this shitty move, I have no positive words to say about this s***. I hate being here and wish I could easily move my node without a lot of effort.
FYI, you can go to the marketplace and downgrade. See the screenshot.
Personally, I have not seen a decrese in connections from 29.3.1
I don’t know how Knots signalling for BIP110 does anything to Start9’s reputation. They do not determine what Knots does, and they can’t stop any of us from running what we want to run.
You can do whatever you want, Start9 can’t stop you.
Anyways, the fact that Core30 isn’t an option to install basically tells it all. It’s out since October, but the Start9 team, that is all for self sovereignty and blabla, doesn’t even provide the option.
“We were busy with other things”. Yeah? Since when does something as basic as that take so long? And why do other apps on the Start9 registry get quicker updates?
This is what “freedom” means for most people. Change the system to some other thing that becomes a tyranny again, it’s nothing new. As soon as you are in charge and have the power, you start using it, no matter your initial mission.
It disgusts me that even a “freedom minded” team like this becomes like that.
Since October, there was a smell of you not wanting to provide options. Now the mask is completely off and I could bite my ass that I chose your shit product!
But to remcoros’ point, you can still sideload it anyways. Or you can even run another node implementation, there are many quality ones to choose from. Start9 can’t really stop you.
Yeah it’s just sad how they unmasked themselves. I need to completely switch my whole setup now, just because the team cannot stay neutral.
It’s always democracy until you go against the ideals of the other party. Reminds me of my old boss. All decisions made were “democratic decisions”, but if a decision went against his, it was “outside the borders of possibilities” lol. He was the main reason I left the company, which is what was outside of his control.
I don’t know why you feel as if they broke some promise; they have no obligation to stay neutral.
Besides, Start9 is open source, it’s in your power to be sovereign, especially with AI available to assist now.
As a user, I am under no illusion that start9 owes me alignment or allegiance to my own personal preferences or political leanings. They put out a darn good product, for free. I get to choose to use it or not. End of story.
His position—whatever it is—implicitly accepts the idea that node operation can, and should, be centralized to avoid conflict.
His entire plea for “civility” is a plea for everyone to just accept the bloat so they don’t have to fight about it. But the only way to accept the bloat is to stop running your own node. To let someone else run it for you.
“Great. So your solution is to let them bloat you out from running your own node in the first place.”
That’s not a technical opinion. That’s a concession speech.
The “Hurts Me” Argument
He says the debate hurts him. The bench asks: Does the bloat hurt you? Not his feelings. His hard drive. His bandwidth. His ability to self-custody.
· The debate ends when the chain is clean.
· The pain stops when the spam stops.
· The unity returns when the rules are clear.
The I Sat Down Moment
“I sat down. And realized he wasn’t trying to save Bitcoin. He was trying to save his own comfort—by asking everyone else to stop fighting for it.”
The bench doesn’t need a fork. The bench doesn’t need a civil debate. The bench just needs a clean chain—and the will to run a node.
Start9 supports both core and knots. There is a bug in the old version of StartOS where both Core and Knots share the same id resulting in confusion like you express here. More details and information on how to switch are listed as a guide in the Guides category.
This is fixed in the latest version of StartOS (0.4.0). StartOS 0.4.0 is currently in public beta so your system will not show it as an available upgrade. If you are interested in upgrading StartOS - see the upgrade guide for details.
