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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jtimon@monetize.io>) id 1WzAeF-0003gk-Mf
for bitcoin-development@lists.sourceforge.net;
Mon, 23 Jun 2014 20:15:27 +0000
Received: from mail-lb0-f178.google.com ([209.85.217.178])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WzAeD-0006pd-T6
for bitcoin-development@lists.sourceforge.net;
Mon, 23 Jun 2014 20:15:27 +0000
Received: by mail-lb0-f178.google.com with SMTP id 10so5338765lbg.9
for <bitcoin-development@lists.sourceforge.net>;
Mon, 23 Jun 2014 13:15:19 -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:date
:message-id:subject:from:to:cc:content-type;
bh=yvesGUDDFf9Qtr5mDfdftRMrS+GgOIBgIu8sZGD5GuY=;
b=ddSGwlwHHqgVjkwFVqv2b+OWbLT0oTQKFz7cJNX/I/HH1sSXaPHjdQdTYAPaFGrhim
wIvl2MuOHbzuqmT6z59WgCnueJtYKVPfKpA6w3EX6drt7/eKi5//JyeuvR8tCc7sjfgA
Zg7Z2vy3j827FaOqlfCXpCq0eByhbe9AbquvXI/FxDYomd0mjkeOzZDDQSsq87Fa6bKD
mNFNTxpcqLQbjq/MYuAwEIeDr3MfCIQfmWqyRE7qcBRbnOvcN6H2fpKQa/QhNDcnyj2k
wDHV6+8YaJZq+t0tBCrrQbcgBpGPE6kcsIn6Nr20LDCtIWYCHeglvOpYu+4jt/e+Pfve
5AHQ==
X-Gm-Message-State: ALoCoQmNG5T3L/lGhqHkQMxy+euqxkZTdetWmCxvuT1g4vYnVpyfYHNoUv6SUEhF24GVLY/S5ZnC
MIME-Version: 1.0
X-Received: by 10.112.157.130 with SMTP id wm2mr18019747lbb.38.1403554519128;
Mon, 23 Jun 2014 13:15:19 -0700 (PDT)
Received: by 10.112.185.4 with HTTP; Mon, 23 Jun 2014 13:15:19 -0700 (PDT)
X-Originating-IP: [85.53.220.49]
In-Reply-To: <CA+s+GJDVBQVu8yH9jLu_rQmk=dsJuMUctT-iK0zzOJRYgE8k9w@mail.gmail.com>
References: <CAC1+kJNjcPkaHiR8mzofwXE4+4UX5nmxX5Q3rZv37v-K40p1Tw@mail.gmail.com>
<CA+s+GJDVBQVu8yH9jLu_rQmk=dsJuMUctT-iK0zzOJRYgE8k9w@mail.gmail.com>
Date: Mon, 23 Jun 2014 22:15:19 +0200
Message-ID: <CAC1+kJOQ2uBo2peYKZJyPSQL6qzk6Yu-cF-tPs3GzVS6cAc53w@mail.gmail.com>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@monetize.io>
To: Wladimir <laanwj@gmail.com>
Content-Type: text/plain; charset=UTF-8
X-Spam-Score: 0.0 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
X-Headers-End: 1WzAeD-0006pd-T6
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Plans to separate wallet from core
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, 23 Jun 2014 20:15:27 -0000
On 6/23/14, Wladimir <laanwj@gmail.com> wrote:
> It's least surprising if the wallet works as a SPV client by default.
> Then, users can use it without first setting up a core. Thus the idea
> would be to use P2P primarily.
So first bitcoind will support SPV mode then we separate the wallet?
Are the core and the wallet share any code (say, the p2p messages via
a sub-repo or something)?
> There could be a mode to use a trusted core by RPC for
> mempool/conflicted transaction validation and such. But I'm not sure
> about this - as we've seen, pure-SPV wallets work pretty well. If you
> want it to act as an edge router you can point a SPV wallet at your
> trusted core as well.
I thought we would first separate wallet from core (maintaining the
full-node wallet status) and then implement an optional SPV mode for
the core (and transitively for "qt-wallet", which would support both
full and SPV mode).
> There are no plans for adding Electrum-like functionality to bitcoind.
> There is already Electrum. Let's not reinvent any wheels.
I'm sorry, but I still don't know what Electrum has to do with all this.
Bitcoin companies often like to interface with the network via
bitcoind nodes, what's wrong with their custom wallets consuming some
optional indexes from a bitcoind node their run themselves?
I'm not proposing a "bitcoind-client" similar to a electrum-client. I
thought it was assumed you where still going to run both the core and
the wallet and we just wanted to separate the code for better
modularity. Seriously, Mike also said something about Electrum too and
I'm really lost about what you people mean here.
> It does not need to keep a full chain database. But it needs its own
> record of the chain, headers-only + what concerns the keys in the
> wallet.
Why cannot consume that data from a bitcoind node that always run alongside it?
I still don't get the plan but it feels like it won't look as DRY as I
was expecting...
|
