ordspv
    Preparing search index...

    Interface GenealogyVerifyOptions

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

    Hierarchy (View Summary)

    Index
    expectedInscriptionId?: string

    The inscription id the caller asked for, read by verifyCustodyBundle and by verifySatGenealogy, which inherits these options. A bundle names the inscription it proves, and every other check 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. verifyAnchoredHop takes these options too and ignores this one: a hop carries no claim of its own to bind.

    maxSteps?: number

    verifier-side step bound (DoS guard for hostile bundles); default 10000

    powLimitBits?: number | null

    Compact-bits proof-of-work floor applied to every hop 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 each hop's header to a trusted view of the chain; throw to reject.

    The return value states what the hook checked. 'hash-at-height' asserts that this block hash IS the chain's hash at this height, which binds the header to the height and is what a sub-BIP34 coinbase height rests on (see CoinbaseHeightUnprovenError). Returning nothing keeps the hook rejection-only: it may reject whatever it likes by throwing, and a verifier reads no positive assertion out of its silence.