This repository has been archived by the owner on Oct 9, 2019. It is now read-only.
forked from bitcoin/bitcoin
-
Notifications
You must be signed in to change notification settings - Fork 55
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
src/init.cpp: Add -advertise2x option, for NODE_xxx optionality
- Loading branch information
Showing
1 changed file
with
4 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit officially makes segwit2x a trojan horse as it allows anyone to run 2x nodes in disguise. Now core needs to find a new way to detect and ban your nodes.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What have you done with the old jgarzik and how much will it cost us to buy him back?
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jgarzik
This commit is a pure shame for 2X and for all 2x supporting companies.
Intentionally trying to disrupt the bitcoin network will have consequences and in a lot of states you will be held accountable by law for this attack.
I can only encourage every single B2X supporter to drop the support of B2X right now, before you will be part of a crime and have to face legal actions against you and everyone who is involved in this attack.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jgarzik this is tragic. bitcoin is about consensus not covert war tactics. this is open source software and masking clients to trick other open source software is just not OK by any community standards.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is anyone planning on reverting this commit back to the way it was so that all can go back and sleep in peace.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyone with an educated opinion knows this is 100% unethical and is aware that the excuse "we want to download the blockchain from high-bandwidth core clients before and after the fork" is not true at all.
If you needed to download the blockchain from core clients then that means that 2X has already failed due to a lack of adoption at that point, and disguising it won't change that. If there's adoption then you don't need this anyway.
This might cause things to get messy until the first >1MB block (non-witness data) gets mined as well. Up till now I thought the 2X fork was trying to be ethical and had good intentions in mind even with no replay protection, but this is the straw that broke the camel's back for me.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's how you can tell there is consensus for their hard-fork; Because they have to hide their nodes.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I didn't realize the hate on 2X until this commit. Thanks for spoiling it!
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Logerfo Thing is, this updates is to hide segwit2x support. it's just full on attack to BTC. Why hide your intentions if you're legit?
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@monxas I think I was not clear: I didn't realize the reason for the hate. You're right, now I do.
28ebbdb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a privacy feature. See discussion at PR #109 for more.
This feature defaults to advertise (privacy=off).
Users may optionally disable advertising (privacy=on).
There is historical precedent with Internet browsers: https://stackoverflow.com/questions/7975996/why-does-internet-explorer-9-report-mozilla-in-useragent
Users also rightly requested privacy features like this due to past attacks:
Bitcoin Core violated the Robustness Principle as described in RFC 1122 and elsewhere. https://tools.ietf.org/html/rfc1122