Only difference seems to be the final asmap.dat file.

$ shasum -a 256 1704463200/final_result.txt
4aba172195b8dc375c2bb1b39c3508f48c212cedc02983a7dc794a373820653b  1704463200/final_result.txt
$ wc -l 1704463200/final_result.txt
1256210 1704463200/final_result.txt
$ sed '/2606:9dc0:6666::\/48 AS4199999899/d' 1704463200/final_result.txt > 1704463200/final_result_edit.txt
$ wc -l 1704463200/final_result_edit.txt
1256209 1704463200/final_result_edit.txt
$ python3 ~/bitcoin/contrib/asmap/asmap-tool.py encode 1704463200/final_result_edit.txt 1704463200/asmap.dat
$ shasum -a 256 1704463200/asmap.dat
7779317bbd97833e807d453a7fc9bbd73df1d6a9de7dd5c467e573b7718cf1c1  1704463200/asmap.dat

$ ls -l 1704463200/asmap.dat
-rw-r--r-- 1 emzy emzy 1678365 Jan  8 13:55 1704463200/asmap.dat

Seems like the asmap.py tool doesn't create a deterministic asmap.dat.

$ shasum -a 256 final_result_0xb10c.txt
4aba172195b8dc375c2bb1b39c3508f48c212cedc02983a7dc794a373820653b  final_result_0xb10c.txt
$ sed '/2606:9dc0:6666::\/48 AS4199999899/d' final_result_0xb10c.txt > final_result_edit.txt
$ wc -l final_result_edit.txt
1256209 final_result_edit.txt
$ python3 asmap-tool.py encode final_result_edit.txt asmap.dat
$ shasum -a 256 asmap.dat
8706a208e84339b39f42fb9407e6a3260391b339cbfa203b657f10c5dfcd8d6b  asmap.dat

Hm, running it twice on my machine produces the same output asmap.dat.

Can @Emzy or @fjahr, can you upload your file? (you'll have to zip it for github to accept it)

Here's my asmap.dat:
asmap.dat.gz

Hm, running it twice on my machine produces the same output asmap.dat.

I also get the same after a rerun.

Here my asmap.dat:
asmap.dat.gz

The decoded files (asmap-tool.py decode asmap.dat) match again.

Mmm, I got 328c7700ce980e5114047c0757a0159532c5ca51fd46fc62ec9da20e3d951177 on Ubuntu (tried twice), e6b96412647f2f34380e99ed03f8c3ef9eb2f094dcda466db0a1c29f261772c9 on Intel macOS 14.2.1 (tried twice).

Hash of 1704463200_final_result_edit.txt: cedeac924c949895b11ea0245aaf3cfa08ca3838fa8d96580788c382d65c66ea (both on Linux and Mac, so the sed command is probably not the issue)

Sounds like it's putting something machine specific in?

The issue with asmap-tool should be fixed now, please check out the latest version of the branch at bitcoin/bitcoin#28793 and see if we get the same result. I was able to replicate it by using different python versions but didn't test it on multiple platforms yet.

The hash of my file is now 45b87814c47b5ea056c2e47fcc08a75afbb535c8bfb80d734bb364cddb432e73.

Works. Now I got the same asmap.dat file.

~/kartograf/out$ python3 ~/bitcoin/contrib/asmap/asmap-tool.py encode 1704463200/final_result_edit.txt 1704463200/asmap.dat
~/kartograf/out$ shasum -a 256 1704463200/asmap.dat
45b87814c47b5ea056c2e47fcc08a75afbb535c8bfb80d734bb364cddb432e73  1704463200/asmap.dat

I get the same hash now, hooray!

Alright, for the first run two ACKs are good enough for me :)

Please join the next run in ~24h if possible, which hopefully should run a lot cleaner so we can use it as a demo: #7