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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <mh.in.england@gmail.com>) id 1YwzgH-0003BE-F3
for bitcoin-development@lists.sourceforge.net;
Mon, 25 May 2015 21:13:05 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.178 as permitted sender)
client-ip=209.85.212.178; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f178.google.com;
Received: from mail-wi0-f178.google.com ([209.85.212.178])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YwzgG-0000Il-Cm
for bitcoin-development@lists.sourceforge.net;
Mon, 25 May 2015 21:13:05 +0000
Received: by wichy4 with SMTP id hy4so59750339wic.1
for <bitcoin-development@lists.sourceforge.net>;
Mon, 25 May 2015 14:12:58 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.61.82 with SMTP id n18mr1495163wjr.35.1432588378366;
Mon, 25 May 2015 14:12:58 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.143.9 with HTTP; Mon, 25 May 2015 14:12:58 -0700 (PDT)
In-Reply-To: <1515563.NQHYuaqTfB@crushinator>
References: <CANe1mWzBy8-C+CWfwaOLxJ2wokjy8ytQUh2TkRY_Ummn1BpPzw@mail.gmail.com>
<2114827.D6GUhXtGkV@crushinator>
<CANEZrP2KnL9NO-DgUuaT5-VHE0oT5MTsok2YuAO1nJiznLfpMA@mail.gmail.com>
<1515563.NQHYuaqTfB@crushinator>
Date: Mon, 25 May 2015 23:12:58 +0200
X-Google-Sender-Auth: AIuDTeNHDa1gMJwPdICgo4JwJUQ
Message-ID: <CANEZrP2FjxmMn3TKPGdP-mTMDt4a4aJB5AisEp+NdW6qCAAEEw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Whitlock <bip@mattwhitlock.name>
Content-Type: multipart/alternative; boundary=047d7ba9778066e8af0516ee7914
X-Spam-Score: -0.5 (/)
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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(mh.in.england[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
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: 1YwzgG-0000Il-Cm
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A suggestion for reducing the size of the
UTXO database
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: Mon, 25 May 2015 21:13:05 -0000
--047d7ba9778066e8af0516ee7914
Content-Type: text/plain; charset=UTF-8
>
> If it matters, I configure the app to connect only to my own trusted
> Bitcoin node, so I only ever have one active connection at most.
Ah, I see, non default configuration. Because the Bitcoin network can and
does change in backwards incompatible ways, the app wants to see that the
transaction it made actually propagated across the network. If you set a
trusted node it won't see that.
Probably the logic should be tweaked so if you set a trusted node you're
just assumed to know what you're doing and we assume the transactions we
make ourselves always work.
--047d7ba9778066e8af0516ee7914
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">If it matters, I configure the app to connect on=
ly to my own trusted Bitcoin node, so I only ever have one active connectio=
n at most.</blockquote><div><br></div><div>Ah, I see, non default configura=
tion. Because the Bitcoin network can and does change in backwards incompat=
ible ways, the app wants to see that the transaction it made actually propa=
gated across the network. If you set a trusted node it won't see that.<=
/div><div><br></div><div>Probably the logic should be tweaked so if you set=
a trusted node you're just assumed to know what you're doing and w=
e assume the transactions we make ourselves always work.=C2=A0</div></div><=
/div></div>
--047d7ba9778066e8af0516ee7914--
|
