mirror of
https://github.com/Cuprate/cuprate.git
synced 2024-12-22 19:49:28 +00:00
Boog900
1a178381dd
* split the DB service abstraction * fix ci * misc changes * Apply suggestions from code review Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * review fixes * Update storage/service/Cargo.toml Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * Update storage/service/Cargo.toml Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * fix clippy * fix doc * `bc` -> `blockchain` * doc fixes * Update storage/service/README.md Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * cargo fmt --------- Co-authored-by: hinto-janai <hinto.janai@protonmail.com> |
||
---|---|---|
.. | ||
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.