Proof-of-Serve | Hallmark

PROOF-OF-SERVE

Every read proves itself

Each response ships with a signed receipt. Honest nodes get paid; a wrong answer is caught and slashed on-chain. Enforced by the protocol — not a promise.

Account-Hash Proofs

Answers carry a hash of the underlying account state, bound to the slot it was read at.

Known-Answer Audits

Auditors probe nodes with queries whose truth is already known. A node's answer is checked against ground truth.

Signed Receipts

Every read is signed; anyone can check freshness and authenticity offline, with no round-trip.

Stake & Slashing

Operators post stake. Wrong answers are provable — and provably slashed on-chain.

THE RECEIPT

{
  "result": { "lamports": 4198320512, "slot": 296410233 },
  "slot": 296410233,
  "receipt": {
    "query": "getBalance:5tz…9aF",
    "answerDigest": "9f1c…ab",
    "slot": 296410233,
    "issuedAt": 1718900000000,
    "sig": "7c0a…ff"
  }
}

The signature covers a deterministic, key-sorted encoding. The verifier recomputes the exact bytes and checks the signature against Hallmark's published public key. No network round-trip, no trust in the responder.