mirror of
https://github.com/hinto-janai/cuprate.git
synced 2024-12-23 03:59:37 +00:00
663c852b13
* Fast sync (work in progress) * Cargo.lock * Add missing hashes file * clippy warnings * Stub of database tool to create the fast sync hashes * Command line arg for target height, error handling * Cargo.lock * fmt and unused imports * fmt * Add license information to consensus/fast-sync/Cargo.toml Co-authored-by: Boog900 <boog900@tutanota.com> * Order imports in consensus/fast-sync/src/create.rs Co-authored-by: Boog900 <boog900@tutanota.com> * beautify hex generation function & fmt * Reorder imports consensus/fast-sync/src/fast_sync.rs |
||
---|---|---|
.. | ||
fast-sync | ||
rules | ||
src | ||
tests | ||
Cargo.toml | ||
README.md |
Consensus Rules
This folder contains 2 crates:
cuprate-consensus-rules
(rules/
directory)cuprate-consensus
cuprate-consensus-rules
contains the raw-rules and is built to be a more flexible library which requires the user
to give the correct data and do minimal calculations.
cuprate-consensus
on the other hand contains multiple tower::Service
s that handle transaction/block verification as a
whole with a context
service that keeps track of blockchain state. cuprate-consensus
uses cuprate-consensus-rules
internally.
If you are looking to use Monero consensus rules it's recommended you try to integrate cuprate-consensus
and fall back
to cuprate-consensus-rules
if you need more flexibility.