Class ArkadeIntentsOptions

Namespace

NArk.ArkadeIntents

Assembly

NArk.ArkadeIntents.dll

Settings shared by both Arkade intent corridors.

public sealed class ArkadeIntentsOptions

Inheritance

object

ArkadeIntentsOptions

Inherited Members

object.Equals(object)

object.Equals(object, object)

object.GetHashCode()

object.GetType()

object.ReferenceEquals(object, object)

object.ToString()

Properties

EmulatorPubkeyOverride

Co-sign covenants with this key instead of the network's pinned one. 33-byte compressed hex.

public string? EmulatorPubkeyOverride { get; set; }

Property Value

string

Remarks

Left unset — the normal case — the co-signer comes from DefaultFor(string?), which is a property of the network rather than of whatever host answers. Set, every covenant this SDK builds can be completed by whoever holds the supplied key and by nobody else, so it is a statement that you trust that operator in place of the network's.

It exists mainly for a key rotation this SDK has not shipped a constant for yet, and secondarily for a self-hosted emulator or a local stack. See Resolve(string?, string?).

MaxPayAmountSats

Refuse a receive quote that bills the payer more than this, in sats. Unset means no ceiling.

public long? MaxPayAmountSats { get; set; }

Property Value

long?

Remarks

A receive request pins one leg and leaves the other to the solver. Pinning what the payer is billed fixes it exactly and needs no ceiling; pinning what lands on Arkade leaves the payer's side as the solver's free variable, and this is the only thing bounding it.

Nothing is at risk either way — a quote is refused before an invoice reaches anyone, and the amount that lands is checked separately. What a ceiling prevents is handing a customer an invoice for more than the order they approved, which their wallet may refuse outright.

OnchainClaimConfirmations

Confirmations to require on an off-board's L1 funding before claiming it. Defaults to the most any solver may ask for.

public int OnchainClaimConfirmations { get; set; }

Property Value

int

Remarks

The quoted count is not persisted, so the automatic claim pass cannot read it back — this is what that pass waits for instead. The default is the corridor's ceiling, which is longer than most solvers ask: of the two ways to be wrong about a confirmation count, waiting too long costs time and waiting too little costs the trade.

A caller driving the claim itself passes its own count and never reads this.