{"type":"rich","version":"1.0","author_name":"npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","author_url":"https://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgyd","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-07-18\n📝 Original message:\u003e SPV clients behaving normally are highly abusive: they use up maximum\n\u003e node resources with minimum cost to themselves.\n\u003e\n\nThis must be a new use of the word \"abuse\" I haven't come across before :)\n\nAt any rate, some of these assumptions are incorrect. Botnets of\ncompromised web servers are quite common, and asymmetry in node resources\nis obviously biased against the kinds of devices people increasingly have\n(phones, tablets) where extremely limited memory bandwidth is common and\napps routinely have just 16 or 32mb of memory to do everything including\nthe GUI.\n\nA good anti-DoS strategy looks much the same as a good load shedding\nstrategy. There's little reason to treat them separately. Perhaps instead\nof talking about DoS we should instead talk about what happens if Bitcoin\nsuddenly gets too popular. Now there are suddenly lots of good users all\nwanting to use the network, and not enough nodes to support them all. What\ndo we do?\n\nSome rules seem obvious - try to prioritise existing users over new users,\nold coins over new coins (dPriority already does this) etc. If you run out\nof TCP sockets prefer to disconnect recent connections (probably new users)\nto long lived connections (probably high powered backbone peers). If you\nrun out of disk seeks prefer processing new blocks to serving old parts of\nthe chain, etc.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20130718/4c80ef0f/attachment.html\u003e"}