Mario
Mario
Just some figures about the current situation, today there was an average of 25 block candidates per epoch (derived from block #230700 to block #231099 with at least 2 rollbacks...
I just extracted the numbers from the logs of a node by grepping the received block log. Maybe the difference lies in the fact that the node has been up...
This issue is still relevant as it is an attack vector for those nodes with public Json RPC server.
AFAIK, the `signing_committee_length` cannot be less than 1.
I had the same token problem: `Issued in the future`. In my case, the problem was really easy to solve. It seems that the server's clock was out of sync...
Hi @nikeshnazareth ! Thanks for discovering it! Do you mind rebasing the pull request with the master branch? I just merged some changes that fix the [failing checks](https://github.com/witnet/bls-solidity/pull/2/checks?check_run_id=2992897223).