|
| 1 | +--- |
| 2 | +layout: post |
| 3 | +type: socratic |
| 4 | +title: "Socratic Seminar 77" |
| 5 | +meetup: https://www.meetup.com/chibitdevs/events/312832542 |
| 6 | +--- |
| 7 | + |
| 8 | +## Announcements |
| 9 | + |
| 10 | +Please join us for our next Socratic Seminar! A special thanks to Strike for the event space. |
| 11 | + |
| 12 | +Doors open at 6pm with discussion starting shortly after! |
| 13 | + |
| 14 | +[Follow ChiBitDevs on twitter](https://x.com/chibitdevs) |
| 15 | + |
| 16 | +## CBC/F&C events |
| 17 | + |
| 18 | +- May 17th Founding Members Brunch (Members Only) |
| 19 | +- May 19th Tasting Table w/ chef Foise @The Chopping Block |
| 20 | +- May 21st B.O.B. Social (A focus on Bitcoin Basics) |
| 21 | +- May 28th Bitdevs 77.5 @CBC |
| 22 | + |
| 23 | +<https://www.chicagobitcoincollective.com/> |
| 24 | + |
| 25 | +## CVE-2024-52911 |
| 26 | + |
| 27 | +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. |
| 28 | + |
| 29 | +<https://groups.google.com/g/bitcoindev/c/e1UEdViSYkU> |
| 30 | + |
| 31 | +## The Bitcoin Lost and Found |
| 32 | + |
| 33 | +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. |
| 34 | + |
| 35 | +<https://groups.google.com/g/bitcoindev/c/YQmrRN0aRvE> |
| 36 | + |
| 37 | +## Bitcoin Core v31.0 released |
| 38 | + |
| 39 | +Some notable features |
| 40 | +- New “cluster mempool” architecture. |
| 41 | +- Better RBF and transaction relay logic. |
| 42 | +- Private transaction broadcast over Tor/I2P. |
| 43 | +- New mempool inspection RPCs. |
| 44 | +- Embedded asmap support included. |
| 45 | +- Default -dbcache increased to 1024 MiB. |
| 46 | +- Fee estimation now supports 0.1 sat/vB. |
| 47 | +- New REST endpoint for partial block downloads. |
| 48 | +- Qt GUI upgraded to 6.8. |
| 49 | +- Deprecated fee and networking options removed. |
| 50 | +- Mining IPC interface updated/breaking changes. |
| 51 | +- Bitcoin Core 28.x and older are now EOL. |
| 52 | + |
| 53 | +<https://groups.google.com/g/bitcoindev/c/suU6e-eMo44> |
| 54 | + |
| 55 | +## [BIP Draft] Dust UTXO Disposal Protocol |
| 56 | + |
| 57 | +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. |
| 58 | + |
| 59 | +<https://groups.google.com/g/bitcoindev/c/pr1z3_j8vTc> |
| 60 | + |
| 61 | +## Fingerprinting nodes: Possible Solutions |
| 62 | + |
| 63 | +Earlier naiyoma and danielabrozzoni posted to Delving about fingerprinting nodes via addr reqeusts. In this latest post naiyoma writes about potential mitigations. |
| 64 | + |
| 65 | +<https://delvingbitcoin.org/t/fingerprinting-nodes-possible-solutions/2466> |
| 66 | + |
| 67 | +## Onion Message Jamming in the Lightning Network |
| 68 | + |
| 69 | +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. |
| 70 | + |
| 71 | +<https://delvingbitcoin.org/t/onion-message-jamming-in-the-lightning-network/2414> |
0 commit comments