Add 1706536800_asmap.dat

[fjahr]

This adds the asmap.dat result for the coordinated launch from https://github.com/fjahr/asmap-data/issues/9 from the epoch 1706536800. We had a match from 4 out of 6 participants in the coordinated launch.

To confirm the result of the encoding you also need to check out bitcoin/bitcoin#28793 to get the latest version of asmap-tool.

$ shasum -a 256 1706536800_final_result.txt
05ee8c4a7e1363f5eb0e3888059093bffe788d77b60bb6814f1865ee443b1c04  1706536800_final_result.txt

$ python3 contrib/asmap/asmap-tool.py encode 1706536800_final_result.txt 1706536800_asmap.dat

$ shasum -a 256 1706536800_asmap.dat
2155eab71080099f469c524e49ff71d264859b023431b27aa52f58315a640ff1  1706536800_asmap.dat

[Sjors]

Matches!

[0xB10C]

I have a matching asmap.dat with 2155eab71080099f469c524e49ff71d264859b023431b27aa52f58315a640ff1 too!

Loading that file also seems to work. However, it prints a different version/hash. Not sure how this hash is calculated.

2024-02-06T13:32:41Z Opened asmap file "[..]/1706536800_asmap.dat" (1681485 bytes) from disk
2024-02-06T13:32:41Z Using asmap version 3ee55159b40d3ae5864c33d6cf4387a1302d616dd1c8fac7ef54c265952c5189 for IP bucketing

[fjahr]

However, it prints a different version/hash. Not sure how this hash is calculated.

Yeah, it prints a double-SHA256 hash of the decoded data. Not sure it is needed to print the file hash as well. I will keep it in mind if this keeps confusing people.