Private keys stay local
All 35 supported networks derive their signing keys locally. Private keys are not sent to the Altbase public API.
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.
All 35 supported networks derive their signing keys locally. Private keys are not sent to the Altbase public API.
For normal sends, the wallet builds and signs locally. The API receives only a signed raw transaction or a serialized signed transaction envelope for broadcast.
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.
EVM, Solana and Tron connect directly to PublicNode. Address derivation and signing stay local; the Altbase backend supplies prices and module metadata.
| Module | Networks | Public data requests | Local operations |
|---|---|---|---|
| EVM | Ethereum, BNB Smart Chain, Polygon, Arbitrum One | eth_getBalance, eth_call, eth_getLogs, eth_estimateGas, eth_getTransactionReceipt | Local keys, ERC-20 amounts, fee preparation and transaction signing. |
| Solana | Solana | getBalance, getAccountInfo, getTokenAccountsByOwner, simulateTransaction | Local keys, SPL token handling and transaction signing. |
| Tron | Tron | /wallet/getaccount, /walletsolidity/getaccount, /wallet/triggerconstantcontract | Local keys, TRC token handling, resource estimates and transaction signing. |
Public RPC indexing and history can be incomplete. Tokens can be added by contract or mint; icons download on demand and spam stays hidden until enabled.