@orangecheck/stamp-core / VerifyInput
Interface: VerifyInput
Defined in: stamp-core/src/types.ts:91
Properties
| Property | Type | Description | Defined in |
|---|---|---|---|
<a id="property-content"></a> content? | Uint8Array<ArrayBufferLike> | Optional: the content bytes. If present, verify() additionally checks that sha256(content) matches envelope.content.hash. | stamp-core/src/types.ts:97 |
<a id="property-envelope"></a> envelope | StampEnvelope | - | stamp-core/src/types.ts:92 |
<a id="property-skipsignatureverification"></a> skipSignatureVerification? | boolean | Skip the BIP-322 signature verification. Default false. Useful for test vectors where signatures are placeholders, or for preview UIs that re-verify separately. | stamp-core/src/types.ts:127 |
<a id="property-verifybip322"></a> verifyBip322? | (msg: string, signatureB64: string, address: string) => Promise<boolean> | Verifier for BIP-322. Plugged in by the caller because signature verification libraries differ across Node, browser, and CLI environments. | stamp-core/src/types.ts:102 |
<a id="property-verifyotsanchor"></a> verifyOtsAnchor? | (proofB64: string, blockHeight: number, blockHash: string, envelopeId: string) => Promise<boolean> | Optional hook for OTS anchor verification. If present and ots.status === "confirmed", the caller-supplied function walks the proof and returns true iff it chains to a real Bitcoin block header at the declared height. envelopeId is the 64-char hex envelope id (equals the 32-byte digest committed by the OTS proof, hex-encoded). Passing it explicitly lets the verifier avoid the broken "look up the digest from the block hash" dance the old adapter tried to do. The default behavior (anchor hook omitted) is to ACCEPT a confirmed envelope on shape alone — useful for preview UIs. Callers that attach legal or economic weight MUST supply this hook. | stamp-core/src/types.ts:117 |