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 ) id 1Wz1Ip-0008CM-UI for bitcoin-development@lists.sourceforge.net; Mon, 23 Jun 2014 10:16:43 +0000 Received: from mail-lb0-f177.google.com ([209.85.217.177]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wz1Io-0000Bh-4I for bitcoin-development@lists.sourceforge.net; Mon, 23 Jun 2014 10:16:43 +0000 Received: by mail-lb0-f177.google.com with SMTP id u10so4190074lbd.36 for ; Mon, 23 Jun 2014 03:16:35 -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:date:message-id:subject:from:to :content-type:content-transfer-encoding; bh=2ssyTCQA360tLsJANLFuG7pmFlJ9oWwMKWRtJiZkDU4=; b=OoFp58qR90JdGj7xB+8qdkBYK4M4T/ruqr1TfiviEofKNVnmnxEolbGBBHxzH6R4HK z36BCh6i6VSRv0zsoKmFQMOuzCRW8mJoPdS8QnX/Pjs1+i9vsFN8GEaQOcO9g9v5aaoX 6WqDI/jhIWeYpvkrmWtCfwNc7xnfH2guqe3BoPjaR1d4XBvQm6s8vStk2bH+J7hEupbQ 29kSY8ZElQrP/PQd9bHDJn5BAoYoMNRMqWhBFNotJ6uOJMyEchEOsLO9ZOfm7txez0bc fZMIuJGIDzrJzNJ8ecMAw4N9cBsH6uGH/rlOVANUvVt6hztvysdPtyYC5118ckDS/EVr hyAA== X-Gm-Message-State: ALoCoQk7bkoI6yijFocf4EdBhVBE0anciBoUCf2FZfc2N2X+o6xzal2P3dzTKJ3Z1u1FXevbJjeq MIME-Version: 1.0 X-Received: by 10.152.45.37 with SMTP id j5mr1267337lam.58.1403517000784; Mon, 23 Jun 2014 02:50:00 -0700 (PDT) Received: by 10.112.185.4 with HTTP; Mon, 23 Jun 2014 02:50:00 -0700 (PDT) X-Originating-IP: [85.59.140.152] Date: Mon, 23 Jun 2014 11:50:00 +0200 Message-ID: From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= To: Bitcoin Development Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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: 1Wz1Io-0000Bh-4I Subject: [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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 10:16:44 -0000 I know there are plans to separate the wallet from the core code and I think it's a great idea that will result in cleaner and more modular software. But it seems like my assumptions on how this would be done may be incorrect= . I was assuming that the wallet would consume data from a trusted bitcoind core node using rpc or a better interface like an http rest api (see PR #2844). So the core would take care of the hard consensus stuff, and the wallet would maintain its own database with private keys, addresses, balances, etc. and would consume some data contained in bitcoind's database. I also assumed that the interface between wallet and core would include queries to the UTXO (see PR #4351) and maybe TXO (see PR #3652) for getting the historic balances. As said, I'm not sure these assumptions are true anymore so I ask. Is this the plan? Is the plan that the wallet will use the p2p directly and maintain its own chain database? Well, it's something that generally interests me so if anyone can detail the steps for separating the wallet a little bit, maybe I can help with some of the steps. Maybe there's no roadway yet. In that case I would like to advance that discussion in this thread. --=20 Jorge Tim=C3=B3n