Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

BaseChainDB no longer supports a header-only DB

See original GitHub issue

What is wrong?

BaseChainDB._set_as_canonical_chain_head() now expects the DB to contain transactions as well, and that breaks LightChain since it only syncs headers.

When there’s a chain reorg, that method will try to remove tx lookups from the DB, but that crashes because we have no transactions in the DB

Issue Analytics

State:
Created 6 years ago
Comments:7 (4 by maintainers)

Top GitHub Comments

2reactions

gsalgadocommented, Feb 1, 2018

We might want to take it a step further and have one DB containing just the headers and another one containing just the block bodies/receipts. That would potentially allow us to have a single header DB for both light/full modes. Also, given the way full-node sync should be implemented (i.e. fetching/validating header chains before fetching the block bodies), having separate DBs would make it easier for us to parallelize parts of it

0reactions

gsalgadocommented, Jul 12, 2018

We now have separate HeaderDB and ChainDB classes, and the former’s _set_as_canonical_chain_head() method doesn’t expect the DB to contain transactions in case of a chain reorg, so this is fixed

Top Results From Across the Web

Basic Usage Examples — BigchainDB Javascript Driver 0.0.1 ...

If the BigchainDB node requires special HTTP request headers (such as app_id and app_key ) ... the first node does not use custom...

bigchaindb/bigchaindb - Gitter

Hi, During the past few days, I started getting a "INTERNAL SERVER ERROR" response when posting transactions to the test network. I am...

bigchaindb/CHANGELOG.md at master - GitHub

The main BigchainDB Dockerfile (and its generated Docker image) now contains only BigchainDB Server. · Made separate schemas for CREATE and ...

The Transaction, Block and Vote Models — BigchainDB 0.5.1 ...

Currently, BigchainDB only supports indivisible assets. You can't split an asset apart into multiple assets, nor can you combine several assets together ...

A Survey of Ledger Technology-Based Databases - MDPI

Blockchain is an append-only ledger technology that endeavours to be ... database with tamper-evidence and non-repudiation features similar ...