Preparing Hive Mirrornet (a.k.a. fakenet) for the release candidate testing

# Yet another Hive mirror instance I’ll use this post for on-chain coordination on the progress of its deployment. It will evolve for the next few days as the new instance of the mirror is brought to life. Three months ago I started the first public mirror net instance for Hive. There were three more instances running and it was of great help to all core devs involved in making Hive better. Now I’m in the process of updating it to the release candidate version for HF26. When? Soon^(TM). As you can see in my posts… I mean, by the lack of them, there’s a lot of work going on. # RTFM You can find some more info on the mirrornet (a.k.a. fakenet) in my [previous post](/@gtg/hive-mirrornet-a-k-a-fakenet-is-up-and-running) I strongly recommend you read it before doing anything that involves Hive Mirrornet.  ^{Logo reveal video that I’ve featured in my previous post converted to a fancy animated GIF} # Notes - The "Recipe for Copy&Paste Experts" will currently not work (it needs all the components to be updated) - TBD (see Changelog for the info on progress) - Conversion process is time consuming and resource hungry (like everything that runs on such a huge amount of data), fortunately it needs to be done only once for the whole mirror. Other participants will just download the converted one. - To have a better idea about amount of data, we are processing `629GB` of data, just getting md5 checksum for the input file could take couple of minutes (on regular HDD it might take more than an hour). With 1Gbps network you will need roughly two hours to just download it. - I've used a trick to speed things up - knowing that there were no significant changes in the blockchain converter itself, I’m reusing converted `block_log` that was used for a previous instance of the mirror and resume feature so I could just convert blocks in range `66000000-66755355`. That saves us two days if the replay will succeed. - It wasn't possible to just replay previous instance because the gap between the blocks that was to big and caused unexpected issues. (In the real world scenario it is very unlikely for Hive to be stopped for more than 7 days!) # Changelog - Using current latest `develop` i.e. `5885515c2e99064213b3b2b33708ada28a8702e0`. - Using current state of mainnet, i.e. as the input for converter. - Mainnet uncompressed `block_log` at block `66755355` - size `674947358456` - md5 `0a686f863ab32cc8d6265b3c82384994` - Conversion started (incremental, see Notes above) # Work in progress... This post will be updated during the next few days until the mirror consensus will be fully functional and other participants could join it. That of course will include "starter pack" to download and bootstrap your nodes. So please, pay attention, and then, once it's up and running, please participate. (That's a mirror so you will participate to some extent even if you don't know it ;-) )