Cuprate/cuprate
Cuprate/cuprate
1
0
Fork 0
mirror of https://github.com/Cuprate/cuprate.git synced 2024-09-28 20:51:03 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
cuprate/consensus
History
Boog900 0e5555d4d4
Consensus: block batch prepper (#151) 
* add block batch prepper

* Apply suggestions from code review

Co-authored-by: hinto-janai <hinto.janai@protonmail.com>

* review comments

* review comments

* fix doc

---------

Co-authored-by: hinto-janai <hinto.janai@protonmail.com>
2024-06-07 21:23:48 +01:00
..
rules Consensus: fix panic in batch verifier (#152) 2024-06-07 13:34:53 +01:00
src Consensus: block batch prepper (#151) 2024-06-07 21:23:48 +01:00
tests Consensus: use cuprate-types types (#145) 2024-06-04 18:19:35 +01:00
Cargo.toml Consensus: use cuprate-types types (#145) 2024-06-04 18:19:35 +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.