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

Files

hinto-janai fcbf260747 workspace: initial release cycle files (#370 )

* initial files

* hashes

* ci: more targets

* release.yml

* moves

* remove commit list

* typo

* add linux arm to `monerod-download`

* update

* fast sync

* remove `cuprated.service`

* update

* changes

* move contributing

2025-03-11 23:15:53 +00:00

context

clippy: add doc-valid-idents (#378 )

2025-03-08 18:48:47 +00:00

fast-sync

workspace: initial release cycle files (#370 )

2025-03-11 23:15:53 +00:00

rules

clippy: add doc-valid-idents (#378 )

2025-03-08 18:48:47 +00:00

src

clippy: add doc-valid-idents (#378 )

2025-03-08 18:48:47 +00:00

tests

Update to experimental monero oxide api (#386 )

2025-03-06 19:03:25 +00: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.