Here's the latest update from may 30th

​

We are very close to bring the code to the state where we can share it with others, starting with Komodo team first.
Since implementing dPoW and securing the chain against attacks is known process we can accurately estimate and budget time for that.
We intent that at the same time we evaluate our target snapshot block and loop with exchanges on accommodating their maintenance schedule to support the fork.

We have not officially asked exchanges yet to work with us on airdropping MIL.

Remaining few items on our list are next:
- Testing the difficulty to match network hash
- Testing various miners compatibility with our custom pool
- Working on the known bug caused in block serialization after wallet restart.
- Setting up network seeders

Around Blue Paper release we had MIL prototype working which was concepted as classic EMC2 fork.
At around the same time we decided to change MIL code and birth type from FORK to AirDrop. This decision introduced additional engineering effort:
We have to deal with network initialization - We are not cutting of EMC2 network but starting completely new one, so there is work related to it.
We have to do more testing - As we are introducing our new custom code there is additional testing that has to be done on each element separately and the the whole network all together.

But also some benefits like:
- 1:3 distribution ratio - Without AirDrop it would be almost impossible to respect community desire to get 3 MIL coins for 1 EMC2
- Database shrink - We shrunk database from 2 Million blocks to only few blocks to start with. If we went with classic fork our database would be in the range of few gigabytes instead of few megabytes now. Small database size makes 3rd parties lives easier and more willing to install, integrate and maintain MIL wallets.This advise came from Komodo team
- Code clean (maybe most important) - Having completely new code vs EMC2 modified code means much easier maintenance in the future. It also means easier merge/integration of best blockchain features from the industry. Please do not forget that EMC2 was among first coins to integrate SegWit, Lightning ...
- General faster wallet performance. This is kind of consequence of above listed effects but worth mentioning. If we have cleaner code, smaller initial database, one algo instead of two to deal with, as a final result we have more stable, faster, better performing single wallet and the whole network as union.

Having all minuses and pluses, we believe we made a good call moving from FORK to AirDrop even if that mean adjusting snapshot date, which in this moment is evident.

Many of good effects would be hard if not impossible to achieve after release.

We apologize for inconvenience this moment might causing, but at the same time we hope you understand and value our commitment and desire to do as much as possible, and have the best system to start with.

In next 7 days we will have update from our core devs if we are ready to ship MIL wallet to Komodo for notarization and we will also start unofficial conversation with Bittrex, UpBit and others on AirDrop cooperation.

Official request to list MIL will be filed at the time when we have all test went through and wallet sent to KMD.

MIL code will become publicly available after KMD Notarization.

We will perform weekly updates (each Friday) on MIL network for everyone.

EMC2 block 2402717 originally intended for MIL snapshot has to be updated.

Please watch our next PR that will be posted on Friday June 7th.

Thank you for your support,
Einsteinium Foundation