ordspv
    Preparing search index...

    Interface FetchSatIdentityOptions

    interface FetchSatIdentityOptions {
        anchorSources?: string[];
        checkpoints?: Map<number, string>;
        esplora?: string[];
        fetchFn?: FetchFn;
        limits?: BackendLimitsInit;
        maxSteps?: number;
        minConfirmations?: number;
        minHeaderAgreement?: number;
        onAttempt?: OnAttempt;
        powLimitBits?: number | null;
        trustHeader?: (
            header: BlockHeader,
            height: number,
        ) => Promise<HeaderTrustReport>;
        witnessSection?: WitnessSectionMode;
    }
    Index
    anchorSources? checkpoints? esplora? fetchFn? limits? maxSteps? minConfirmations? minHeaderAgreement? onAttempt? powLimitBits? trustHeader? witnessSection?
    anchorSources?: string[]

    header attesters (default DEFAULT_ANCHOR_SOURCES); see HeaderTrustOptions

    checkpoints?: Map<number, string>
    esplora?: string[]
    fetchFn?: FetchFn
    limits?: BackendLimitsInit
    maxSteps?: number

    funding steps the walk will follow (default DEFAULT_MAX_STEPS)

    minConfirmations?: number
    minHeaderAgreement?: number

    see HeaderTrustOptions; defaults mirror the resolver

    onAttempt?: OnAttempt

    Called once per build attempt, before it runs, with the member leading it and what ended the attempt before. An attempt here is a whole walk, which on a deep ancestry is thousands of requests, so a caller that shows progress has to be told a rotation happened.

    powLimitBits?: number | null
    trustHeader?: (
        header: BlockHeader,
        height: number,
    ) => Promise<HeaderTrustReport>

    Anchor both endpoint headers instead of makeHeaderTrust. Throw to reject. The report's attests field is passed to the core verifier, so a hook that returns 'hash-at-height' there lets a terminal coinbase below the BIP34 boundary be accepted, and a rejection-only hook leaves such a bundle refused with CoinbaseHeightUnprovenError.

    witnessSection?: WitnessSectionMode

    Whether the reveal hop carries its wtxid proof. 'when-needed' (default) attaches it to multi-input reveals only, which is what verification requires and keeps single-input bundles byte-identical to before the option existed. 'always' attaches it to every reveal, at one raw block request, so the bundle verifies at indexProof: 'wtxid' and carries no executed-leaf residual.

    Settings
    Member Visibility

    On This Page
    Properties