1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1X88bt-0001Rg-H8
for bitcoin-development@lists.sourceforge.net;
Fri, 18 Jul 2014 13:54:05 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.179 as permitted sender)
client-ip=74.125.82.179; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f179.google.com;
Received: from mail-we0-f179.google.com ([74.125.82.179])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1X88bs-0006Zy-Aw
for bitcoin-development@lists.sourceforge.net;
Fri, 18 Jul 2014 13:54:05 +0000
Received: by mail-we0-f179.google.com with SMTP id u57so4552853wes.38
for <bitcoin-development@lists.sourceforge.net>;
Fri, 18 Jul 2014 06:53:56 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=OheIrj5Lwsmxr/pXshnYUAsHZtDP5j7rVCs3D6H1CLE=;
b=aOuJeytJmKIqgMj+vw3HIHYcgZD2osmQxAzgQoJCz+REjYiVBjdkgpZHod9JQKy+no
LQOzQsCiTkyWO2OyvCNIh/Dmf8cd59N9rKvYSoc7mouRW1ch+s+fHwYGZGj+HoIrfUUh
GmY+gUncw4D2bG3wTMvuj4Z5Sq+YMdPVDhX1RCtAw54WzVSSRFJ7iJ9yr4cZUjO3wMyX
R3tDFhlUU3mwd326dTJaBsvCYVsSueokx/oZOXCaeXqCnZR5XQd296G/pLecDC2/50Pi
BSvDqhypBGCP15OMc2gw8HYcFbRYjo/3VKcIPti9/1HpHBzDOGgEH2tc21uRwJ7Ayc2c
0z7Q==
X-Gm-Message-State: ALoCoQl657HG1y+bxlx0Xaoxq/Wf3eHCZuASj3vvMbTg3BBEODMR+9+H1QVpmqE+p7vrFKcpY1nS
X-Received: by 10.180.24.97 with SMTP id t1mr32868753wif.45.1405691635961;
Fri, 18 Jul 2014 06:53:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.5.67 with HTTP; Fri, 18 Jul 2014 06:53:35 -0700 (PDT)
In-Reply-To: <CABsx9T0ag_o_mu=5Q7Ju7s2hO3jz-o5g9FihE9h4B6+ednd2Pg@mail.gmail.com>
References: <CA+iPb=EaX=bvOjNtZ+LnYTMRLQQ9nFcrefAkBdv8eActoX_b8A@mail.gmail.com>
<CABsx9T0ag_o_mu=5Q7Ju7s2hO3jz-o5g9FihE9h4B6+ednd2Pg@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Fri, 18 Jul 2014 09:53:35 -0400
Message-ID: <CAJHLa0NZRF+1QjSwtwjaTE07NWJ_U-O-DE24=P5eSAutMqTupg@mail.gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1X88bs-0006Zy-Aw
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Squashing redundant tx data in blocks on
the wire
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 18 Jul 2014 13:54:05 -0000
On Thu, Jul 17, 2014 at 6:46 PM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> I'd encourage you to code up a prototype first (or at the same time), in
> whatever programming language / networking library you're most familiar
> with.
+1
> Maybe not even using the existing p2p protocol; there could be a mining-only
> very-fast-block-propagation network separate from the existing p2p network.
>
> Combining your optimizations with "broadcast as many near-miss blocks as
> bandwidth will allow" on a mining backbone network should allow insanely
> fast propagation of most newly solved blocks.
Yes, I would encourage thinking along these lines. That was the
motivation of the UDP P2P protocol extension I wrote:
https://bitcointalk.org/index.php?topic=156769.0
The intention was to experiment with sending block header + tx list +
coinbase, via UDP best effort broadcast.
Incentives:
If your neighbors receiving this message already have the TXs in the
TX list, then the block is complete, and may be relayed further.
If your neighbors do not have all TXs in the block, they must fetch
them at additional time/latency cost.
Thus, you have an incentive to relay blocks containing TXs already
distributed out into network mempools and cached in the signature
cache.
We want to capture that incentive in whatever protocol is eventually
used. Miners have a TX fee incentive to include many transactions.
In theory, they want to include as many TX as possible. It will help
us scale quite a bit to solve this problem.
|
