ScanClient
Read layer over a Super Validator's Scan API (.../api/scan).
Covers the reads a wallet needs from the network's public index: the DSO party, ANS name resolution (name-based sending), aggregated holdings from scan's server-side ACS snapshots, the AmuletRules fee configuration, open mining rounds (amulet price), and per-member synchronizer traffic status.
Note the base URL differs from TransferRegistryClient's: registry endpoints mount at the vhost root (/registry/...), scan endpoints under /api/scan.
Types
Aggregate Amulet totals for one owner party in a scan ACS snapshot.
Aggregated holdings answered from one server-side ACS snapshot.
A sequencer member's extra-traffic accounting, all in bytes. Purchased traffic becomes spendable once the sequencer incorporates it: totalLimitBytes catching up to totalPurchasedBytes means all purchases are live (either can briefly lead the other, as the two numbers come from the sequencer and scan's ledger ingestion respectively).
Functions
The AmuletRules configuration effective at asOf (/v0/amulet-rules): the USD transfer-fee schedule, synchronizer traffic pricing, and the active synchronizer id — the reads that feed TransferFeeEstimator and ValidatorClient.buyTraffic.
The party id of the DSO — the instrument admin for Amulet.
Server-side aggregated Amulet balances for ownerPartyIds (/v1/holdings/summary) — scan folds its ACS snapshot so apps don't fold the full ACS client-side.
The network's latest synchronizer-migration id (/v0/migrations/last) — the id scan's ACS snapshots are addressed by. holdingsSummary resolves this automatically; fetch it yourself only to pin the id across many calls.
Lists ANS entries, optionally filtered by a name prefix.
Resolves an ANS name to its entry, or null if unregistered.
The extra-traffic status of one sequencer member (/v0/domains/{id}/members/{member}/traffic-status) — the read that shows a ValidatorClient.buyTraffic purchase landing.
The currently open mining rounds (/v0/open-and-issuing-mining-rounds), in ascending round order. Each round carries the USD amulet price that taps and fee conversions use. Note the list includes rounds whose OpenMiningRound.opensAt is still in the future — pick the round a submission would execute against with latestUsable.
The participant hosting partyId on synchronizerId (/v0/domains/{id}/parties/{party}/participant-id), as a sequencer member id (PAR::name::fingerprint) — the memberId that memberTrafficStatus expects. Null if scan doesn't know the party.
The active preapproval for partyId, or null if none — the signal that transfers to this party settle in one step ("direct") instead of the two-step offer flow.