2e9a9b1121
* Problem: Validator set not tracked by BigchainDB Solution: BigchainDB depends on tendermint's RPC API to get the validator set which is not avaiable during replay so the validators set should be tracked inside BigchainDB * Problem: Unclear code and documentation Solution: Fix decode_validator and docs strings * Problem: Doc strings missing Solution: Add doc string for store_validato_set
Overview
A high-level description of the files and subdirectories of BigchainDB.
Files
lib.py
The BigchainDB class is defined here. Most node-level operations and database interactions are found in this file. This is the place to start if you are interested in implementing a server API, since many of these class methods concern BigchainDB interacting with the outside world.
models.py
Block, Transaction, and Asset classes are defined here. The classes mirror the block and transaction structure from the documentation, but also include methods for validation and signing.
consensus.py
Base class for consensus methods (verification of votes, blocks, and transactions). The actual logic is mostly found in transaction and block models, defined in models.py.
processes.py
Entry point for the BigchainDB process, after initialization. All subprocesses are started here: processes to handle new blocks, votes, etc.
config_utils.py
Methods for managing the configuration, including loading configuration files, automatically generating the configuration, and keeping the configuration consistent across BigchainDB instances.
Folders
commands
Contains code for the CLI for BigchainDB.
db
Code for building the database connection, creating indexes, and other database setup tasks.