4 ms·

> Yes, it's been around for a while and contains various enhancements and patches that aren't in Core. See https://bitcoinxt.software/patches.html https://bitc

> Yes, it's been around for a while and contains various enhancements and patches that aren't in Core. See https://bitcoinxt.software/patches.html https://bitcoinxt.software/patches.html Only if by enhancements you mean damaging centralization bugs. TOR blacklisting by default for example

jnbiche 11y ago
I'm still not sure how I feel about that patch, but to be clear it does not blacklist Tor by default. What it does is that if a particular node detects a DOS attack that originates from the Tor network, each node with then down rate the Tor IPs (since that's where many of the DOSs originate from), giving non-Tor nodes higher precedence. And thus avoiding the DOS attach for non-Tor nodes. Under normal conditions, Tor nodes are fully integrated into the network. Like I said, I'm still ambivalent about this patch (for multiple reasons), but saying blacklisting Tor by default might give people the wrong impression of what it does. In the words of BitcoinXT site [1]: "This patch set introduces code that runs when a node is full and otherwise could not accept new connections. It labels and prioritises connections according to lists of IP ranges: if a high priority IP address connects and the node is full, it will disconnect a lower priority connection to make room. Currently Tor exits are labelled as being lower priority than regular IP addresses, as jamming attacks via Tor have been observed, and most users/merchants don't use it. In normal operation this new code will never run. If someone performs a DoS attack via Tor, then legitimate Tor users will get the existing behaviour of being unable to connect, but mobile and home users will still be able to use the network without disruption." I've looked at the patch, and that's pretty much what it does [2]. 1. https://bitcoinxt.software/patches.html https://bitcoinxt.software/patches.html 2. https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23 https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8...

jnbiche 11y ago

I'm still not sure how I feel about that patch, but to be clear it does not blacklist Tor by default. What it does is that if a particular node detects a DOS attack that originates from the Tor network, each node with then down rate the Tor IPs (since that's where many of the DOSs originate from), giving non-Tor nodes higher precedence. And thus avoiding the DOS attach for non-Tor nodes. Under normal conditions, Tor nodes are fully integrated into the network. Like I said, I'm still ambivalent about this patch (for multiple reasons), but saying blacklisting Tor by default might give people the wrong impression of what it does. In the words of BitcoinXT site [1]: "This patch set introduces code that runs when a node is full and otherwise could not accept new connections. It labels and prioritises connections according to lists of IP ranges: if a high priority IP address connects and the node is full, it will disconnect a lower priority connection to make room. Currently Tor exits are labelled as being lower priority than regular IP addresses, as jamming attacks via Tor have been observed, and most users/merchants don't use it. In normal operation this new code will never run. If someone performs a DoS attack via Tor, then legitimate Tor users will get the existing behaviour of being unable to connect, but mobile and home users will still be able to use the network without disruption." I've looked at the patch, and that's pretty much what it does [2]. 1. https://bitcoinxt.software/patches.html https://bitcoinxt.software/patches.html 2. https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8faea9c2b2c785a2f5b68aa4c23 https://github.com/bitcoinxt/bitcoinxt/commit/73c9efe74c5cc8...