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

Files

hinto-janai 372cab24d7 cuprated: internal signatures required for RPC pt. 2 (#320 )

* apply diffs

* clippy

* fix tests

* rpc: fix tests

* remove `BlockchainManagerRequest::Overview`

* cuprated/p2p: fix `ConnectionInfo`

* move `CalculatePow`

* remove `AddAuxPow`

* move `Spans` and `NextNeededPruningSeed`

* factor types into `cuprate-types`

* scope cargo features

* fix/doc type serde

* Update binaries/cuprated/src/rpc/request/address_book.rs

Co-authored-by: Boog900 <boog900@tutanota.com>

* Update binaries/cuprated/src/rpc/request/blockchain_context.rs

Co-authored-by: Boog900 <boog900@tutanota.com>

* Update binaries/cuprated/src/rpc/request/blockchain_manager.rs

Co-authored-by: Boog900 <boog900@tutanota.com>

* fmt

* txpool: collapse `TxEntry`

* `ConnectionId`

* fix import

* fix bin

---------

Co-authored-by: Boog900 <boog900@tutanota.com>

2024-11-01 22:25:55 +00:00

context

cuprated: internal signatures required for RPC pt. 2 (#320 )

2024-11-01 22:25:55 +00:00

fast-sync

workspace: Defines cuprate members as workspace dependencies (#326 )

2024-10-24 23:12:30 +01:00

rules

workspace: Defines cuprate members as workspace dependencies (#326 )

2024-10-24 23:12:30 +01:00

src

Move consensus context service into a subcrate. (#318 )

2024-10-17 00:17:58 +01:00

tests

consensus: enable workspace lints (#295 )

2024-09-21 01:32:03 +01:00

Cargo.toml

workspace: Defines cuprate members as workspace dependencies (#326 )

2024-10-24 23:12:30 +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.