mirror of
https://github.com/Cuprate/cuprate.git
synced 2024-12-22 11:39:26 +00:00
Boog900
8be369846e
Some checks failed
CI / fmt (push) Waiting to run
CI / typo (push) Waiting to run
CI / ci (macos-latest, stable, bash) (push) Waiting to run
CI / ci (ubuntu-latest, stable, bash) (push) Waiting to run
CI / ci (windows-latest, stable-x86_64-pc-windows-gnu, msys2 {0}) (push) Waiting to run
Doc / build (push) Waiting to run
Doc / deploy (push) Blocked by required conditions
Audit / audit (push) Has been cancelled
Deny / audit (push) Has been cancelled
* add cuprated skeleton * fmt and add deny exception * add main chain batch handler * add blockchain init * very rough block manager * misc changes * move more config values * add new tables & types * add function to fully add an alt block * resolve current todo!s * add new requests * WIP: starting re-orgs * add last service request * commit Cargo.lock * add test * more docs + cleanup + alt blocks request * clippy + fmt * document types * move tx_fee to helper * more doc updates * fmt * fix imports * remove config files * fix merge errors * fix generated coins * handle more p2p requests + alt blocks * clean up handler code * add function for incoming blocks * add docs to handler functions * broadcast new blocks + add commands * add fluffy block handler * fix new block handling * small cleanup * increase outbound peer count * fix merge * clean up the blockchain manger * add more docs + cleanup imports * fix typo * fix doc * remove unrelated changes * improve interface globals * manger -> manager * enums instead of bools * move chain service to separate file * more review fixes * add link to issue * fix syncer + update comment * fmt |
||
---|---|---|
.. | ||
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.