mirror of https://github.com/MAGICGrants/cuprate-for-explorer.git synced 2026-01-09 19:47:59 -05:00

Files

Boog900 5c08d1a0e2 Consensus: fix Rx VM initialization (#190 )

* fix Rx VM initialization

* fix imports

* Apply suggestions from code review

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

* use checked_sub

---------

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

2024-06-25 01:55:04 +01:00

fast-sync

workspace: enforce crate/directory naming scheme (#164 )

2024-06-24 02:30:47 +01:00

rules

workspace: enforce crate/directory naming scheme (#164 )

2024-06-24 02:30:47 +01:00

src

Consensus: fix Rx VM initialization (#190 )

2024-06-25 01:55:04 +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.