Recompute a published hash, and verify a signed event
A published hash without a published recipe cannot be checked by a stranger. They have to
take the issuer's word for it. This works the recipe out from the outside, by trying the
canonicalizations that real systems use and reporting which one reproduces the value.
Read only. Nothing is stored. Nothing you paste is retained after the response.
Which canonicalization reproduces this hash
Paste the JSON object as it was published, and the hash somebody claims was
taken over it. If a recipe reproduces the value, you get the exact expression, and whether
that recipe is RFC 8785 JCS. A hash that cannot be reproduced is reported as not reproduced,
with the number of combinations tried. That is never a finding that the hash is wrong.
Recompute the id, verify the signature, and see what is inside it
Give an event id and this page asks public relays for the signed event over a
WebSocket opened by your browser. The issuer's own servers are not involved in getting it.
The id is then recomputed and the BIP340 signature verified. For any field name you list, the
answer says whether it sits inside the signed bytes or beside them.