📅 Original date posted:2014-05-19
📝 Original message:On 19/05/14 14:15, Mike Hearn wrote:
> As an interested party not intimately familiar with the bitcoin codebase
> who also spent some time setting up a node a while ago, I would like to
> add one thing to the above list - network rate limiting.
>
>
> The problem is that this is easier said than done. Bitcoin Core won't
> notice a remote peer is working but slow and switch to a faster one, and
> even if it did, it'd just mean throttling your connection would cause
> all remote nodes to give up and hit the other unthrottled peers even more.
>
Does this mean that you can currently actively hurt the network by
adding a node with a very slow upstream / downstream? If so, what is the
recommended minimum amount of bandwidth you should allocate for a node?
I've already throttled mine with QoS based on the script in the contrib/
folder.
Bjørn Øivind
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 901 bytes
Desc: OpenPGP digital signature
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140519/9ea04427/attachment.sig>;
Bjørn Øivind Bjørnsen [ARCHIVE] /
npub1nt…7vpyf
2023-06-07 15:21:45
in reply to nevent1q…hjsv
Author Public Key
npub1ntcsdfwvtt0v3h4gwpkr44kzrnjllnx24m6wx3ga826mc66stfmqu7vpyfSeen on
wss://relay.nostr.bandPublished at
2023-06-07 15:21:45Event JSON
{
"id": "297058c3ce74bddab25be120e2ce2c9bb15e93c959879f5c1ce785c7d4bb18c6",
"pubkey": "9af106a5cc5adec8dea8706c3ad6c21ce5ffcccaaef4e3451d3ab5bc6b505a76",
"created_at": 1686151305,
"kind": 1,
"tags": [
[
"e",
"d13d5f5ef63c165861ecb6f28bbd05784e8dd9d95e01dbc1a067d919b20bb61d",
"",
"root"
],
[
"e",
"3dc759ddc41f69e6d959465c7d36bbbe205aef942f7d55a94188888ae2bd73a3",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2014-05-19\n📝 Original message:On 19/05/14 14:15, Mike Hearn wrote:\n\u003e As an interested party not intimately familiar with the bitcoin codebase\n\u003e who also spent some time setting up a node a while ago, I would like to\n\u003e add one thing to the above list - network rate limiting.\n\u003e \n\u003e \n\u003e The problem is that this is easier said than done. Bitcoin Core won't\n\u003e notice a remote peer is working but slow and switch to a faster one, and\n\u003e even if it did, it'd just mean throttling your connection would cause\n\u003e all remote nodes to give up and hit the other unthrottled peers even more.\n\u003e \n\nDoes this mean that you can currently actively hurt the network by\nadding a node with a very slow upstream / downstream? If so, what is the\nrecommended minimum amount of bandwidth you should allocate for a node?\nI've already throttled mine with QoS based on the script in the contrib/\nfolder.\n\nBjørn Øivind\n\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 901 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140519/9ea04427/attachment.sig\u003e",
"sig": "73784b1f0653f3a2b97d3676663188eb493bb4500fea84479caa245e23762405aca87e3bee91a4d8c27d15fb655c8f9427d168d3c32473ec51256072213c4c62"
}