From: Tier Nolan <tier.nolan@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Torrent-style new-block propagation on Merkle trees
Date: Thu, 24 Sep 2015 09:52:34 +0100 [thread overview]
Message-ID: <CAE-z3OV-1wziASBZ3moE9D2=bVVh7-RBwjMJAV=3LcanCzbN1w@mail.gmail.com> (raw)
In-Reply-To: <36CE1B0F-3BE5-4DC3-8488-A57667256059@toom.im>
[-- Attachment #1: Type: text/plain, Size: 2611 bytes --]
On Thu, Sep 24, 2015 at 12:12 AM, Jonathan Toomim (Toomim Bros) via
bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
>
> As I understand it, the current block propagation algorithm is this:
>
> 1. A node mines a block.
> 2. It notifies its peers that it has a new block with an *inv*. Typical
> nodes have 8 peers.
> 3. The peers respond that they have not seen it, and request the block
> with *getdata* [hash].
> 4. The node sends out the block in parallel to all 8 peers simultaneously.
> If the node's upstream bandwidth is limiting, then all peers will receive
> most of the block before any peer receives all of the block. The block is
> sent out as the small header followed by a list of transactions.
> 5. Once a peer completes the download, it verifies the block, then enters
> step 2.
>
Mining pools currently connect to the "fast relay network". This is
optimised for fast block distribution. It does no validation and is only
for low latency propagation. The normal network is used as a fallback.
My understanding is that it works as follows:
Each miner runs a normal full node and a relay node on the same computer.
The full node tells the relay node whenever it receives a new transaction
via the inv message and the node requests the full transaction.
The relay node tells its relay peers that it knows about the transaction
(hash only) and its 4 byte key. This is not forwarded onwards, since the
relay peer only gets the hash of the transaction and doesn't do validation
anyway. The key is just a 4 byte counter.
Each relay node keeps a mapping of txid to key for each of its peer. There
is some garbage collection and entries are removed once the transaction is
included in a block (there might be a confirm threshold).
When a block is found, the local node sends it to the relay node. The
relay node then forwards it to all of its peers in a compact form.
The block is sent as a list of keys for that peer and full transactions are
only sent for unknown transactions.
When a relay node receives a block, it just verifies the POW, checks that
it is new and recent. It does not do tx validation. It forwards the block
to its local full node, which does the validation. Since the relay node is
on localhost, it never gets kicked due to sending invalid blocks. This
prevents a DOS attack where you could send invalid blocks to the relay node
and cause the local full node to kick it.
If all the transactions are already known, then it can forward a block for
only 4 bytes per transactions. I think it has an optimisation, so that is
compressed to 1 byte per tx.
[-- Attachment #2: Type: text/html, Size: 3278 bytes --]
prev parent reply other threads:[~2015-09-24 8:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 23:12 Jonathan Toomim
2015-09-24 0:31 ` Angel Leon
2015-09-24 8:52 ` Tier Nolan [this message]
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='CAE-z3OV-1wziASBZ3moE9D2=bVVh7-RBwjMJAV=3LcanCzbN1w@mail.gmail.com' \
--to=tier.nolan@gmail$(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