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

Files

hinto-janai 118f02d52e workspace: Rust 1.85..=1.87 (#482 )

* apply

* remove false positive

* manual_midpoint

* fmt

* fix macro

* reason

* lukka/get-cmake@v4.0.2

* lukka/get-cmake@v4.0.1

* revert cmake

2025-05-27 23:55:14 +01:00

context

workspace: Rust 1.85..=1.87 (#482 )

2025-05-27 23:55:14 +01:00

fast-sync

fast-sync: .bin -> .json (#448 )

2025-05-02 18:55:12 +01:00

rules

workspace: Rust 1.85..=1.87 (#482 )

2025-05-27 23:55:14 +01:00

src

workspace: Rust 1.85..=1.87 (#482 )

2025-05-27 23:55:14 +01:00

tests

cuprated: RPC handlers (#355 )

2025-04-08 17:09:43 +01:00

Cargo.toml

consensus: Batch get outputs (#382 )

2025-03-06 16:17:09 +00: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.