I did a little more digging. So please correct me if this is not right.

Luke used to work with the original “Bitcoin Core” and the older developers there before it was called bitcoin core.

He received a lot of pushback after many attempts to implement a few things so created “Knots.”

Copied (not plagiarized) Core then added some changes. Nothing that will break the system, but allows me to be able to configure my settings on Knots.

One would logically think that he runs the code by at least one other person before he pushes it to primetime. I mean…. I’m sure that he has a lot more to lose than I do if something goes wrong with Knots or bitcoin.

Besides that isn’t his best buddy one of the best coders this side of the planet? Jason wk057? (I saw this guy take a part a Tesla and swap the high voltage battery out before anyone knew that you could do that.

If it were me and I was in his position I would ask my best friend to review my code. BUT being my best friend I wouldn’t have to work for him. I would do it because we are striving for the same goal.

My conclusion:

#runknots

#bitcoin

#bitcoinmining

#tothebitcoinceo

#mynodemychoice

Reply to this note

Please Login to reply.

Discussion

I like to believe/trust as well...

But #Bitcoin is about verifying.

Since so few can (me mostly included) perhaps it is time to freeze the Bitcoin release ?

I don't trust democracy anymore, I have seen that most people are corrupt-able or else can be blackmailed way too easy.

I mean, the freedom of mankind is at stake....

I would think that your approach is the best one. The update is unpopular so freeze the release. Core will surely do that unless there is another motive. I think Vortex may have just clued us in to what the motivation would be. Long hours and little to no pay. They do deserve fair pay, but not at the expense of bitcoin and the changes they want to make.