Type Alias GasDecision

GasDecision:
    | { limit: bigint; source: "explicit" }
    | {
        estimate: bigint;
        limit: bigint;
        marginPercent: number;
        source: "estimate";
    }
    | { error: Error; limit: undefined; source: "fallback" }

How the gas limit on a send was chosen (MK-037).

Why this is on the result and not only in a log line. MK-035 added a measured margin to every write. MK-037 was that the margin could vanish on any send, for any reason, and the only trace was a console.warn: a consumer cannot assert on it, cannot route it to their own telemetry, and does not see it in a console they have filtered. The degradation is real (the send goes out with the pre-MK-035 behavior, which is the behavior that produced the reverts), so it has to be legible through the surface the SDK actually returns.

Branch on source when you care. Ignore the field entirely when you do not; it is additive.

Type declaration

  • { limit: bigint; source: "explicit" }

    The caller passed an explicit gas. Neither the estimate nor the margin was consulted.

  • { estimate: bigint; limit: bigint; marginPercent: number; source: "estimate" }

    The estimate succeeded and the margin was applied to it. The normal case.

  • { error: Error; limit: undefined; source: "fallback" }

    The estimate failed, so the send carried NO gas field and the wallet client estimated internally: the pre-MK-035 behavior, with no margin at all.

    error is what mapRevert made of the failure, so it is the same typed MusdError taxonomy every other error on this path already uses, not a raw transport object.

Settings

Member Visibility