📅 Original date posted:2015-09-22
📝 Original message:On Fri, Sep 18, 2015 at 2:07 AM, Wladimir J. van der Laan via
bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org> wrote:
> My long-term vision of bitcoind is a P2P node with validation and blockchain store, with a couple of data sources that can be subscribed to or pulled from.
I agree with this long term vision.
Here's how I think it could happen:
1) Libconsensus is completed and moved to a subtree (which has libsecp
as an internal subtree)
2) Bitcoind becomes a subtree of bitcoin-wallet (which has
bitcoin-wallet and bitcoin-qt)
Without aggressively changing it for this purpose, libconsensus should
tend to become C, like libsecp, which is better for proving
correctness.
Hopefully at some point it won't take much to move to C.
Upper layers should move to C++11
Don't focus on the git subtrees, the basic architecture is bitcoin-qt
on top of bitcoin-wallet, bitcoin-wallet on top of bitcoind (and
friends like bitcoin-cli and bitcoin-tx), bitcoind on top of
libconsensus on top of libsecp256k1.
I believe this would maximize the number of people who can safely
contribute to the project.
I also believe this is the architecture most contributors have in mind
for the long term, but I may be wrong about it.
Criticisms to this plan?
Jorge Timón [ARCHIVE] /
npub1fx…cl2d8
2023-06-07 17:41:03
in reply to nevent1q…e27d
Author Public Key
npub1fx98zxt3lzspjs5f4msr0fxysx5euucm29ghysryju7vpc9j0jzqtcl2d8Published at
2023-06-07 17:41:03Event JSON
{
"id": "e51ec1495ec7086851ad5a7b4ba1a7da65068097310a36499b6824663d04ff92",
"pubkey": "498a711971f8a0194289aee037a4c481a99e731b5151724064973cc0e0b27c84",
"created_at": 1686159663,
"kind": 1,
"tags": [
[
"e",
"06584fedf60bc7015c2e887f3ff56bb10e3ef162cbdc9c96bca7ab3007479c6f",
"",
"reply"
],
[
"p",
"a23dbf6c6cc83e14cc3df4e56cc71845f611908084cfe620e83e40c06ccdd3d0"
]
],
"content": "📅 Original date posted:2015-09-22\n📝 Original message:On Fri, Sep 18, 2015 at 2:07 AM, Wladimir J. van der Laan via\nbitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org\u003e wrote:\n\u003e My long-term vision of bitcoind is a P2P node with validation and blockchain store, with a couple of data sources that can be subscribed to or pulled from.\n\nI agree with this long term vision.\nHere's how I think it could happen:\n\n1) Libconsensus is completed and moved to a subtree (which has libsecp\nas an internal subtree)\n\n2) Bitcoind becomes a subtree of bitcoin-wallet (which has\nbitcoin-wallet and bitcoin-qt)\n\nWithout aggressively changing it for this purpose, libconsensus should\ntend to become C, like libsecp, which is better for proving\ncorrectness.\nHopefully at some point it won't take much to move to C.\n\nUpper layers should move to C++11\n\nDon't focus on the git subtrees, the basic architecture is bitcoin-qt\non top of bitcoin-wallet, bitcoin-wallet on top of bitcoind (and\nfriends like bitcoin-cli and bitcoin-tx), bitcoind on top of\nlibconsensus on top of libsecp256k1.\n\nI believe this would maximize the number of people who can safely\ncontribute to the project.\nI also believe this is the architecture most contributors have in mind\nfor the long term, but I may be wrong about it.\n\nCriticisms to this plan?",
"sig": "38dac2e8bb88f757e4aa7f1087ba65d6e1ba1618eb7c38e7b7eeb8fc21d98a0e542e6c95d8abf3dc6e0e28af719d279dc14ff14d18fd0f69d0176a1c1ac51d82"
}