cuprate-hinto-janai/consensus
Boog900 b97bbab593
Cuprated: Fix reorgs ()
* fix reorgs

* fix off by 1 and add a test

* commit file

* docs

* remove unneeded fn

* fix tests
2025-03-21 17:52:10 +00:00
..
context Cuprated: Fix reorgs () 2025-03-21 17:52:10 +00:00
fast-sync fast-sync: add tests () 2025-03-19 15:52:05 +00:00
rules clippy: add doc-valid-idents () 2025-03-08 18:48:47 +00:00
src Cuprated: Fix reorgs () 2025-03-21 17:52:10 +00:00
tests Update to experimental monero oxide api () 2025-03-06 19:03:25 +00:00
Cargo.toml consensus: Batch get outputs () 2025-03-06 16:17:09 +00:00
README.md Cleanup & Document consensus () 2024-05-31 01:52:12 +01:00

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.