Private service API
The service capabilities required behind wallet compatibility.
Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.
Proposed capabilities
| Capability | Required behavior |
|---|---|
| Initialize privacy keys | Derive viewing material after an explicit signing request |
| Read receiving key | Resolve registered recipient encryption material |
| Check access | Verify credential permission for an account |
| Read raw private balance | Distinguish total balance from fee-reserved balance |
| List private history | Reconstruct incoming and outgoing changes |
| Estimate operation cost | Return fee assumptions and expiration context |
Authentication boundary
The reference proxy isolates data using an access token and wallet address, with a protected cookie or credential-bearing RPC URL. Jammer must define a versioned service contract before exposing an equivalent API.
URL credentials can leak through logs, analytics, screenshots, or browser history. Redaction, short-lived sessions where practical, origin checks, and server-side authorization are required. CORS is not an authorization system.
History semantics
A private history record should distinguish the internal action ID from the base-chain transaction hash. Asset deltas, fee deltas, block metadata, and confirmation state are separate fields.
Receiving-key registration is an on-chain action and is not equivalent to local key generation. An API must preserve that distinction.
Release status
No Jammer RPC namespace, SDK package, API token format, or public endpoint is finalized. Do not send signatures or private keys to guessed endpoints.