Developer

Altbase Wallet API Transparency

This page explains the APIs used by the Altbase non-custodial wallet and the Altbase API server. It is based on the wallet source code and is intended for website and GitHub transparency.

2026-06-13Reviewed source date
API v1Wallet API base
LocalNon-custodial wallet
Privacy Summary

Private operations stay on the device.

Private keys stay local

The wallet derives addresses, private keys, WIF keys, Quai keys, Epic keys, and Zano keys locally. Mnemonics and private keys are not sent to the Altbase public API.

Signed transactions are broadcast

For normal sends, the wallet builds and signs the transaction locally, then sends only the signed raw transaction hex to the broadcast endpoint.

Addresses are queried

Balance, UTXO, history, and snapshot endpoints receive public wallet addresses. Those addresses are public blockchain data, but API access can associate requests with network metadata such as IP address.

Privacy coins use local native wallet code. When encrypted privacy cache is enabled, the server stores an encrypted blob only. Encryption keys are derived locally from the mnemonic; the server does not receive plaintext wallet cache.