mirror of
https://github.com/Cuprate/cuprate.git
synced 2024-12-22 19:49:28 +00:00
Boog900
5c08d1a0e2
Some checks failed
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
* fix Rx VM initialization * fix imports * Apply suggestions from code review Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * use checked_sub --------- 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::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.