SyntheticBird/cuprate-hinto-janai
1
0
Fork 0
mirror of https://github.com/hinto-janai/cuprate.git synced 2024-12-22 11:39:30 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
cuprate-hinto-janai/consensus
History
Boog900 b44c6b045b
Consensus: add alt-chain handling (#214) 
* add `pop_blocks` to the difficulty cache

* add a rolling median struct

* use RollingMedian in weight cache

* add pop_blocks to weight cache

* add alt context cache

* add getting alt RX vms

* rework alt cache

* add alt block verify function

* keep alt caches around

* add alt checked alt blocks to the cache

* check the alt blocks timestamp

* add docs + cleanup code

* add popping blocks from the context cache

* finish popping blocks + fix tests

* fix doc

* add a test popping blocks from HF cache

* add a request to clear alt caches

* add back lint

* Apply suggestions from code review

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

* review fixes

* small changes

* change panic doc

---------

Co-authored-by: hinto-janai <hinto.janai@protonmail.com>
2024-07-29 01:13:08 +01:00
..
fast-sync Consensus: add alt-chain handling (#214) 2024-07-29 01:13:08 +01:00
rules Consensus: add alt-chain handling (#214) 2024-07-29 01:13:08 +01:00
src Consensus: add alt-chain handling (#214) 2024-07-29 01:13:08 +01:00
tests Consensus: use cuprate-types types (#145) 2024-06-04 18:19:35 +01:00
Cargo.toml Consensus: add alt-chain handling (#214) 2024-07-29 01:13:08 +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.