OptionalmaxMaximum OP_RETURN outputs the server accepts per transaction.
undefined when not advertised — a server that omits the field and one
that sends 0 both mean "no limit stated". Never 0n, which would read
as a server that forbids them outright.
OptionalmaxWeight budget an ark transaction must stay under; the server answers
TX_TOO_LARGE past it.
undefined when not advertised — a server that omits the field and one
that sends 0 both mean "no limit stated". Never 0n, which would read
as a server that accepts no transaction at all.
OptionalscheduledMaximum boarding input amount.
Maximum virtual output amount.
OptionalvtxoSweep delay the operator advertises for the shared batch output.
undefined when not advertised — never coerce to 0n, which would
satisfy any floor comparison.
The Arkade server's advertised configuration — the
/v1/inforesponse.Naming/placement vs the NArk reference (AGENTS.md asks divergences to be noted): NArk calls this
ArkServerInfo, reads it viaGetServerInfoAsyncon the transport, and caches it in a dedicatedCachingClientTransport. This SDK names it for the product (ArkadeInfo, per #734) and hangs the read off the wallet (getArkadeInfo()), because here the wallet is the one object every consumer already holds and — in the service-worker model — the only side that has a transport at all; the page has no provider to hang it on. TheCachingClientTransport-style memo lives at this layer instead, asCachingArkProvider.