mirror of
https://github.com/Cuprate/cuprate.git
synced 2024-11-16 15:58:17 +00:00
Boog900
0622237d19
Some checks failed
Audit / audit (push) Has been cancelled
CI / fmt (push) Has been cancelled
CI / typo (push) Has been cancelled
CI / ci (macos-latest, stable, bash) (push) Has been cancelled
CI / ci (ubuntu-latest, stable, bash) (push) Has been cancelled
CI / ci (windows-latest, stable-x86_64-pc-windows-gnu, msys2 {0}) (push) Has been cancelled
Deny / audit (push) Has been cancelled
* move consensus database to /types * fix `storage` builds * unify `VerifiedBlockInformation` * fix docs * change `Database` trait wording * order imports * service -> blockchain * Apply suggestions from code review Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * fix typo * fix key_images_spent * add back todo * fix tests * service -> blockchain 2 * update docs * update docs 2 --------- Co-authored-by: hinto-janai <hinto.janai@protonmail.com> |
||
|---|---|---|
| .. | ||
| 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::Services 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.