From: praxeology_guy <praxeology_guy@protonmail•com>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Bandwidth limits and LN w/ node relay network topography
Date: Sun, 26 Mar 2017 18:11:14 -0400 [thread overview]
Message-ID: <OlmJBOCNdLgek6x1SvZhs_z04xtkZ1i1zRoJMoeda0WZhMZyRl459BVklFY4xxBmwaP0pLJbBtbUO8i-3bprB8ZuoeoHwUqoHR8rdPYRd9g=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 1581 bytes --]
next reply other threads:[~2017-03-26 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-26 22:11 praxeology_guy [this message]
2017-03-27 17:09 ` Aymeric Vitte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='OlmJBOCNdLgek6x1SvZhs_z04xtkZ1i1zRoJMoeda0WZhMZyRl459BVklFY4xxBmwaP0pLJbBtbUO8i-3bprB8ZuoeoHwUqoHR8rdPYRd9g=@protonmail.com' \
--to=praxeology_guy@protonmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox