pull down to refresh

Additional context for "DoS due to inv-to-send sets growing too large"x.com/0xB10C/status/1844705899455062220
349 sats \ 3 comments \ @0xB10C 11 Oct 2024 bitcoin
related
Notes on 'DoS due to inv-to-send sets growing too large' from May 2023b10c.me/observations/15-inv-to-send-queue/
11.5k sats \ 3 comments \ @0xB10C 24 Jun bitcoin
Why happen force closures on LN channels?
14.7k sats \ 18 comments \ @DarthCoin 23 Aug 2024 bitcoin
Dissection of a force-close that already cost me 140k sats
10.2k sats \ 21 comments \ @C_Otto 31 Dec 2023 lightning freebie
PR closed: datacarriersize: Match more datacarrying by luke-jrgithub.com/bitcoin/bitcoin/pull/28408
2997 sats \ 14 comments \ @niftynei 9 Jan 2024 bitdevs
Tor now has a PoW based DoS mitigation feature in v0.4.8.1a with new algo Equi-Xforum.torproject.net/t/alpha-release-0-4-8-1-alpha/7816
2281 sats \ 6 comments \ @janowitz 5 Jun 2023 bitcoin
Zaps Failing, Fragility, and Bet Update
7361 sats \ 55 comments \ @denlillaapan 15 Jan meta
Bitcoin Core: Disclosure of DoS due to inv-to-send sets growing too largebitcoincore.org/en/2024/10/08/disclose-large-inv-to-send/
437 sats \ 0 comments \ @0xB10C 11 Oct 2024 bitcoin
DoS Disclosure: LND Onion Bombdelvingbitcoin.org/t/dos-disclosure-lnd-onion-bomb/979
1878 sats \ 3 comments \ @Rsync25 18 Jun 2024 lightning freebie
[bitcoin-dev] Full Disclosure: CVE-2023-40231 / CVE-2023-40232 / CVE-2023-40233lists.linuxfoundation.org/pipermail/bitcoin-dev/2023-October/021999.html
3804 sats \ 13 comments \ @Rsync25 16 Oct 2023 bitcoin
[Lightning-dev] Disclosure: Fake channel DoS vectorlists.linuxfoundation.org/pipermail/lightning-dev/2023-August/004064.html
1663 sats \ 1 comment \ @Rsync25 24 Aug 2023 bitcoin
Niklas Gögge on denial-of-service bugs in LNDbrink.dev/blog/2023/12/22/dos-bugs-lnd/
3597 sats \ 0 comments \ @Rsync25 22 Dec 2023 bitcoin
remote bitcoin core killer?? OOM from bad peer conn msgsx.com/123456/status/1741922597908959701
2630 sats \ 7 comments \ @niftynei 6 Jan 2024 bitdevs
MAD Transactions: Mutual Assured Destruction Transactionsmedium.com/@idBrain/mad-transactions-mutual-assured-destruction-transactions-c04f7b5a2fa7
1909 sats \ 6 comments \ @fiatjaf 3 Jan 2023 bitcoin
I2P is experiencing a Denial-of-Service attackteddit.net/r/i2p/comments/10v9uxp
855 sats \ 8 comments \ @cryptocoin 7 Feb 2023 bitcoin
Summation of retiring the 80-Byte OP_RETURN Limit by instagibbsgist.github.com/instagibbs/c436110890ab25aa9997b13c2270d5ce
767 sats \ 16 comments \ @k00b 5 May bitcoin
Something else is burning blockspace and bloating the UTXO set 🧵nitter.at/mononautical/status/1621663167582437376
2431 sats \ 9 comments \ @cryptocoin 4 Feb 2023 bitcoin
Sunday Survey: What's your ideal client for Bitcoin Core v30?
210 sats \ 5 comments \ @jimmysong 18 May bitcoin
[bitcoin-dev] Why Full-RBF Makes Multiparty Protocols DoS More Expensivelists.linuxfoundation.org/pipermail/bitcoin-dev/2023-January/021322.html
703 sats \ 3 comments \ @k00b 10 Jan 2023 bitcoin
Will small UTXOs become a problem in a mempool-collapsed future?
1898 sats \ 36 comments \ @pillar 30 Nov 2022 bitcoin
[bitcoin-dev] V3 Transactions are still vulnerable to significant tx and attackslists.linuxfoundation.org/pipermail/bitcoin-dev/2023-December/022211.html
4961 sats \ 0 comments \ @Rsync25 20 Dec 2023 bitcoin
Why Raising OP_RETURN Limits Helps Mitigate Spamsubstack.com/@scottmsul/p-163473475
1110 sats \ 6 comments \ @k00b 16 May bitcoin