ValidatorClient
Client for a validator's user-facing wallet API (.../api/validator) — the onboarding, faucet, and traffic-purchase operations a wallet app drives against its own validator, authenticated as the end user.
Every call sends a bearer token from accessTokenProvider; the validator derives the ledger user from the token's subject claim. On LocalNet that is the unsafe HS256 JWT the integration harness mints; against a real validator it is the user's OAuth access token.
Unlike ScanClient (public network index) and TransferRegistryClient (registry choice contexts), this API is validator-local: it only answers for users of the validator behind baseUrl.
Types
A created buy-traffic request, identified for status polling.
Where a buy-traffic request stands (buyTrafficStatus).
Onboarding state of the authenticated user on this validator.
Functions
Requests a synchronizer extra-traffic purchase (/v0/wallet/buy-traffic-requests), paid in Amulet from the authenticated user's wallet.
Where the buy-traffic request created under trackingId stands (/v0/wallet/buy-traffic-requests/{tracking_id}/status), or null if the validator knows no such request — not yet processed, or already beyond the wallet's transaction-log horizon.
Taps the faucet (/v0/wallet/tap): mints Amulet to the authenticated user's wallet party. Test networks only — DevNet and LocalNet validators expose the tap; on MainNet it fails.
The authenticated user's onboarding state (/v0/wallet/user-status).