Issues · kulpreet/libbitcoin-mvcc-database · GitHub

Labels Milestones

Take snapshot and sync to disk on shutdown. On startup, read databases from files. Rebuild indexes as we read the databases.

#14

· kulpreet opened

on Aug 13, 2020

Implement snapshot and garbage collector that move all confirmed blocks to disk, and moves all spent outputs (and inputs?) to disk.

#13

· kulpreet opened

on Aug 13, 2020

Run a test with simple setup for blockchain and mvcc database to see if IBD works. Provide a clean way to stop the node if we reach max memory limit.

#12

· kulpreet opened

on Aug 13, 2020

Blog Post: High level architecture decisions we made for this MVCC database.

#11

· kulpreet opened

on Aug 13, 2020

Blog Post: The goals of this database.

#10

· kulpreet opened

on Aug 13, 2020

Blog Post: Why an in memory database with mvcc for libbitcoin?

#9

· kulpreet opened

on Aug 13, 2020

Blog Post: Why an in memory database for bitcoin?

#8

· kulpreet opened

on Aug 13, 2020

Fork blockchain to use mvcc database api. We need to provide a way to retry transactions that rollback.

#7

· kulpreet opened

on Aug 13, 2020

Provide data_base class that uses block database and transaction database

#6

· kulpreet opened

on Aug 13, 2020

Add github actions or travis test to cover the same build matrix as rest of libbitcoin libs

#5

· kulpreet opened

on Aug 13, 2020

Add input and output iterators to transaction_result

#3

· kulpreet opened

on Aug 13, 2020

Implement block_result and transaction_result as delegators to tuple classes

#2

· kulpreet opened

on Aug 13, 2020