We wanted to add the filled and unfilled versions of the file going forward, per the discussion in #24. The latest_asmap file should be the filled one. I think that's also the reason the new latest file is a lot bigger than the current one, because the file added isn't a filled one but the last time we added a filled one.

thanks, forgot about that. added the hash for the filled file to the OP.

I think the latest_asmap should be the filled one and I would give the unfilled file the extension _unfilled while the filled one has that normal name without an extension, that way its clearer that the filled file is the one we recommend using as the default and that is potentially embedded into core.

ACK, I could reproduce the same files by encoding with and without filling. Also confirmed the file hashes of the files added with the PR.

FYI, the command in the example contains -fill, so it's missing a dash and should be --fill.

FYI, the command in the example contains -fill, so it's missing a dash and should be --fill.

I fixed this, I keep forgetting that I can edit all messages as the repo owner :)

ACK, I could reproduce the same files by encoding with and without filling. Also confirmed the file hashes of the files added with the PR.

$ sha256sum out/1755187200/final_result.txt
97c5e82a1626afdaa40989b957bb84650907c30df9d666f4246f15c5e6db40a7  out/1755187200/final_result.txt
$ python3 ~/bitcoin/contrib/asmap/asmap-tool.py encode --fill ~/kartograf/out/1755187200/final_result.txt 1755187200_asmap.dat
$ sha256sum 1755187200_asmap.dat
447d13a870e42e4a61e7933572b700872386e40529a69a7e0880816acf8a9012  1755187200_asmap.dat

$ python3 ~/bitcoin/contrib/asmap/asmap-tool.py encode ~/kartograf/out/1755187200/final_result.txt 1755187200_asmap.dat
$ sha256sum 1755187200_asmap.dat
8f6325dd68ab387295e20182330ea0f05a3b1c3af6a8efa63d2210950ce88462  1755187200_asmap.dat

Thanks @Emzy !