tmpolaczyk

For example this function is missing the precondition logic, used in data request tests: https://github.com/witnet/witnet-rust/blob/65049271c91abb75fc3430ee0c9feb45df31698a/node/tests/data_request_examples.rs#L47

Another example is the retrieval timeout: the witnet-toolkit does not implement that feature so sometimes it can "hang", breaking the bridge. See https://github.com/witnet/price_feed_poller/pull/34

This would be useful now to verify that any changes to validations do not affect old blocks from the mainnet. That's useful to verify that new nodes will be able...

`websocket` is part of the dependency tree of the old decentralized ethereum bridge: ``` $ cargo tree --no-dedupe --workspace -i websocket websocket v0.21.1 └── web3 v0.10.0 └── witnet-ethereum-bridge v0.1.0 (/witnet-rust/bridges/ethereum)...

This is one of the problems that are blocking #1583. The simplest solution would be to return an error if there is already a ChainState with different consensus constants.

I think it refers to an identity reducer that can do `[T] => [T]`, to be used in the aggregation stage. The use case would be to get different kinds...

We use two different versions of tokio: `0.1.22` and `1.12.0`. I opened #2119 to update from `1.12.0` to the latest version, but any packages that still use version `0.1.22` will...

This is the function that converts a wallet error into a JSON-RPC error with (code, message, data) fields: https://github.com/witnet/witnet-rust/blob/cc772097b883d7470298328ac625200bfc163a74/wallet/src/actors/app/error.rs#L32 I think most of the errors are "Validation Error" with code...

If I remember correctly, all the commit transactions should be equally valid to ensure a fair network. This is because if one node is 100% sure that it will be...

> I thought about using a more complex function that is hard to predict upfront, but minimizing something like that would essentially transform the node operation to be computationally intensive,...