The Hidden Layer · hunt

S5 · Canary deltaWhat matters is what changed

← All stages

We publish an epoch attestation SIGNED by a key dedicated to the hunt (not to be confused with the warrant canary at /canary — this one is a game artifact). Two versions are online: the current (/hunt/epoch.asc) and the previous (/hunt/epoch-prev.asc).

Import the hunt signing key (/hunt/hunt-signing.asc). VERIFY the signature on BOTH files — an unverified canary is worthless. Then diff them: exactly one "marker:" line changed. Its new value is the answer.

Run this:

curl -sO https://onsecret.net/hunt/hunt-signing.asc && gpg --import hunt-signing.asc
curl -sO https://onsecret.net/hunt/epoch.asc && curl -sO https://onsecret.net/hunt/epoch-prev.asc
gpg --verify epoch.asc && gpg --verify epoch-prev.asc
diff <(gpg -d epoch-prev.asc 2>/dev/null) <(gpg -d epoch.asc 2>/dev/null)

⇩ /hunt/hunt-signing.asc · ⇩ /hunt/epoch.asc · ⇩ /hunt/epoch-prev.asc

What this teaches. The real "canary" skill: verify a signature BEFORE reading the content, then compare versions over time. A canary only protects the person who verifies and tracks it — not the one who skims it.

Support