add 1783008000, update latest_asmap.dat

[jurraca]

This adds the latest_asmap.dat result for the coordinated launch from #60 for epoch 1783008000. We had a match from 6/12 participants, with one more being off by one, and another 2 being off by 3. In both cases the initial assignment can be considered better than the differing assignments.

The sha256 hash after encoding the file are:

final_result.txt (output of the run): 853229f2b3854ca6360ebee3557b55a2693bc6220cf220052708e47e5450087e
filled (encoded with --fill) / latest_asmap.dat: ac39bc1205240969d23b227227889138e3959ad5d7010d86f9165a4a5a8bda0d
unfilled: 0c21f465e29e18ecbf928514954e3d4d0ccca845f9a63d356a3d22b77f574766

To confirm the result of the encoding you can use asmap-tool.

$ sha256sum final_result.txt
853229f2b3854ca6360ebee3557b55a2693bc6220cf220052708e47e5450087e final_result.txt

$ python bitcoin/contrib/asmap/asmap-tool.py encode --fill final_result.txt 1783008000_asmap.dat

$ sha256sum 1783008000_asmap.dat
ac39bc1205240969d23b227227889138e3959ad5d7010d86f9165a4a5a8bda0d 1783008000_asmap.dat

$ python bitcoin/contrib/asmap/asmap-tool.py encode final_result.txt 1783008000_asmap_unfilled.dat

$ sha256sum 1783008000_asmap_unfilled.dat
0c21f465e29e18ecbf928514954e3d4d0ccca845f9a63d356a3d22b77f574766 1783008000_asmap_unfilled.dat

# also check the latest_asmap.dat file is the filled ASmap
$ sha256sum latest_asmap.dat
ac39bc1205240969d23b227227889138e3959ad5d7010d86f9165a4a5a8bda0d latest_asmap.dat

[Emzy]

I got the same asmap.dats.

$ sha256sum out/1783008000/final_result.txt
853229f2b3854ca6360ebee3557b55a2693bc6220cf220052708e47e5450087e  out/1783008000/final_result.txt

$ python ../bitcoin/contrib/asmap/asmap-tool.py encode --fill out/1783008000/final_result.txt 1783008000_asmap.dat

$ sha256sum 1783008000_asmap.dat
ac39bc1205240969d23b227227889138e3959ad5d7010d86f9165a4a5a8bda0d  1783008000_asmap.dat

$ python ../bitcoin/contrib/asmap/asmap-tool.py encode out/1783008000/final_result.txt 1783008000_asmap_unfilled.dat

$ sha256sum 1783008000_asmap_unfilled.dat
0c21f465e29e18ecbf928514954e3d4d0ccca845f9a63d356a3d22b77f574766  1783008000_asmap_unfilled.dat

[fjahr]

ACK 4ebe56d

I got the same hash results for the encoding steps:

$ sha256 1783008000_asmap_unfilled.dat
SHA256 (1783008000_asmap_unfilled.dat) = 0c21f465e29e18ecbf928514954e3d4d0ccca845f9a63d356a3d22b77f574766
$ sha256 1783008000_asmap.dat
SHA256 (1783008000_asmap.dat) = ac39bc1205240969d23b227227889138e3959ad5d7010d86f9165a4a5a8bda0d

I added the raw inputs for others to reproduce here as well: https://github.com/bitcoin-core/asmap-data/releases/tag/1783008000