[crnkovic]

> if this was a non-issue they wouldn't be patching it

As far as I can tell, nobody is claiming it's a 'non-issue'. Rather, it's a minor issue with an impact that is greatly exaggerated or sensationalised by the person reporting it.

[pbear2k23]

>it's a minor issue with an impact that is greatly exaggerated or sensationalised by the person reporting it.

until, again, a botnet makes huge swaths of the bitcoin network unprofitable.

this is computer science - not how you feel about or faultily interpret an exploit.

[jameshilliard]

> until, again, a botnet makes huge swaths of the bitcoin network unprofitable.

You seem to be mixing up bitcoin nodes and bitcoin miners.

[pbear2k23]

you seem to be mixing up that mining pools expose tcp/8333 and if one pool's full node is attacked - many miners are caught in the crossfire unless in some type of special firewalled whitelist.

[jameshilliard]

> you seem to be mixing up that mining pools expose tcp/8333 and if one pool's full node is attacked - many miners are caught in the crossfire unless in some type of special firewalled whitelist.

Mining pools don't typically expose tcp/8333 in a way that makes it easy for them to be targeted and when they do they typically have redundant nodes and other mitigation measures in place to ensure reliability.

There have additionally been high speed optimized block relay networks used in the past by mining pools, although I don't think they are used anymore due to the public p2p network being much faster and more reliable than in the past due to various protocol improvements.

https://bitcoinrelaynetwork.org/

https://bitcoinfibre.org/