Please join us for our next Socratic Seminar! A special thanks to Strike for the event space.
Doors open at 6pm with discussion starting shortly after!
https://www.chicagobitcoincollective.com/
Cory Fields (MIT DCI) reported an issue which after Bitcoin Core v0.14.0 and before v29.0 a user/miner could create a specially crafted block to cause nodes to access previously freed memory. An attacker with sufficent proof of work could have exploited this attack to crash victim nodes.
https://groups.google.com/g/bitcoindev/c/e1UEdViSYkU
Yet another quantum topic. John Light posted to the mailing list about the idea of a Bitcoin lost and found where if a quantum enabled user found a wallet with Bitcoin in it and did not steal the funds how they would go about proving who owned the Bitcoin and how to return it to them.
https://groups.google.com/g/bitcoindev/c/YQmrRN0aRvE
Some notable features
https://groups.google.com/g/bitcoindev/c/suU6e-eMo44
Everyone hates dust, personally I’ve tried brooming, mopping and even a roomba. Nontheless there is still dust in my home. Bubbles proposes a mechanism to safely remove dust outputs from your wallets.
https://groups.google.com/g/bitcoindev/c/pr1z3_j8vTc
Earlier naiyoma and danielabrozzoni posted to Delving about fingerprinting nodes via addr reqeusts. In this latest post naiyoma writes about potential mitigations.
https://delvingbitcoin.org/t/fingerprinting-nodes-possible-solutions/2466
You might have heard about Lighting, Lightening, Lightning Channel jamming, what you might not know is that there is another networking layer ontop of the lightning network which is the onion messaging network. Currently there is no standard way to handle jamming attacks on that network and this post approaches that.
https://delvingbitcoin.org/t/onion-message-jamming-in-the-lightning-network/2414