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
111
112
113
114
115
116
117
118
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <laanwj@gmail.com>) id 1WXzDM-00057g-92
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 20:35:20 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.223.174 as permitted sender)
client-ip=209.85.223.174; envelope-from=laanwj@gmail.com;
helo=mail-ie0-f174.google.com;
Received: from mail-ie0-f174.google.com ([209.85.223.174])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WXzDL-0005FQ-9i
for bitcoin-development@lists.sourceforge.net;
Wed, 09 Apr 2014 20:35:20 +0000
Received: by mail-ie0-f174.google.com with SMTP id rp18so3007227iec.19
for <bitcoin-development@lists.sourceforge.net>;
Wed, 09 Apr 2014 13:35:14 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.50.79.161 with SMTP id k1mr12497677igx.31.1397075713992;
Wed, 09 Apr 2014 13:35:13 -0700 (PDT)
Received: by 10.64.70.131 with HTTP; Wed, 9 Apr 2014 13:35:13 -0700 (PDT)
In-Reply-To: <CAJna-Hj1U5cQ22bSXoNB-4ck_urCuS9xCk+iEHsbh+yv17MP7A@mail.gmail.com>
References: <CA+s+GJCn9U2kmyMH6w3o+m99NCfO0ws=SccvGBYJv07WVuF=eA@mail.gmail.com>
<CAADm4BCEFCiOpNzUThPPHUamP2256izU8pwD3nerLCxks0wENA@mail.gmail.com>
<CAAS2fgTx40XSLhiygnJMrSbOC=iJ2YMVLNK7-AMt3ifvAHDZUA@mail.gmail.com>
<E9BAD633-3B6A-4A2C-AA06-DB591973DF66@bitsofproof.com>
<53456B99.9010207@monetize.io>
<B2FEC170-7214-4E46-8830-153995870B62@bitsofproof.com>
<00b77560-d7ed-4ed4-a4e5-eb1f00467a06@email.android.com>
<0509477C-89F9-47C7-8820-29ACAD4A4A8E@bitsofproof.com>
<CANEZrP2Q=TG+jejEVFFh5FhjzDDkySHNSTfwtKueLcHu=pB6Kw@mail.gmail.com>
<CA+s+GJBRvDFgktTgW2sCvAVahrjxcGqfgHw0BVNPvwUupotVrg@mail.gmail.com>
<534592E2.7040800@gmail.com>
<CAAS2fgS3q6N9go-NSKdjLwgU_5bFwa8YE88DcjNYHQTwzPCn3Q@mail.gmail.com>
<5345986C.3040901@gmail.com>
<CAAS2fgQyXHNnBDKoUMd_=-=1irGJ6cFKwi59enLJvFJiWBv50A@mail.gmail.com>
<CAJna-Hj1U5cQ22bSXoNB-4ck_urCuS9xCk+iEHsbh+yv17MP7A@mail.gmail.com>
Date: Wed, 9 Apr 2014 22:35:13 +0200
Message-ID: <CA+s+GJA0EqvZB3Bi75W+-Pfkjg=3=-wafjSBPMCnd_vbi2F-0w@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: slush <slush@centrum.cz>
Content-Type: multipart/alternative; boundary=089e01183c36a8819504f6a209a1
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(laanwj[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1WXzDL-0005FQ-9i
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoind-in-background mode for SPV
wallets
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: Wed, 09 Apr 2014 20:35:20 -0000
--089e01183c36a8819504f6a209a1
Content-Type: text/plain; charset=UTF-8
On Wed, Apr 9, 2014 at 10:12 PM, slush <slush@centrum.cz> wrote:
> Maybe there're other ideas how to improve current situation without needs
> of reworking the architecture.
>
Nothing I've proposed here would require larger changes to the architecture
then were already planned. After SPV lands we are going to split off the
wallet, and that will need an interface to an bitcoind to allow 'running
with full node'. If that can be generalized to be useful for other (SPV)
clients as well, that would be useful, hence I asked for input.
It of course doesn't preclude also looking for other solutions.
Wladimir
--089e01183c36a8819504f6a209a1
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, Apr 9, 2014 at 10:12 PM, slush <span dir=3D"ltr"><<a href=3D=
"mailto:slush@centrum.cz" target=3D"_blank">slush@centrum.cz</a>></span>=
wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div dir=3D"ltr">Maybe there're other id=
eas how to improve current situation without needs of reworking the archite=
cture.</div>
</blockquote><div><br></div><div>Nothing I've proposed here would requi=
re larger changes to the architecture then were already planned. After SPV =
lands we are going to split off the wallet, and that will need an interface=
to an bitcoind to allow 'running with full node'. If that can be g=
eneralized to be useful for other (SPV) clients as well, that would be usef=
ul, hence I asked for input. <br>
<br></div><div>It of course doesn't preclude also looking for other sol=
utions.<br></div><div><br></div><div>Wladimir<br><br></div></div></div></di=
v>
--089e01183c36a8819504f6a209a1--
|
