tmpolaczyk

I'm saying that if we find a way to ensure that the blocks have as many commits as possible, then we could order the commits during the reveal stage and...

I found the cause. bn256 keys can be found in two places: the miner key in the block header, and the witness keys in the commit transactions. The miner keys...

## Possible solutions I already tried one solution in the [test branch](https://github.com/tmpolaczyk/witnet-rust/tree/test-bn256-missing-keys), but it changes the ARS logic so it is a hard fork. This solution is to insert all...

Hi, illegal instruction usually means that you are running a binary compiled for a different architecture. In the logs you should see a line like: ``` "Downloading 'witnet-x86_64-pc-windows-msvc.tar.gz'. It may...

Since you are using a slightly old CPU, it is possible that the compiled witnet binary uses some instructions that are not supported by your CPU, for example AVX or...

It looks like an issue with the rocksdb wrapper we are using https://github.com/rust-rocksdb/rust-rocksdb/issues/363

Yes, migrations are hard because we are using bincode. The ChainState struct has support for adding new fields, however these fields must always be at the end of the list...

So having it as part of the ChainState was easier to implement, and it ensures that the stats are always consistent with the chain state. This means that when there...

This warning comes from the `surf` crate, which has just been updated in PR #2085, amazingly. ``` $ cargo tree --no-dedupe --workspace -i cpuid-bool cpuid-bool v0.2.0 └── polyval v0.4.5 └──...

TODO: check if this method persists the data request (for dataRequestReport command)