📅 Original date posted:2015-08-20
📝 Original message:I dont think a libconsensus would have any kind of networking layer, nor
is C++ an antique tool set (hopefully libconsensus can avoid a boost
dependency, though thats not antique either). Ideally it would have a
simple API to give it blocks and a simple API for it to inform you of
what the current chain is. If you really want to get fancy maybe it has
pluggable block storage, too, but I dont see why you couldnt use this in
~any client?
On 08/20/15 08:35, Tamas Blummer via bitcoin-dev wrote:
> Every re-implementation, re-factoring even copy-paste introduces a risk of disagreement,
> but also open the chance of doing the work better, in the sense of software engineering.
>
>> On Aug 20, 2015, at 10:06, Jorge Timón <jtimon at jtimon.cc> wrote:
>>
>>
>> But the goal is not reimplementing the consensus rules but rather
>> extract them from Bitcoin Core so that nobody needs to re-implement
>> them again.
>
>
>
> My goal is different. Compatibility with Bitcoin is important as I also want to deal with Bitcoins,
> but it is also imperative to be able to create and serve other block chains with other rules and for those
> I do not want to carry on the legacy of an antique tool set and a spaghetti style.
>
> Bits of Proof uses scala (akka networking), java (api service), c++ (leveledb and now libconsensus)
> and I am eager to integrate secp256k1 (c) as soon as part of consensus. The choices were
> made because each piece appears best in what they do.
>
> Tamas Blummer
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
Matt Corallo [ARCHIVE] /
npub1e4…jxmcu
2023-06-07 17:37:17
in reply to nevent1q…c8sz
Author Public Key
npub1e46n428mcyfwznl7nlsf6d3s7rhlwm9x3cmkuqzt3emmdpadmkaqqjxmcuPublished at
2023-06-07 17:37:17Event JSON
{
"id": "8ea8dd765d644dc56cccd63ec48aab21fa854d093930e2e53f66fcf733da57b7",
"pubkey": "cd753aa8fbc112e14ffe9fe09d3630f0eff76ca68e376e004b8e77b687adddba",
"created_at": 1686159437,
"kind": 1,
"tags": [
[
"e",
"62eaaecf7e0dd571a7fefc51979233ca5e3a2661a7ebffd6475a1fa69ae78e93",
"",
"root"
],
[
"e",
"2876057d444a62f0170db4ccf8cf19f4a52ec09e0fc23d094c824c433931ed2c",
"",
"reply"
],
[
"p",
"c632841665fccdabf021322b1d969539c9c1f829ceed38844fea24e8512962d7"
]
],
"content": "📅 Original date posted:2015-08-20\n📝 Original message:I dont think a libconsensus would have any kind of networking layer, nor\nis C++ an antique tool set (hopefully libconsensus can avoid a boost\ndependency, though thats not antique either). Ideally it would have a\nsimple API to give it blocks and a simple API for it to inform you of\nwhat the current chain is. If you really want to get fancy maybe it has\npluggable block storage, too, but I dont see why you couldnt use this in\n~any client?\n\nOn 08/20/15 08:35, Tamas Blummer via bitcoin-dev wrote:\n\u003e Every re-implementation, re-factoring even copy-paste introduces a risk of disagreement,\n\u003e but also open the chance of doing the work better, in the sense of software engineering.\n\u003e \n\u003e\u003e On Aug 20, 2015, at 10:06, Jorge Timón \u003cjtimon at jtimon.cc\u003e wrote:\n\u003e\u003e\n\u003e\u003e\n\u003e\u003e But the goal is not reimplementing the consensus rules but rather\n\u003e\u003e extract them from Bitcoin Core so that nobody needs to re-implement\n\u003e\u003e them again.\n\u003e \n\u003e \n\u003e \n\u003e My goal is different. Compatibility with Bitcoin is important as I also want to deal with Bitcoins,\n\u003e but it is also imperative to be able to create and serve other block chains with other rules and for those\n\u003e I do not want to carry on the legacy of an antique tool set and a spaghetti style.\n\u003e \n\u003e Bits of Proof uses scala (akka networking), java (api service), c++ (leveledb and now libconsensus)\n\u003e and I am eager to integrate secp256k1 (c) as soon as part of consensus. The choices were\n\u003e made because each piece appears best in what they do.\n\u003e \n\u003e Tamas Blummer\n\u003e \n\u003e \n\u003e \n\u003e _______________________________________________\n\u003e bitcoin-dev mailing list\n\u003e bitcoin-dev at lists.linuxfoundation.org\n\u003e https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\u003e",
"sig": "8209aed8262e3a749f666f9803384d8c1ec7628fcfda823643105c544cf27f869290f7a3ef7157b059ae21c6282d6a1b0c1ff4ba7573eb7cea2e34b68d4c7451"
}