Wladimir [ARCHIVE] on Nostr: 📅 Original date posted:2014-06-23 📝 Original message:On Mon, Jun 23, 2014 at ...
📅 Original date posted:2014-06-23
📝 Original message:On Mon, Jun 23, 2014 at 11:50 AM, Jorge Timón <jtimon at monetize.io> wrote:
> 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).
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.
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.
There are no plans for adding Electrum-like functionality to bitcoind.
There is already Electrum. Let's not reinvent any wheels.
> 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.
Right, the wallet would keep track of those.
> 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?
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.
Wladimir
Published at
2023-06-07 15:23:11Event JSON
{
"id": "842977e918475506198d236bf992d775f225dd41cd0dc571025331ec41a5f230",
"pubkey": "30217b018a47b99ed4c20399b44b02f70ec4f58ed77a2814a563fa28322ef722",
"created_at": 1686151391,
"kind": 1,
"tags": [
[
"e",
"70c0fbbfb361e1a5e33121959a54368ef9bf960fb4424bf0b260b1c5f505777b",
"",
"root"
],
[
"e",
"9393750e57fb8e122b7e42175ba172fb5cb2b0b8ef1087f0ea195a381aa843cf",
"",
"reply"
],
[
"p",
"498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84"
]
],
"content": "📅 Original date posted:2014-06-23\n📝 Original message:On Mon, Jun 23, 2014 at 11:50 AM, Jorge Timón \u003cjtimon at monetize.io\u003e wrote:\n\u003e I know there are plans to separate the wallet from the core code and I\n\u003e think it's a great idea that will result in cleaner and more modular\n\u003e software.\n\u003e But it seems like my assumptions on how this would be done may be incorrect.\n\u003e\n\u003e I was assuming that the wallet would consume data from a trusted\n\u003e bitcoind core node using rpc or a better interface like an http rest\n\u003e api (see PR #2844).\n\nIt's least surprising if the wallet works as a SPV client by default.\nThen, users can use it without first setting up a core. Thus the idea\nwould be to use P2P primarily.\n\nThere could be a mode to use a trusted core by RPC for\nmempool/conflicted transaction validation and such. But I'm not sure\nabout this - as we've seen, pure-SPV wallets work pretty well. If you\nwant it to act as an edge router you can point a SPV wallet at your\ntrusted core as well.\n\nThere are no plans for adding Electrum-like functionality to bitcoind.\nThere is already Electrum. Let's not reinvent any wheels.\n\n\u003e So the core would take care of the hard consensus stuff, and the\n\u003e wallet would maintain its own database with private keys, addresses,\n\u003e balances, etc. and would consume some data contained in bitcoind's\n\u003e database.\n\nRight, the wallet would keep track of those.\n\n\u003e I also assumed that the interface between wallet and core would\n\u003e include queries to the UTXO (see PR #4351) and maybe TXO (see PR\n\u003e #3652) for getting the historic balances.\n\u003e\n\u003e As said, I'm not sure these assumptions are true anymore so I ask.\n\u003e Is this the plan?\n\u003e Is the plan that the wallet will use the p2p directly and maintain its\n\u003e own chain database?\n\nIt does not need to keep a full chain database. But it needs its own\nrecord of the chain, headers-only + what concerns the keys in the\nwallet.\n\nWladimir",
"sig": "b480efe303f07fe8d38864d123154243bd1558c1dea791f4c4d2402d9a77763af53486b96b3d2b96b8ba6cdb2e16cb7d3595b8b2b40ff60062d42700f38e4f14"
}