Repository containing ASmap file attestations.
The asmap-data repository contains ASmaps for use with Bitcoin Core. This repository contains attestations on those files.
The full ASmap generation process follows:
Generate ASmap -> encode ASmap -> attest to file hashes -> PR to this repo
(Kartograf) (asmap-tool) (asmap-attest)
For usage instructions of these separate tools see Kartograf and asmap-tool. You must also ensure that the encoded files follow the naming conventions in asmap-data, see also below.
<run epoch>/<signer>: each ASmap from a collaborative run is run at a specific epoch (Unix timestamp), which serves to identify a given run.SHA256SUMS: hashes of thefinal_result.txt, filled and unfilled encoded ASmapSHA256SUMS.asc: detached PGP signature over theSHA256SUMSfile
builder-keys/<signer>.gpg: signer keys
The attestation file should contain three lines, the first for the final result, the second for the filled ASmap and the third for the unfilled ASmap, for example (assuming EPOCH=1700000000000):
cc199d5de04add6b5c2d95a72610c8a1a7b1f41fe01bd2b4c6db17795856aa31 final_result.txt
1146cbba8719cf3988d377df579667f68f97d2376d67755beb1e38194e196cfc 1700000000000_asmap_filled.dat
1c20ea2dee306af0a3ab4eaefaabe1e4c23a1c4256e60639e7ba48b2bbe56f24 1700000000000_asmap_unfilled.dat
To attest to an ASmap, you must have:
- the result file
final_result.txtcontaining the ASmap in text format - encoded the file via
asmap-tool.pyas both filled and unfilled versions - the Unix timestamp associated with the ASmap run
- a PGP key added to the
builder-keysdir in this repo
Attesting to an ASmap output:
env SIGNER=<gpg-key-name>\
ASMAP_TXT=<path/to/final_result.txt>\
ENCODED_FILLED=<path/to/filled.dat>\
ENCODED_UNFILLED=<path/to/unfilled.dat>\
EPOCH=<unix_timestamp>\
./asmap-attestThis will add a SHA256SUMS file and a SHA256SUMS.asc file under the <EPOCH>/<SIGNER> folder.
Verifying attestations in this repo:
./asmap-verifyThis will print out verifications of all attestations in the repo.