mirror of
https://github.com/hinto-janai/cuprate.git
synced 2024-11-16 15:58:14 +00:00
Boog900
8227c28604
* update monero-serai * update monero-serai + change height to `usize` * fix merge * fix merge * fix doc * fix clippy take 2 * misc changes * move RPC imports to dev deps * handle miner txs when calculating fee * Update consensus/rules/src/blocks.rs Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * Update consensus/rules/src/transactions.rs Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * Update storage/blockchain/src/ops/tx.rs Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * Update test-utils/src/data/free.rs Co-authored-by: hinto-janai <hinto.janai@protonmail.com> * fixes * fix clippy --------- Co-authored-by: hinto-janai <hinto.janai@protonmail.com> |
||
---|---|---|
.. | ||
fast-sync | ||
rules | ||
src | ||
tests | ||
Cargo.toml | ||
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::Service
s 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.