Wallet RPC

A proposed Ethereum JSON-RPC compatibility surface, not a live endpoint.

Protocol behavior is proposed. This release is an interface preview; no funds or wallet signatures are accepted.

Compatibility mapping

Method	Privacy-aware behavior
eth_chainId	Return the virtual network identity
eth_sendTransaction / eth_sendRawTransaction	Interpret supported signed intents and start shielded execution
eth_getBalance	Return authorized shielded native balance
eth_call: balanceOf	Resolve shielded ERC-20 balance for an authorized account
eth_getTransactionCount	Return a nonce consistent with private execution state
eth_estimateGas	Estimate the supported shielded action
eth_getTransactionByHash / Receipt	Map the private action to settlement status
eth_syncing	Expose scanner and registry synchronization
eth_blockNumber / eth_gasPrice	Read appropriate base-chain data

Example request

// Standard JSON-RPC shape; no Jammer endpoint is live.
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_getBalance",
  "params": ["<authorized-address>", "latest"]
}

Unsupported actions

The proxy must not imply that arbitrary EVM calls become private. Unsupported methods and calldata need explicit handling: safe public reads can be forwarded, while unsupported value-moving actions should fail with a clear error.

Log, receipt, nonce, and balance behavior can differ from a normal Ethereum node. Integrations need method-level conformance tests rather than a blanket “EVM compatible” assumption.

TECHNICAL REFERENCESRPC method reference

PreviousFees & finality Next Private service API

JAMMER / DOCUMENTATION DESIGN REVISION 0.1