praxeology_guy [ARCHIVE] on Nostr: đ
Original date posted:2017-03-26 đ Original message:Bandwidth limits: Would be ...
đ
Original date posted:2017-03-26
đ Original message:Bandwidth limits:
Would be nice to specify global and per node up/down bandwidth limits.
Communicate limits to peers.
Monitor actual bandwidth with peers.
Adjust connections accordingly to attain bandwidth goals/limits.
With Lightning Network:
Prepay for bandwidth/data. Continue paying nodes who continue to send new useful data. Potentially pay different amounts for different kinds of data.
Request refunds when a node sends useless/duplicate/invalid/spam data. Discontinue connection w/ nodes that don't refund. Hence LN payment channel network topography becomes somewhat correlated w/ bitcoin node relay network topography.
Should help nodes get better data faster, improve spam/DDoS resiliance. Incentivizes relay of unconfirmed txs and new blocks, when currently there is only a utilitarian marginal self benefit via helping everyone in general.
Maybe relay advertisements of available bandwidth and prices, etc.
To identify network splits:
Nodes could find hash of "nonce + pub key + tip blockhash" beating a difficulty threshold. Sign, broadcast. Prove their existence and connectedness. History can be maintained and monitored for disruption. Could be made part of the messages that advertise available network bandwidth.
Cheers,
Praxeology Guy
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170326/20cc7d35/attachment.html>
Published at
2023-06-07 17:57:55Event JSON
{
"id": "d03a4939f682849b9c0e61f6a43b6c0f26eee384b0e01d7a9ce1d7f3d8d6ecfb",
"pubkey": "b8acca17a6f74c77cd8a4899846d99012d1b52082a01a2d2753fcb0c6669a60b",
"created_at": 1686160675,
"kind": 1,
"tags": [
[
"e",
"65ca063a54e18cb8dff03a2b9158bd834752ef7d46fc5cbdcbf7364793c1e315",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "đ
Original date posted:2017-03-26\nđ Original message:Bandwidth limits:\nWould be nice to specify global and per node up/down bandwidth limits.\nCommunicate limits to peers.\nMonitor actual bandwidth with peers.\nAdjust connections accordingly to attain bandwidth goals/limits.\n\nWith Lightning Network:\nPrepay for bandwidth/data. Continue paying nodes who continue to send new useful data. Potentially pay different amounts for different kinds of data.\nRequest refunds when a node sends useless/duplicate/invalid/spam data. Discontinue connection w/ nodes that don't refund. Hence LN payment channel network topography becomes somewhat correlated w/ bitcoin node relay network topography.\n\nShould help nodes get better data faster, improve spam/DDoS resiliance. Incentivizes relay of unconfirmed txs and new blocks, when currently there is only a utilitarian marginal self benefit via helping everyone in general.\n\nMaybe relay advertisements of available bandwidth and prices, etc.\n\nTo identify network splits:\nNodes could find hash of \"nonce + pub key + tip blockhash\" beating a difficulty threshold. Sign, broadcast. Prove their existence and connectedness. History can be maintained and monitored for disruption. Could be made part of the messages that advertise available network bandwidth.\n\nCheers,\nPraxeology Guy\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20170326/20cc7d35/attachment.html\u003e",
"sig": "769d56db8441721f3641e2f968ff810568dcd0e157b17010f76d382cbed0ec4d3c17bfb24e819cae06d8dfc2a310a9ceb9491778b4782249b21885a512a0f94c"
}