ordspv
    Preparing search index...

    Function buildSatGenealogyBundle

    • Build a sat genealogy bundle for an inscription. The result is UNVERIFIED; callers must run verifySatGenealogy (fetchSatIdentity does both).

      Parameters

      • inscriptionId: string
      • backend: AnchorBackend
      • options: {
            maxSteps?: number;
            powLimitBits?: number | null;
            revealSource?: AnchorBackend;
            witnessBackends?: AnchorBackend[];
            witnessSection?: WitnessSectionMode;
        } = {}
        • OptionalmaxSteps?: number
        • OptionalpowLimitBits?: number | null

          Proof-of-work floor for both endpoint headers, in checkPowLimit's convention: undefined is the mainnet limit and null disables it. The caller's verification applies the same floor, so passing it here is what lets a header under it cost one attempt rather than a whole walk.

        • OptionalrevealSource?: AnchorBackend

          The backend the walk's deciding requests are made against: the reveal's tx hex, its status, its merkle proof, and the terminal coinbase's status, whose answers decide every domain refusal the walk can raise. Everything checked against bytes a txid already fixes (prev txs, headers, block info, the funding walk) stays on backend, where pool fallover cannot change a domain decision, and the raw block keeps its deliberate rotation through witnessBackends. A failure of one of the four requests throws RevealSourceError so the caller can tell one member's failure from pool exhaustion. Defaults to backend, unwrapped.

        • OptionalwitnessBackends?: AnchorBackend[]
        • OptionalwitnessSection?: WitnessSectionMode

      Returns Promise<BuildSatGenealogyResult>