Privacy cache

Privacy Coin Native APIs

Epic and Zano use native local wallet modules because their privacy models require more than a simple public address balance lookup.

EpicPrivacy cache
ZanoPrivacy cache
LocalPrivate keys stay local
Wallet API Local engines Upstream APIs Privacy cache
CoinLocal native componentExternal/network API useWhat stays local
ZanonativeCore.privacyLightWallet with zano-light engine.Altbase API scan/proxy data, Zano node RPC/index data through the server.Mnemonic-derived wallet state, spend preparation, private view/spend data, and decrypted cache contents.
Epic Cashnative/epic_core and Epic wallet libraries.Altbase API as Epic node URL in source, Epic node foreign API, and Epicbox WebSocket server for slate exchange.Epic wallet seed, local wallet database, output ownership, transaction creation, and finalized wallet state.

Encrypted Privacy Cache

The privacy cache is designed to speed up restores for Epic and Zano without giving the server plaintext wallet data.

  • The wallet derives a backup ID locally from the coin and mnemonic.
  • The wallet derives an encryption key locally with HKDF-SHA256.
  • The cache payload is encrypted locally with AES-256-GCM before upload.
  • The server receives only coin, backupId, and encryptedBlob.
  • The encrypted cache can include local wallet metadata such as address, balance snapshot, transactions, restore start height, scan height, and scan state, but only after local encryption.

What The API Does Not Do

  • It does not receive wallet mnemonics for normal balance, history, send, or update calls.
  • It does not receive private keys or WIF keys for UTXO, Quai, Epic, or Zano sends.
  • It does not sign normal wallet transactions on behalf of the user.
  • It does not need custody of user funds.
  • It does not expose production coin RPC credentials to the desktop app.