cuprate-hinto-janai/consensus
hinto.janai f7ecd747c5
Some checks failed
Deny / audit (push) Has been cancelled
Audit / audit (push) Has been cancelled
Merge branch 'main' into sig
2024-10-25 17:16:08 -04:00
..
context Merge branch 'main' into sig 2024-10-25 17:16:08 -04:00
fast-sync workspace: Defines cuprate members as workspace dependencies (#326) 2024-10-24 23:12:30 +01:00
rules workspace: Defines cuprate members as workspace dependencies (#326) 2024-10-24 23:12:30 +01:00
src Move consensus context service into a subcrate. (#318) 2024-10-17 00:17:58 +01:00
tests consensus: enable workspace lints (#295) 2024-09-21 01:32:03 +01:00
Cargo.toml workspace: Defines cuprate members as workspace dependencies (#326) 2024-10-24 23:12:30 +01:00
README.md Cleanup & Document consensus (#65) 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.