I’m not pleased either about the fact that knots is a one-man-team, but:

1) hopefully more devs will start contribute to knots

2) core is already a hypercentralization problem, and from their latest interview I think they know it and play on it (you don’t like what we are doing? Go run another software (which there really isn’t another real choice atm)

I think we need more software alternatives to core monopoly and this is a good situation to start acting on it

Reply to this note

Please Login to reply.

Discussion

I'll stick to core v28 until I better understand the repercussions of v29 and changing the OP_RETURN limit myself, but it's certainly not as straightforward as many people want to make it seem

So far Knots, to me at least, appears to be the worst choice. And most people promoting Knots have no clue about software security

I agree with you man, I also was thinking of staying with 28v, but:

1) I see this as simply postponing the problem (going back to what I said about future version with important bug fixes)

2) I wanted to switch to knots mostly to send a signal to core (have you seeing the live debate knots/core? Core has made statements like “btc is not monetary system, is a database” “the priority is the miners not nodes”. Cannot ignore this behaviour of theirs

Bitcoin is indeed technically just a database (multiple actually: it uses LevelDB and SQLite), but that database is also at the heart of an emerging global monetary system.

Todd refused to acknowledge that 2nd part (which is crucial context) and Mechanic almost exclusively spewed empty rhetoric and dogma. It was very disappointing tbh

But I guess this is what "rough consensus" looks like 😅

The suggested change you have doubts about is still an open PR. Bitcoin Core v29 was released a month ago without that change. It's fine to upgrade from v28.