Sign an attestation

A formal attestation of an assumeUTXO snapshot, statement 0.0.1, from your node's own output, signed by your key. An attestation is not replaceable: a wrong one stays, and a correction is a new event. Experiment; the design is issue 1 and issue 4 on the record.

1. What your node computed

The JSON that dumptxoutset printed (or gettxoutsetinfo hash_serialized_3 at the snapshot height)

Network

Method

The JSON from getchainstates on the same node (where its chainstate came from, and whether it is validated) If the chainstate came from a snapshot: that snapshot's height (from getblockheader <snapshot_blockhash>) Implementation: the subversion from your node's getnetworkinfo, pasted, not typed When the node computed it

Optional: build, commit, binary and file hashes (claims about your software; shown in grey until a reproducible build stands behind them)

Release tag (bitcoind --version)

Source commit

sha256 of the bitcoind binary

sha256 of the snapshot file written

Note (optional; at most 200 characters, no links)

2. Your key

A NIP-07 extension signs without showing the page your key. Without one, paste a hex private key for a throwaway or agent key; it stays in this tab and is never sent anywhere.

or a private key (hex)

3. The statement

…

4. The event (kind 3332, not replaceable)

Publish to a relay (your click, your event)

To put it on the record, open a pull request adding the file as attestations/<network>-<height>/<pubkey>.json in assumeutxo/assumeutxo.github.io.