4

Most likely this is due to a mismatch between the sqlite3 version that c-lightining was compiled with and the version your OS currently has installed. With the recently release v0.10 2, c-lightining now accepts a far wider range of library versions, so upgrading should address the issue.


3

I think you are confusing what it means to store things "in memory". As you say, indeed, the block index DB and the chainstate DB are both levelDB databases stored on disk. However, while Bitcoin Core is running, parts (or all) of these databases are loaded into memory to speed things up. The "in memory" part isn't a separate database. So ...


2

Backwards compatibility is a massive priority for Core and it is generally very conservative in its technology choices. I don't think it would consider a new (database) technology until it had been proven over many years on other projects. It is providing a consensus engine and infrastructure and doesn't have the same tolerance as startups or bigger ...


2

An extended public key contains the chaincode, so it is not stored separately. So the tpubs that you have found will contain the chaincode. The private keys are not encrypted, and unencrypted private keys are stored using DER serialization. This method produces a private key that is 214 bytes, with the vast majority of the data being irrelevant. Private keys ...


1

You clarified in the comments that you are using BigQuery datasets and so you are right Taproot transactions should eventually be labelled as witness_v1_.... Taproot only activated a couple of days ago at the time of writing so presumably the authors haven't added Taproot support yet. You can either wait for them to do so (or request they do!) or find an ...


1

I've written an open-access academic paper on Bitcoin full node data here, and the data is in the Electronic Supplements. I explain in the Appendix how I get and prepare the data if you need more fine-grained analyses. The data is country-year from 2014-2018. Good luck! PS: The data includes Bitcoin merchant data worldwide too. Please do cite the paper after ...


1

Why this is hard Bitcoin Core is chiefly a tool to synchronize with the current state of the network and to enforce the consensus rules with a self-owned piece of hardware. Beside being on the same page regarding the rules, this requires the node only to keep track of the ledger, the Unspent Transaction Output (UTXO) set. Bitcoin transactions need to be ...


1

Blockchain: Chain of blocks +++++----------++++---------++++++---------+++++++ Who creates the blocks? Miners Who validates, saves and relay these blocks? Full nodes https://bitcoin.stackexchange.com/a/103172/ Different full node implementations for Bitcoin: Core, btcd, bcoin, gocoin, libbitcoin, knots, etc. Database used by Bitcoin Core: Bitcoin Core ...


1

I can't imagine any other reason as to why BDB wasn't dumped altogether if it wasn't for backwards support. There simply is none. The wallet file doesn't need to be a database, it could be a flat text file and that would operate just as well. BDB will remain for compatibility for the foreseeable future, and change is risky, so it remains.


Only top voted, non community-wiki answers of a minimum length are eligible