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 bitcoin
related
Dissection of a force-close that already cost me 140k sats
10.1k 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 bitdevs
Why happen force closures on LN channels?
14.7k sats \ 18 comments \ @DarthCoin 23 Aug 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
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
[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
I2P is experiencing a Denial-of-Service attackteddit.net/r/i2p/comments/10v9uxp
855 sats \ 8 comments \ @cryptocoin 7 Feb 2023 bitcoin
The testnet mempool is full.
2032 sats \ 19 comments \ @lloyddunne 14 Apr Ordinals_Inscriptions_Runes
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
DoS Disclosure: LND Onion Bombdelvingbitcoin.org/t/dos-disclosure-lnd-onion-bomb/979
1878 sats \ 3 comments \ @Rsync25 18 Jun lightning freebie
[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
[bitcoin-dev] Solving CoinPool high-interactivitylists.linuxfoundation.org/pipermail/bitcoin-dev/2023-September/021969.html
2829 sats \ 0 comments \ @Rsync25 26 Sep 2023 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
remote bitcoin core killer?? OOM from bad peer conn msgsx.com/123456/status/1741922597908959701
2630 sats \ 7 comments \ @niftynei 6 Jan bitdevs
Force Closes with large timeout recovery tx fee
2578 sats \ 5 comments \ @ZezzebbulTheMysterious 18 Oct lightning
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 bitcoin
Windows TCP/IP Remote Code Execution Vulnerability - IPV6 strikes backmsrc.microsoft.com/update-guide/vulnerability/CVE-2024-38063
387 sats \ 2 comments \ @aljaz 14 Aug security
Will small UTXOs become a problem in a mempool-collapsed future?
1898 sats \ 36 comments \ @pillar 30 Nov 2022 bitcoin
In 2023, Bitcoiners Must Stop Shooting (Or Blocking) The Messengersbitcoinmagazine.com/culture/dont-shoot-the-bitcoin-messengers?utm_source=carrot&utm_medium=partner&utm_campaign=carrot_share
229 sats \ 2 comments \ @BitcoinIsTheFuture 23 Jan 2023 bitcoin
Disclosure of memory DoS due to headers spam - Bitcoin Corebitcoincore.org/en/2024/09/18/disclose-headers-oom/
1010 sats \ 0 comments \ @Rsync25 19 Sep bitcoin
Murch Overflows: history of mysterious 1-of-1 multisig txsbitcoin.stackexchange.com/questions/115443/1-of-1-multisig
127 sats \ 1 comment \ @k00b 3 Oct 2022 bitcoin