mirror of https://github.com/Cuprate/cuprate.git synced 2024-11-16 15:58:17 +00:00

History

Boog900 90027143f0 Some checks failed CI / fmt (push) Has been cancelled Details CI / typo (push) Has been cancelled Details CI / ci (macos-latest, stable, bash) (push) Has been cancelled Details CI / ci (ubuntu-latest, stable, bash) (push) Has been cancelled Details CI / ci (windows-latest, stable-x86_64-pc-windows-gnu, msys2 {0}) (push) Has been cancelled Details Doc / build (push) Has been cancelled Details Doc / deploy (push) Has been cancelled Details consensus: misc fixes (#276 ) * fix decoy checks + fee calculation * fmt		2024-09-10 01:18:26 +01:00
..
fast-sync	Consensus: move more types to `types` (#250 )	2024-08-09 00:56:13 +01:00
rules	helper: add and use `cast` module (#264 )	2024-09-02 18:09:52 +01:00
src	consensus: misc fixes (#276 )	2024-09-10 01:18:26 +01:00
tests	Storage: split the DB service abstraction (#237 )	2024-08-05 21:47:30 +01:00
Cargo.toml	update monero-serai (#201 )	2024-08-07 00:48:53 +01:00
README.md	Cleanup & Document consensus (#65 )	2024-05-31 01:52:12 +01:00

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.