📅 Original date posted:2022-12-06
📝 Original message:On Tue, Dec 06, 2022 at 12:39:40AM -0500, Peter Todd via bitcoin-dev wrote:
> 10 or 20 nodes is completely meaningless. Pools run nodes themselves, which by
> default connect to 8 outgoing peers. There's about 5000 IPv4 listening nodes on
> the network. When a node learns of a new block, it tells all it's peers that
> the new block exists.
>
> For your censorship to work, there has to be a substantial propability that a
> miner *only* runs a single node (they don't), that has no incoming peers, and
> all 8 peers of that node happen to be one of your 20 censoring nodes.
> Obviously, since the probability of a given peer being a censoring node is
> 20/5000, all 8 being censored is extraordinarily unlikely.
>
> Even if you ran so many nodes that 20% of the entire network was censoring, the
> probability of all 8 outgoing peers being censors is only 0.2^8 = 0.000256%
>
>
> This is an example of information being hard to censor and easy to spread. In
> fact, for full-rbf this same math works in our favor: for a node to have a 50%
> chance of connecting to at least one full-rbf peer, just 8.3% of the network
> needs to run full-rbf. 5000 IPv4 nodes * 8% = 400 nodes.
>
> The percolation threshold doesn't need to be met for this to be succesful,
> because someone to just run a full-rbf node that connects to every single
> listening node simultaneously.
FYI here's a percolation simulator for full-rbf:
https://github.com/mzumsande/fullrbf_simulation
It finds similar results to my math above.
--
https://petertodd.org 'peter'[:-1]@petertodd.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221206/3f1d55d9/attachment.sig>;
Peter Todd [ARCHIVE] /
npub1m2…a2np2
2023-06-07 23:17:26
in reply to nevent1q…lgsz
Author Public Key
npub1m230cem2yh3mtdzkg32qhj73uytgkyg5ylxsu083n3tpjnajxx4qqa2np2Published at
2023-06-07 23:17:26Event JSON
{
"id": "14b8d3f2ad5101e24c59cfc3fe98c564ce66bb0a78f353b30c46cc88c90e12fb",
"pubkey": "daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa",
"created_at": 1686179846,
"kind": 1,
"tags": [
[
"e",
"fa32ea72e135d9ce7f2b7566efc472cd2a1427d59f8cfc5b2d532064311864b5",
"",
"root"
],
[
"e",
"93c76f67bcf16f6e1c34ba024372604d0e7c4fff23498689d872453d43daefd0",
"",
"reply"
],
[
"p",
"daa2fc676a25e3b5b45644540bcbd1e1168b111427cd0e3cf19c56194fb231aa"
]
],
"content": "📅 Original date posted:2022-12-06\n📝 Original message:On Tue, Dec 06, 2022 at 12:39:40AM -0500, Peter Todd via bitcoin-dev wrote:\n\u003e 10 or 20 nodes is completely meaningless. Pools run nodes themselves, which by\n\u003e default connect to 8 outgoing peers. There's about 5000 IPv4 listening nodes on\n\u003e the network. When a node learns of a new block, it tells all it's peers that\n\u003e the new block exists.\n\u003e \n\u003e For your censorship to work, there has to be a substantial propability that a\n\u003e miner *only* runs a single node (they don't), that has no incoming peers, and\n\u003e all 8 peers of that node happen to be one of your 20 censoring nodes.\n\u003e Obviously, since the probability of a given peer being a censoring node is\n\u003e 20/5000, all 8 being censored is extraordinarily unlikely.\n\u003e \n\u003e Even if you ran so many nodes that 20% of the entire network was censoring, the\n\u003e probability of all 8 outgoing peers being censors is only 0.2^8 = 0.000256%\n\u003e \n\u003e \n\u003e This is an example of information being hard to censor and easy to spread. In\n\u003e fact, for full-rbf this same math works in our favor: for a node to have a 50%\n\u003e chance of connecting to at least one full-rbf peer, just 8.3% of the network\n\u003e needs to run full-rbf. 5000 IPv4 nodes * 8% = 400 nodes.\n\u003e \n\u003e The percolation threshold doesn't need to be met for this to be succesful,\n\u003e because someone to just run a full-rbf node that connects to every single\n\u003e listening node simultaneously.\n\nFYI here's a percolation simulator for full-rbf:\n\nhttps://github.com/mzumsande/fullrbf_simulation\n\nIt finds similar results to my math above.\n\n-- \nhttps://petertodd.org 'peter'[:-1]@petertodd.org\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 833 bytes\nDesc: not available\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20221206/3f1d55d9/attachment.sig\u003e",
"sig": "ee5c946406ff0bd382ae7058b4d1d8586b1904690e24a3d0451d8726f609bdde0367bbd88368426cd1be9259a04de3ab667548241732c835e23e73fd52fe9eaa"
}