search

btc1 / bitcoin

btc1 project bitcoin implementation
MIT License
329 stars 55 forks source link

Planning for a Mass DDOS Attack vs btc1 Nodes/DNS Seeds #129

Closed BTCgithub closed 6 years ago

BTCgithub commented 6 years ago

This is an excercise in adversarial thinking. I have left out likely 'adversaries' names in an attempt to keep the thread non-political.

The SegWit2X hardfork looks to be proceeding smoothly and on target for next month with 93-95% of the mining hashrate and industry/user support. The only possibility I see of disruption would be a btc1 Full Node/DNS Seed DDOS Attack while the fork is underway.

SegWit2X Adversaries provide no mining hashrate and have focused their thinking/efforts to making Full Node software incompatible and exploiting competitors Node vulnerabilities. They have a past history of attacking Bitcoin Unlimited Nodes and blasting them off of the network in an attempt to disrupt hardfork support for larger blocks.

Parties have convinced us to self-identify our btc1 nodes via the NODE_SEGWIT2X service flag.

If all self-identified btc1 nodes were DDOS'd would our chain continue processing transactions using other 0.14 Core Nodes & Bitcoin Unlimited/Classic Nodes? Ensuring a smooth Hard Fork at Block 494784 will be critical and I wanted to address the impact to the SegWit2x fork under this scenario.

Developer jheathco added a command-line arg to hide the segwit2x service bit. Assuming an imminent DDOS attack, should 'silent' be the btc1 Full Node default rather that requiring node operators to manually intervene in the middle of the hard fork if an attack commences?

Are all Core code-based Nodes somewhat vulnerable to similar DDOS attacks and if so, do we have enough btc1 nodes? Will our chain continue processing transactions if all btc1 Nodes are down?

btc1 DNS Seeds:

Are we using hardcoded seeds and does this make us more vulnerable to DDOS attacks? Are our btc1 DNS Seeds hosted with Highly Resistant DDOS Providers? Do we have enough DNS Seeds if we are DDOS attacked? (Should we have more?)

Developers chjj and christophebiocca discussed DNS seeds in the past and could speak better to the risks here than I. Reference Past Issue: https://github.com/btc1/bitcoin/issues/42

I have a feeling a Full Node/DNS Seed attack may be planned and wanted to revisit the above issues.

bitPico commented 6 years ago

NACK

Speculation and FUD is not development nor an issue.

BTCgithub commented 6 years ago

Nice to see all of the btc1 Nodes coming online. Almost at 1000 Nodes now. Thanks to whomever is doing the work!

https://coin.dance/nodes/btc1

BTCgithub commented 6 years ago

1335 btc1 Nodes ! https://coin.dance/nodes

BTCgithub commented 6 years ago

2000 nodes? Cool =)

https://coin.dance/nodes

jgarzik commented 6 years ago

Closing - not needed

NiKiZe commented 6 years ago

@jgarzik Are you joking? Let me get this straight ... We allowed for segwit to be activated, but we don't get a blocksize increase!? I really hope you and the rest have really good explanation! (And no https://lists.linuxfoundation.org/pipermail/bitcoin-segwit2x/2017-November/000685.html is just retarded!)