An update on this thread, for full clarity: There are now a total of 8 new bugs which can cause wallet deletion or corruption.

My initial comment applies only to the initial, severe bug that affects people simply using Core30 normally.

nostr:nprofile1qqsg3mj8tuxhxvy5w0qt9altpgcrqttdfxg9glvsdfhkpa3plcxfudgpzpmhxue69uhkummnw3ezumt0d5hszrnhwden5te0dehhxtnvdakz7qgawaehxw309ahx7um5wghxy6t5vdhkjmn9wgh8xmmrd9skctckum9s8 _is_, however, impacted by 6 of the others, which are not triggered by normal end users:

3 of these are "power user" functionality (moving wallet files around manually; creating unexpected files in the wallet directory; or using the `bitcoin-wallet` command line tool)

1 of them requires a low-level disk/filesystem/OS problem during shutdown.

The remaining 2 are unrealistic to trigger at all, but hypothetically possible if you start the node software again immediately before it finishes shutting down (within milliseconds), or ... have multiple wallets in the same directory, one of which has recent changes, the node crashes or has a power failure, you start the node again and NOT open the recently-modified wallet, open the other wallet, and shutdown cleanly.

All six of these issues will be fixed in a new version of Knots soon.

nostr:nevent1qqs0j7gkpecnmx4qvhxf585pw3cmpj4fxv537uswn3zm5tgknw6kyscpz4mhxue69uhhyetvv9ujuerpd46hxtnfduhsyg8a6h50dtsdhqtmuzm3mgsynrqcq6tgmznyt92ecfylxgh6wdry5upsgqqqqqqsc8qzjl

Reply to this note

Please Login to reply.

Discussion

Re "new bugs", note that I mean newly discovered.

At least one of these dates back to 2013 (v0.8.0).

Stoked to run knots! Deleted core 30 👽

Thank you for your commitment to commits nostr:npub1lh273a4wpkup00stw8dzqjvvrqrfdrv2v3v4t8pynuezlfe5vjnsnaa9nk

Looking forward to seeing you again next week in Naples.

And let's give the reward to Andreas Antonopoulos...

ok, tks for clarification and job.

Indeed, I'll keep my knots updated 🪢👍

It was a point brought up on nostr:nprofile1qqs879mhq6kkuzh2wk57xdzanl76uem8d7hlyjd7v4a4jcm4u88d8ygprpmhxue69uhhqun9d45h2mfwwpexjmtpdshxuet5qydhwumn8ghj7un9d3shjtnzd96xxmmfdecxzunt9e3k7mgxzfkn5 last week, they wasn't sure at the time whether Knotts was affected but it has been confirmed here. I'm not interested in big dick contests tbh, im interested in the state of the network.

Bitcoin already won. Everyone is just looking for something to argue about now - it’s fiat mentality. No simping just rationalising all of the data I see in front of me.

This complacency is letting shitcoin core devs destroy the monetary property of the bitcoin...!!!

I'm not sure what complacency you're referring to. We are talking on a protocol where we can transact micro payments between each other with zero intermediary.

I've been in the space since 2016, my money has been safe, sound, and secure since then. If you have an issue with the software, you simply don't have to run it, or update it. Thats the power of a decentralised network.

And it's just turned 17 years old.

another confirmation that Bitcoin Knots was not affected and only V30 and V30.1 were affected

Shitcoin core devs always fear nostr:nprofile1qqs0m40g76hqmwqhhc9hrk3qfxxpsp5k3k9xgk24nsjf7v305u6xffcwac93l's relentless work and honesty towards bitcoin code and this is one of the reasons why they have been attacking Luke for several years now and I don't think these attacks will stop anytime soon (at least until plebs and bitcoin miners (not hashers) obliterate shitcoin core)

This is what bitcoin needs more than anything else if plebs want to see OMEGA CANDLES in bitcoin price but unfortunately only ~50 plebs get it (for now).

END THE SHITCOIN CORE BY RUNNING RDTS/BIP110 (AKA BIP444) ON YOUR NODE

nostr:nevent1qqs2v44d5pv5hzyphst4lgemjm0xqndjr2ruyqm7xzy7987q2jx3wlspz3mhxue69uhkummnw3ezummcw3ezuer9wcpzplw4arm2urdcz7lqkuw6ypyccxqxj6xc5eze2kwzf8ej97nnge98qvzqqqqqqyfht9yc

You're amazing.

🙏🏿🙏🏿 Thanks Luke

Appreciate your forthright approach to this important project!

Kudos!