What is checked
1 · Signature authenticity. The signer is established from the signed message alone. For an ordinary wallet that means ECDSA recovery: the private key controlling that lender address really did sign this exact payload, and the submitter cannot forge or alter it after the fact. A Safe or other contract wallet has no key to recover from, so the wallet itself is asked whether it authorized the payload's digest (EIP-1271) — the same check made when the claim was submitted.
2 · Domain binding. An EIP-712 signature is bound to the domain Wildcat Claims v1 on this network's chain id, proving the attestation was made for this claim process and is not a signature lifted from elsewhere or replayed from another chain. A personal_sign proof carries no domain, so this layer is reported as not applicable rather than as a pass.
3 · The undertaking. The signature commits to the SHA-256 of the Qualifying Lender undertaking and its definitions. We recompute that digest from the published text and confirm it matches, and that the signer affirmed it — so what was agreed to is fixed beyond later alteration, not merely asserted by a flag.
4 · On-chain replay. The claim commits a block number (asOfBlock). We re-read the market and the signer's balance at that block on the Wildcat archive node and confirm the penalized-days figure matches and the signer was owed exactly the attested amount. Whether the market was in default at that block is read back and reported alongside, but it does not decide the verdict: eligibility turns on holding a position, so the verifier holds a proof to the same standard the claim process applies, no more.
How it's done
Layers 1–3 are pure cryptography and arithmetic — no trust in whoever submitted the file, beyond one read of the signing wallet's own contract for a Safe. Layer 4 is deterministic: because the figures are pinned to a specific block, anyone with an archive node reads back the identical numbers. Nothing here depends on the applicant being honest.
What a “valid” result means
The wallet holder genuinely attested these facts, the attestation belongs to this process, and the facts were true on-chain at the committed block — sufficient to treat it as impacted-lender evidence. A mismatch means the signature is authentic but the committed figures no longer match the chain (e.g. a doctored payload, or a proof produced in DEBUG mode).