Core/grin
0
0
Fork 0
mirror of https://github.com/mimblewimble/grin.git synced 2025-01-21 11:31:08 +03:00
Code Issues Projects Releases Packages Wiki Activity Actions
grin/store/Cargo.toml

20 lines
480 B
TOML
Raw Normal View History

Initial import.
2016-10-21 03:06:12 +03:00
[package]
name = "grin_store"
version = "0.1.0"
authors = ["Ignotus Peverell <igno.peverell@protonmail.com>"]
Add workspace support for all crates
2017-04-06 09:41:49 +03:00
workspace = ".."
Initial import.
2016-10-21 03:06:12 +03:00
[dependencies]
Moved down to the store module some common persistence code.
2017-02-09 22:41:46 +03:00
byteorder = "^0.5"
Prunable MMR storage (#112) * Base MMR storage structures Implementations of the MMR append-only file structure and its remove log. The append-only file is backed by a mmap for read access. The remove log is stored in memory for quick checking and backed by a simple file to persist it. * Add PMMR backend buffer, make PMMR Backend mutable * The Backend trait now has &mut self methods, and an &mut reference in PMMR. This simplifies the implementation of all backends by not forcing them to be interior mutable. Slight drawback is that a backend can't be used directly as long as it's used by a PMMR instance. * Introduced a buffer in the PMMR persistent backend to allow reads before the underlying files are fully flushed. Implemented with a temporary VecBackend. * Implement a prune list to use with dense backends The PruneList is useful when implementing compact backends for a PMMR (for example a single large byte array or a file). As nodes get pruned and removed from the backend to free space, the backend will get more compact but positions of a node within the PMMR will not match positions in the backend storage anymore. The PruneList accounts for that mismatch and does the position translation. * PMMR store compaction Implement actual pruning of the underlying PMMR storage by flushing the remove log. This triggers a rewrite of the PMMR nodes data (hashes and sums), removing pruned nodes. The information of what has been removed is kept in a prune list and the remove log is truncated. * PMMR store pruning tests and fixes
2017-09-05 08:50:25 +03:00
env_logger="^0.3.5"
tweaks to logging configuration (#176) * tweaks to logging configuration * doc port update
2017-10-13 19:42:04 +03:00
slog = { version = "^2.0.12", features = ["max_level_trace", "release_max_level_trace"] }
Integrate sum trees with the rest of the system (#116) * Integrate PMMR and its persistent backend with the Chain * Chain can set tree roots; PMMR backend discard * Check spent and prune for each input in new block * Handling of forks by rewinding the state * More PMMR tests and fixes, mostly around rewind * Rewrite get_unspent to use the sumtrees, fix remaining compilation issues
2017-09-28 02:46:32 +03:00
libc = "^0.2"
Sumtree mmap fix (#217) * fix mmap error with version 0.6.0, and change reference to include tag
2017-10-30 19:43:49 +03:00
memmap = { git = "https://github.com/danburkert/memmap-rs", tag="0.6.0" }
Bump RocksDB to ^0.8.0 (#555)
2017-12-28 23:25:01 +03:00
rocksdb = "^0.8.0"
Initial import.
2016-10-21 03:06:12 +03:00
grin_core = { path = "../core" }
slog-rs logging (#171) * added global slog instance, changed all logging macro formats to include logger instance * adding configuration to logging, allowing for multiple log outputs * updates to test, changes to build docs * rustfmt * moving logging functions into util crate
2017-10-12 19:56:44 +03:00
grin_util = { path = "../util" }
Prunable MMR storage (#112) * Base MMR storage structures Implementations of the MMR append-only file structure and its remove log. The append-only file is backed by a mmap for read access. The remove log is stored in memory for quick checking and backed by a simple file to persist it. * Add PMMR backend buffer, make PMMR Backend mutable * The Backend trait now has &mut self methods, and an &mut reference in PMMR. This simplifies the implementation of all backends by not forcing them to be interior mutable. Slight drawback is that a backend can't be used directly as long as it's used by a PMMR instance. * Introduced a buffer in the PMMR persistent backend to allow reads before the underlying files are fully flushed. Implemented with a temporary VecBackend. * Implement a prune list to use with dense backends The PruneList is useful when implementing compact backends for a PMMR (for example a single large byte array or a file). As nodes get pruned and removed from the backend to free space, the backend will get more compact but positions of a node within the PMMR will not match positions in the backend storage anymore. The PruneList accounts for that mismatch and does the position translation. * PMMR store compaction Implement actual pruning of the underlying PMMR storage by flushing the remove log. This triggers a rewrite of the PMMR nodes data (hashes and sums), removing pruned nodes. The information of what has been removed is kept in a prune list and the remove log is truncated. * PMMR store pruning tests and fixes
2017-09-05 08:50:25 +03:00
[dev-dependencies]
time = "^0.1"
Reference in a new issue Copy permalink