ordspv
    Preparing search index...

    Interface VerifyOptions

    interface VerifyOptions {
        expectedInscriptionId?: string;
        powLimitBits?: number | null;
        trustHeader?: (header: BlockHeader, height: number) => HeaderAttestation;
    }
    Index
    expectedInscriptionId?: string

    The inscription id the caller asked for. A bundle names the inscription it proves, and every other check in this function reads that claim rather than testing it, so a verification that omits this option establishes that the bundle is internally consistent and establishes nothing about whose inscription it is. A caller that fetched the bundle for a particular id supplies it here and the mismatch is refused; a caller inspecting a bundle it did not request leaves it out. Case is normalized before the comparison, so an id that survived URI case folding still matches.

    powLimitBits?: number | null

    Compact-bits proof-of-work floor applied to the bundle's header before its own PoW check counts for anything. Defaults to the mainnet limit (0x1d00ffff); pass another chain's limit, or null to disable it.

    trustHeader?: (header: BlockHeader, height: number) => HeaderAttestation

    Anchor the header to a trusted view of the chain (checkpoints, multi-source tip cross-check, header sync...). Throw to reject. When omitted the caller accepts embedded-PoW-only anchoring (NOT recommended for adversarial settings: a single header's work is cheap relative to valuable content).

    Returning 'hash-at-height' asserts that this block hash is the chain's hash at this height, which binds the header to the height. Returning nothing keeps the hook rejection-only, which is all this verifier needs: content proofs read no height out of the hook. verifySatGenealogy does, and refuses a sub-BIP34 coinbase height without the assertion.