Value of next_shuffle_block_num after hardfork 26
After query
{ "jsonrpc": "2.0" "method": "database_api.get_witness_schedule", "id": 1 }
We get
{ "jsonrpc": "2.0", "result": { "id": 0, "current_virtual_time": "0", "next_shuffle_block_num": 252, ...
This is on head block 256, next_shuffle_block_num should be greater then head. When running testnet this problem appears after hardfork 26 (before applying hardfork value is as expected).
Maybe if we have mirrornet with applied hardfork 26 we could also observe this issue there.