Skip to content

v0.12.0

Choose a tag to compare

@benwoody benwoody released this 24 Sep 20:17
· 35 commits to main since this release
v0.12.0
20a38dd

thurin status says why a claim doesn't count

Instead of a library error, the claim line names the reason: ✗ key expired 2029-03-05, ✗ key revoked, ✗ key compromised, ✗ signing key expired, ✗ signing key revoked, ✗ not supported (DSA 2048), or ✗ doesn't verify. A verified key that expires within 30 days gets a warning: ⚠ key expires in 12 days (2027-03-06). The history marks a claim replaced by reattest as replaced → #2.

When a keystore on your machine holds the address, each line adds the fix, for example extend it (gpg --quick-set-expire), then thurin update-key. An expired key can be extended and the claim updated with no new signature.

--json carries the same: verification.kind, verification.at, and each claim's fate (active, revoked, or replaced).

Farcaster proofs need no key

Built on identity-kit 1.4.0 (up from 1.3.2), so Farcaster proofs are checked against a public Farcaster node (Quilibrium's, keyless) instead of Neynar. If you installed an earlier version, upgrading brings this in.

Also

  • thurin key create suggests your own name for the published name, not thurin.
  • keys.thurin.id and relay.thurin.id run this version.
  • Named on-chain from thurinlabs.eth: thurin record get thurinlabs.eth thurin.pointer

Verify this release: https://docs.thurin.id/#/guides/verify-release