tmpolaczyk

So, a few concerns after looking at the data from the past 10000 blocks: * Value transfer transactions almost never fill up their reserved block space. This means that most...

I tested the case where we alternate one block with transactions and one empty block, to simulate a bit the data request case, and the result is that the estimate...

Not sure if I am doing something wrong but I get some very weird estimates in this one case: * Fill the queue with normal priorities (max 1_000_000 min 1_000)...

The capacity issue is not fixed yet, see this test: ```rust #[test] fn engine_capacity_3() { let mut engine = PriorityEngine::with_capacity(3); let priorities_list = (1..=9) .map(|i| Priorities { drt_highest: Priority::from(i), drt_lowest:...

The capacity is still broken, now the old test with capacity 2 doesn't pass. Also I'm thinking about the `MINIMUM_TRACKED_EPOCHS` variable which is set to 20, because the stinky priority...

Alright, this looks merge-able. Shall we test https://github.com/witnet/sheikah/pull/1801 before merging?

So what would be the expected way to use the wallet API now? Something like this? ``` {"fee":{"relative":"1.0"}} ```

This is caused by `structopt 0.3.26`, opened issue #2266 to upgrade it.

The conversion from bytes to string is implemented here: https://github.com/witnet/witnet-rust/blob/63920bd875563741850225dd28ce98849adad299/rad/src/lib.rs#L242-L248 We are using this method from the surf library, which only supports UTF8: https://docs.rs/surf/2.3.2/surf/struct.Response.html#method.body_string There is a body_bytes method which...

So this does not work as nicely as expected, because it turns out that writing every item to the storage again does increase the total size used by rocksdb, even...