cuprate-hinto-janai/consensus
2025-01-29 15:27:30 -05:00
..
context Merge branch 'main' into other 2025-01-29 15:27:30 -05:00
fast-sync Consensus: Improve API () 2025-01-28 22:25:20 +00:00
rules Consensus: Improve API () 2025-01-28 22:25:20 +00:00
src Consensus: Improve API () 2025-01-28 22:25:20 +00:00
tests Merge branch 'main' into other 2025-01-29 15:27:30 -05:00
Cargo.toml Consensus: Improve API () 2025-01-28 22:25:20 +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.