SyntheticBird/cuprate-hinto-janai
1
0
Fork 0
mirror of https://github.com/hinto-janai/cuprate.git synced 2024-11-16 15:58:14 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
cuprate-hinto-janai/consensus
History
Boog900 be2f3f2672
Consensus: move more types to types (#250) 
* move `HardFork` to `types`

* fmt

* fix tests & doc

* fmt

* fix clippy

* move transaction verification data

* misc fixes

* doc fixes

* update README.md

* review fixes
2024-08-09 00:56:13 +01:00
..
fast-sync Consensus: move more types to types (#250) 2024-08-09 00:56:13 +01:00
rules Consensus: move more types to types (#250) 2024-08-09 00:56:13 +01:00
src Consensus: move more types to types (#250) 2024-08-09 00:56:13 +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.