Bitcoin full node and query server

Oct 27, 2024

View in context in the libbitcoin Slack #general mirror.

Antoine Poinsot19:42

Here is my "Libbitcoin for Core people" writeup, which intends to conceptually summarizes how Libbitcoin works for people familiar with Bitcoin Core. https://gist.github.com/darosior/97958327835eeef4119418e4d3b6d27f I intend it to post it to Delving Bitcoin (probably tomorrow) so people can discuss it and you can participate if you're so inclined. I tried to keep it a high-level overview, so i've omitted some details you've shared here. These can be brought up if people ask about a certain area in the comments. If you have the time to skim through it please let me know if i got anything wrong or feel i'm misrepresenting something.

evoskuil20:34

When checking a block for confirmability it will for every transaction fetch its prevout transaction(s) (which must have confirmed state, otherwise the block confirmability check fails) and for each prevout it will mark the spender corresponding to the transaction being checked for confirmability as "confirmed" (if there exists any other spender whose related transaction is "confirmed", this is a double spend, the block confirmability check fails).

Validation "fetches" prevouts, confirmability is just a boolean result query. There is no marking of spends or spenders or outputs. Confirmed txs are associated to their containing header (their block), only.