RAVEN. / receiptsRAVEN. / receiptsEvery Raven verdict is a machine-verifiable receipt. Not "looks safe" — but: this mint produced these findings, at this slot, under this engine version, with these gaps, signed by this key. Below: unedited responses from the live verifier. Note USDC reads risk — active issuer authorities are reported as what they are, even on blue chips.
Raven receipts are currently signed with ed25519 key rvk_c2997e90215279c2; the public key is served at /pubkey. Key IDs are explicit so agents can detect rotation. Receipts include engine version, replayHash, and officialAttestationHash, so past outputs remain auditable. If Raven rotates keys, old receipts remain verifiable under their original keyId. Raven does not claim quantum resistance today; future signing schemes arrive through a new keyId and verification domain (/key-policy.json).
Every receipt is tied to the keyId that signed it (today: rvk_c2997e90215279c2). Verify against the key published at /pubkey — and store the full receipt: keyId, signature algorithm, observed slot, engine version, replay hash, official attestation hash.
If Raven rotates keys later, old receipts remain verifiable against the key that signed them — agents should match keyId, not assume the newest key. Retired/revoked key semantics: /key-policy.json. Raven signs evidence; it does not predict price or give financial advice.
Store the full signed response. Index by mintAddress, observedSlot, engineVersion, verdict, keyId, replayHash, officialAttestationHash. Do not overwrite older receipts — a later receipt is new evidence, not replacement truth. Keep the receipt payload and verification metadata together (decentralized storage or agent memory alike); store coverage gaps exactly as returned. Full guidance: /receipt-storage.html · wire receipt schema (validates the receipt object itself): /receipt-wire-schema.json · storage envelope schema: /receipt-schema.json · policy: /receipt-memory-policy.md.
Optional evidence caution: poolAddress and metadataAddress are optional inputs. When missing, the corresponding surfaces become coverage gaps — Raven does not infer liquidity quality without pool evidence, never converts liquidity evidence into price claims, and never treats a missing check as a pass. Re-verify stale receipts before material actions (decision policy).
1. Fetch the key: GET https://raven-hosted-verifier.onrender.com/pubkey → rvk_c2997e90215279c2, domain raven-official-attestation.
2. Recompute replayHash from the response fields via canonical JSON (recipe + exact preimage example in the public test vector).
3. Verify the ed25519 signature over domain || officialAttestationHash.
4. Re-run the same request: same slot evidence → byte-identical findings. Full security model →
Raven verifies on-chain evidence. It does not predict price or guarantee safety.