2019-08-29 14:46:54 -07:00
|
|
|
[package]
|
|
|
|
|
name = "zebra-consensus"
|
2023-01-30 20:53:27 -08:00
|
|
|
version = "1.0.0-beta.20"
|
2019-10-08 09:25:59 -07:00
|
|
|
authors = ["Zcash Foundation <zebra@zfnd.org>"]
|
|
|
|
|
license = "MIT OR Apache-2.0"
|
Enforce Rust edition 2021 (#3332)
* Rust edition 2021: zebra-network, cargo fix --edition and clippy --fix
* Rust edition 2021: zebra-chain, cargo fix --edition
* Rust edition 2021: tower-batch, cargo fix --edition
* Rust edition 2021: tower-fallback, cargo fix --edition
* Rust edition 2021: zebra-client, cargo fix --edition
* Rust edition 2021: zebra-consensus, cargo fix --edition
* Rust edition 2021: zebra-rpc, cargo fix --edition
* Rust edition 2021: zebra-state, cargo fix --edition
* Rust edition 2021: zebra-state, cargo fix --edition
* Rust edition 2021: zebra-test, cargo fix --edition
* Rust edition 2021: zebra-utils, cargo fix --edition
* Rust edition 2021: zebrad, cargo fix --edition
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-01-14 04:10:18 -08:00
|
|
|
edition = "2021"
|
2019-08-29 14:46:54 -07:00
|
|
|
|
Send crawled transaction IDs to downloader (#2801)
* Rename type parameter to be more explicit
Replace the single letter with a proper name.
* Remove imports for `Request` and `Response`
The type names will conflict with the ones for the mempool service.
* Attach `Mempool` service to the `Crawler`
Add a field to the `Crawler` type to store a way to access the `Mempool`
service.
* Forward crawled transactions to downloader
The crawled transactions are now sent to the transaction downloader and
verifier, to be included in the mempool.
* Derive `Eq` and `PartialEq` for `mempool::Request`
Make it simpler to use the `MockService::expect_request` method.
* Test if crawled transactions are downloaded
Create some dummy crawled transactions, and let the crawler discover
them. Then check if they are forwarded to the mempool to be downloaded
and verified.
* Don't send empty transaction ID list to downloader
Ignore response from peers that don't provide any crawled transactions.
* Log errors when forwarding crawled transaction IDs
Calling the Mempool service should not fail, so if an error happens it
should be visible. However, errors when downloading individual
transactions can happen from time to time, so there's no need for them
to be very visible.
* Document existing `mempool::Crawler` test
Provide some depth as to what the test expect from the crawler's
behavior.
* Refactor to create `setup_crawler` helper function
Make it easier to reuse the common test setup code.
* Simplify code to expect requests
Now that `zebra_network::Request` implement `Eq`, the call can be
simplified into `expect_request`.
* Refactor to create `respond_with_transaction_ids`
A helper function that checks for a network crawl request and responds
with the given list of crawled transaction IDs.
* Refactor to create `crawler_iterator` helper
A function to intercept and respond to the fanned-out requests sent
during a single crawl iteration.
* Refactor to create `respond_to_queue_request`
Reduce the repeated code necessary to intercept and reply to a request
for queuing transactions to be downloaded.
* Add `respond_to_queue_request_with_error` helper
Intercepts a mempool request to queue transactions to be downloaded, and
responds with an error, simulating an internal problem in the mempool
service implementation.
* Derive `Arbitrary` for `NetworkUpgrade`
This is required for deriving `Arbitrary` for some error types.
* Derive `Arbitrary` for `TransactionError`
Allow random transaction errors to be generated for property tests.
* Derive `Arbitrary` for `MempoolError`
Allow random Mempool errors to be generated for property tests.
* Test if errors don't stop the mempool crawler
The crawler should be robust enough to continue operating even if the
mempool service fails to download transactions or even fails to handle
requests to enqueue transactions.
* Reduce the log level for download errors
They should happen regularly, so there's no need to have them with a
high visibility level.
Co-authored-by: teor <teor@riseup.net>
* Stop crawler if service stops
If `Mempool::poll_ready` returns an error, it's because the mempool
service has stopped and can't handle any requests, so the crawler should
stop as well.
Co-authored-by: teor <teor@riseup.net>
Co-authored-by: Conrado Gouvea <conrado@zfnd.org>
2021-10-04 17:55:42 -07:00
|
|
|
[features]
|
|
|
|
|
default = []
|
2023-01-16 13:39:47 -08:00
|
|
|
|
|
|
|
|
# Production features that activate extra dependencies, or extra features in dependencies
|
|
|
|
|
|
|
|
|
|
# Experimental mining RPC support
|
2023-01-11 15:39:51 -08:00
|
|
|
getblocktemplate-rpcs = [
|
2023-01-16 13:39:47 -08:00
|
|
|
"zebra-state/getblocktemplate-rpcs",
|
|
|
|
|
"zebra-node-services/getblocktemplate-rpcs",
|
|
|
|
|
"zebra-chain/getblocktemplate-rpcs",
|
2023-01-11 15:39:51 -08:00
|
|
|
]
|
2023-01-16 13:39:47 -08:00
|
|
|
|
|
|
|
|
# Test-only features
|
2022-03-30 11:23:55 -07:00
|
|
|
proptest-impl = ["proptest", "proptest-derive", "zebra-chain/proptest-impl", "zebra-state/proptest-impl"]
|
Send crawled transaction IDs to downloader (#2801)
* Rename type parameter to be more explicit
Replace the single letter with a proper name.
* Remove imports for `Request` and `Response`
The type names will conflict with the ones for the mempool service.
* Attach `Mempool` service to the `Crawler`
Add a field to the `Crawler` type to store a way to access the `Mempool`
service.
* Forward crawled transactions to downloader
The crawled transactions are now sent to the transaction downloader and
verifier, to be included in the mempool.
* Derive `Eq` and `PartialEq` for `mempool::Request`
Make it simpler to use the `MockService::expect_request` method.
* Test if crawled transactions are downloaded
Create some dummy crawled transactions, and let the crawler discover
them. Then check if they are forwarded to the mempool to be downloaded
and verified.
* Don't send empty transaction ID list to downloader
Ignore response from peers that don't provide any crawled transactions.
* Log errors when forwarding crawled transaction IDs
Calling the Mempool service should not fail, so if an error happens it
should be visible. However, errors when downloading individual
transactions can happen from time to time, so there's no need for them
to be very visible.
* Document existing `mempool::Crawler` test
Provide some depth as to what the test expect from the crawler's
behavior.
* Refactor to create `setup_crawler` helper function
Make it easier to reuse the common test setup code.
* Simplify code to expect requests
Now that `zebra_network::Request` implement `Eq`, the call can be
simplified into `expect_request`.
* Refactor to create `respond_with_transaction_ids`
A helper function that checks for a network crawl request and responds
with the given list of crawled transaction IDs.
* Refactor to create `crawler_iterator` helper
A function to intercept and respond to the fanned-out requests sent
during a single crawl iteration.
* Refactor to create `respond_to_queue_request`
Reduce the repeated code necessary to intercept and reply to a request
for queuing transactions to be downloaded.
* Add `respond_to_queue_request_with_error` helper
Intercepts a mempool request to queue transactions to be downloaded, and
responds with an error, simulating an internal problem in the mempool
service implementation.
* Derive `Arbitrary` for `NetworkUpgrade`
This is required for deriving `Arbitrary` for some error types.
* Derive `Arbitrary` for `TransactionError`
Allow random transaction errors to be generated for property tests.
* Derive `Arbitrary` for `MempoolError`
Allow random Mempool errors to be generated for property tests.
* Test if errors don't stop the mempool crawler
The crawler should be robust enough to continue operating even if the
mempool service fails to download transactions or even fails to handle
requests to enqueue transactions.
* Reduce the log level for download errors
They should happen regularly, so there's no need to have them with a
high visibility level.
Co-authored-by: teor <teor@riseup.net>
* Stop crawler if service stops
If `Mempool::poll_ready` returns an error, it's because the mempool
service has stopped and can't handle any requests, so the crawler should
stop as well.
Co-authored-by: teor <teor@riseup.net>
Co-authored-by: Conrado Gouvea <conrado@zfnd.org>
2021-10-04 17:55:42 -07:00
|
|
|
|
2019-08-29 14:46:54 -07:00
|
|
|
[dependencies]
|
2022-03-06 18:07:25 -08:00
|
|
|
blake2b_simd = "1.0.0"
|
2022-05-18 18:03:55 -07:00
|
|
|
bellman = "0.13.0"
|
|
|
|
|
bls12_381 = "0.7.0"
|
2022-07-17 15:43:29 -07:00
|
|
|
halo2 = { package = "halo2_proofs", version = "0.2.0" }
|
2022-05-18 18:03:55 -07:00
|
|
|
jubjub = "0.9.0"
|
2022-03-06 18:07:25 -08:00
|
|
|
rand = { version = "0.8.5", package = "rand" }
|
2022-12-12 13:27:53 -08:00
|
|
|
rayon = "1.6.1"
|
2021-11-19 15:02:56 -08:00
|
|
|
|
2022-11-16 08:47:45 -08:00
|
|
|
chrono = { version = "0.4.23", default-features = false, features = ["clock", "std"] }
|
2021-11-19 15:02:56 -08:00
|
|
|
dirs = "4.0.0"
|
2022-03-06 18:07:25 -08:00
|
|
|
displaydoc = "0.2.3"
|
2021-11-19 15:02:56 -08:00
|
|
|
lazy_static = "1.4.0"
|
2023-01-02 20:23:09 -08:00
|
|
|
once_cell = "1.17.0"
|
2022-12-27 11:46:22 -08:00
|
|
|
serde = { version = "1.0.152", features = ["serde_derive"] }
|
2020-07-23 20:17:39 -07:00
|
|
|
|
2022-10-21 12:02:04 -07:00
|
|
|
futures = "0.3.25"
|
2022-10-21 14:29:22 -07:00
|
|
|
futures-util = "0.3.25"
|
2022-09-26 21:19:01 -07:00
|
|
|
metrics = "0.20.1"
|
2022-12-19 12:42:02 -08:00
|
|
|
thiserror = "1.0.38"
|
2023-01-18 13:16:37 -08:00
|
|
|
tokio = { version = "1.24.2", features = ["time", "sync", "tracing", "rt-multi-thread"] }
|
2022-06-21 10:12:19 -07:00
|
|
|
tower = { version = "0.4.13", features = ["timeout", "util", "buffer"] }
|
2022-10-12 23:46:27 -07:00
|
|
|
tracing = "0.1.37"
|
2021-02-17 02:01:32 -08:00
|
|
|
tracing-futures = "0.2.5"
|
2020-06-11 02:49:32 -07:00
|
|
|
|
2022-10-31 07:15:11 -07:00
|
|
|
orchard = "0.3.0"
|
2021-11-25 08:26:32 -08:00
|
|
|
|
2022-11-18 11:18:57 -08:00
|
|
|
zcash_proofs = { version = "0.9.0", features = ["local-prover", "multicore", "download-params"] }
|
2021-11-19 15:02:56 -08:00
|
|
|
|
2020-08-04 20:03:42 -07:00
|
|
|
tower-fallback = { path = "../tower-fallback/" }
|
2020-07-08 14:23:00 -07:00
|
|
|
tower-batch = { path = "../tower-batch/" }
|
2021-11-19 15:02:56 -08:00
|
|
|
|
2020-10-14 14:06:32 -07:00
|
|
|
zebra-script = { path = "../zebra-script" }
|
2023-01-16 13:39:47 -08:00
|
|
|
zebra-state = { path = "../zebra-state" }
|
|
|
|
|
zebra-node-services = { path = "../zebra-node-services" }
|
|
|
|
|
zebra-chain = { path = "../zebra-chain" }
|
2020-07-08 04:22:36 -07:00
|
|
|
|
2023-01-16 13:39:47 -08:00
|
|
|
# Test-only dependencies
|
2022-02-14 17:44:33 -08:00
|
|
|
proptest = { version = "0.10.1", optional = true }
|
Send crawled transaction IDs to downloader (#2801)
* Rename type parameter to be more explicit
Replace the single letter with a proper name.
* Remove imports for `Request` and `Response`
The type names will conflict with the ones for the mempool service.
* Attach `Mempool` service to the `Crawler`
Add a field to the `Crawler` type to store a way to access the `Mempool`
service.
* Forward crawled transactions to downloader
The crawled transactions are now sent to the transaction downloader and
verifier, to be included in the mempool.
* Derive `Eq` and `PartialEq` for `mempool::Request`
Make it simpler to use the `MockService::expect_request` method.
* Test if crawled transactions are downloaded
Create some dummy crawled transactions, and let the crawler discover
them. Then check if they are forwarded to the mempool to be downloaded
and verified.
* Don't send empty transaction ID list to downloader
Ignore response from peers that don't provide any crawled transactions.
* Log errors when forwarding crawled transaction IDs
Calling the Mempool service should not fail, so if an error happens it
should be visible. However, errors when downloading individual
transactions can happen from time to time, so there's no need for them
to be very visible.
* Document existing `mempool::Crawler` test
Provide some depth as to what the test expect from the crawler's
behavior.
* Refactor to create `setup_crawler` helper function
Make it easier to reuse the common test setup code.
* Simplify code to expect requests
Now that `zebra_network::Request` implement `Eq`, the call can be
simplified into `expect_request`.
* Refactor to create `respond_with_transaction_ids`
A helper function that checks for a network crawl request and responds
with the given list of crawled transaction IDs.
* Refactor to create `crawler_iterator` helper
A function to intercept and respond to the fanned-out requests sent
during a single crawl iteration.
* Refactor to create `respond_to_queue_request`
Reduce the repeated code necessary to intercept and reply to a request
for queuing transactions to be downloaded.
* Add `respond_to_queue_request_with_error` helper
Intercepts a mempool request to queue transactions to be downloaded, and
responds with an error, simulating an internal problem in the mempool
service implementation.
* Derive `Arbitrary` for `NetworkUpgrade`
This is required for deriving `Arbitrary` for some error types.
* Derive `Arbitrary` for `TransactionError`
Allow random transaction errors to be generated for property tests.
* Derive `Arbitrary` for `MempoolError`
Allow random Mempool errors to be generated for property tests.
* Test if errors don't stop the mempool crawler
The crawler should be robust enough to continue operating even if the
mempool service fails to download transactions or even fails to handle
requests to enqueue transactions.
* Reduce the log level for download errors
They should happen regularly, so there's no need to have them with a
high visibility level.
Co-authored-by: teor <teor@riseup.net>
* Stop crawler if service stops
If `Mempool::poll_ready` returns an error, it's because the mempool
service has stopped and can't handle any requests, so the crawler should
stop as well.
Co-authored-by: teor <teor@riseup.net>
Co-authored-by: Conrado Gouvea <conrado@zfnd.org>
2021-10-04 17:55:42 -07:00
|
|
|
proptest-derive = { version = "0.3.0", optional = true }
|
|
|
|
|
|
2020-07-08 14:23:00 -07:00
|
|
|
[dev-dependencies]
|
2022-09-26 15:23:59 -07:00
|
|
|
color-eyre = "0.6.2"
|
2022-08-03 16:42:50 -07:00
|
|
|
# This is a transitive dependency via color-eyre.
|
|
|
|
|
# Enable a feature that makes tinyvec compile much faster.
|
2022-08-04 15:03:24 -07:00
|
|
|
tinyvec = { version = "1.6.0", features = ["rustc_1_55"] }
|
2022-08-03 16:42:50 -07:00
|
|
|
|
2021-11-16 19:26:15 -08:00
|
|
|
hex = "0.4.3"
|
2022-02-14 17:44:33 -08:00
|
|
|
proptest = "0.10.1"
|
Send crawled transaction IDs to downloader (#2801)
* Rename type parameter to be more explicit
Replace the single letter with a proper name.
* Remove imports for `Request` and `Response`
The type names will conflict with the ones for the mempool service.
* Attach `Mempool` service to the `Crawler`
Add a field to the `Crawler` type to store a way to access the `Mempool`
service.
* Forward crawled transactions to downloader
The crawled transactions are now sent to the transaction downloader and
verifier, to be included in the mempool.
* Derive `Eq` and `PartialEq` for `mempool::Request`
Make it simpler to use the `MockService::expect_request` method.
* Test if crawled transactions are downloaded
Create some dummy crawled transactions, and let the crawler discover
them. Then check if they are forwarded to the mempool to be downloaded
and verified.
* Don't send empty transaction ID list to downloader
Ignore response from peers that don't provide any crawled transactions.
* Log errors when forwarding crawled transaction IDs
Calling the Mempool service should not fail, so if an error happens it
should be visible. However, errors when downloading individual
transactions can happen from time to time, so there's no need for them
to be very visible.
* Document existing `mempool::Crawler` test
Provide some depth as to what the test expect from the crawler's
behavior.
* Refactor to create `setup_crawler` helper function
Make it easier to reuse the common test setup code.
* Simplify code to expect requests
Now that `zebra_network::Request` implement `Eq`, the call can be
simplified into `expect_request`.
* Refactor to create `respond_with_transaction_ids`
A helper function that checks for a network crawl request and responds
with the given list of crawled transaction IDs.
* Refactor to create `crawler_iterator` helper
A function to intercept and respond to the fanned-out requests sent
during a single crawl iteration.
* Refactor to create `respond_to_queue_request`
Reduce the repeated code necessary to intercept and reply to a request
for queuing transactions to be downloaded.
* Add `respond_to_queue_request_with_error` helper
Intercepts a mempool request to queue transactions to be downloaded, and
responds with an error, simulating an internal problem in the mempool
service implementation.
* Derive `Arbitrary` for `NetworkUpgrade`
This is required for deriving `Arbitrary` for some error types.
* Derive `Arbitrary` for `TransactionError`
Allow random transaction errors to be generated for property tests.
* Derive `Arbitrary` for `MempoolError`
Allow random Mempool errors to be generated for property tests.
* Test if errors don't stop the mempool crawler
The crawler should be robust enough to continue operating even if the
mempool service fails to download transactions or even fails to handle
requests to enqueue transactions.
* Reduce the log level for download errors
They should happen regularly, so there's no need to have them with a
high visibility level.
Co-authored-by: teor <teor@riseup.net>
* Stop crawler if service stops
If `Mempool::poll_ready` returns an error, it's because the mempool
service has stopped and can't handle any requests, so the crawler should
stop as well.
Co-authored-by: teor <teor@riseup.net>
Co-authored-by: Conrado Gouvea <conrado@zfnd.org>
2021-10-04 17:55:42 -07:00
|
|
|
proptest-derive = "0.3.0"
|
2022-04-28 00:08:30 -07:00
|
|
|
spandoc = "0.2.2"
|
2022-06-14 23:43:20 -07:00
|
|
|
|
2023-01-18 13:16:37 -08:00
|
|
|
tokio = { version = "1.24.2", features = ["full", "tracing", "test-util"] }
|
2022-05-31 20:53:51 -07:00
|
|
|
tracing-error = "0.2.0"
|
2022-10-12 11:12:43 -07:00
|
|
|
tracing-subscriber = "0.3.16"
|
2020-07-08 14:23:00 -07:00
|
|
|
|
2021-07-28 16:55:01 -07:00
|
|
|
zebra-state = { path = "../zebra-state", features = ["proptest-impl"] }
|
2023-01-16 13:39:47 -08:00
|
|
|
zebra-chain = { path = "../zebra-chain", features = ["proptest-impl"] }
|
2020-07-08 14:23:00 -07:00
|
|
|
zebra-test = { path = "../zebra-test/" }
|
