Bitcoin full node and query server

Oct 27, 2024

View in context in the libbitcoin Slack #general mirror.

evoskuil00:34
You’ll get the tx “position” from the txs association table, and input/output positions from the puts association table (it does both).
7 replies · Antoine Poinsot, evoskuil · last Oct 27, 2024
A
Antoine Poinsot00:36
Although for the puts you do store the index explicitly, at least per the PDF?
image.png
evoskuil00:39
Yeah, those were optimized out.
👍 1
evoskuil00:39
I wish it was current, but too much to do. It’s pretty close tho.
A
Antoine Poinsot00:40
No need, i'm really only trying to grasp conceptually.
👍🏻 1
evoskuil00:41
We have a much more detailed design doc. Copies of it are shared way back in #general. But it’s a bit much when starting out.
evoskuil00:44
A put index can be obtained from the put by transitioning to the parent and scanning the put list for the put’s PK. Since the list is bounded it remains constant time. And since that is not needed for sync or validation or block creation or population, it’s more optimal for those to avoid the storage and recovery time.
evoskuil00:46
I have a spreadsheet that was used to predict the storage size from the schema and tuning parameters. Spent a long time optimizing the store for size and time tradeoffs. So some of the schema changed.