Upstream APIs

Altbase API Server Routes

The API server exposes normalized routes to the wallet and translates them into coin-specific node, explorer, or index requests.

RPCUpstream APIs
CachePrice Data APIs
NoSecret wallet data sent?
Server route groupResponsibilityNotes
/api/v1/:coin/networkNetwork height, chain state, mempool status, and sync status.Backed by coin node RPC, Blockbook, Quai RPC, or privacy node adapters.
/api/v1/:coin/address/*Balance, UTXOs, history, and mempool activity for public addresses.Responses are cached briefly to reduce node load. Force-refresh is supported for balance and snapshot flows.
/api/v1/:coin/tx/broadcastSubmits signed raw transactions to the network.The server does not sign wallet transactions.
/api/v1/:coin/account/tx-contextReturns account-chain transaction context.Used mainly by Quai for nonce, gas, chain ID, and gas estimation.
/api/v1/wallet/snapshotBatch endpoint for startup and refresh data.Combines network, balances, and history for multiple coins and addresses.
/api/v1/privacy/*Encrypted cache storage and privacy scan/broadcast support.Plain mnemonics and private keys are not accepted by these routes.
/api/v1/app/updateDesktop app update metadata.The wallet directs users to the official download page.

The server has CORS enabled for JSON API responses, applies request size limits, rate limits clients by IP, and uses short cache TTLs for high-frequency blockchain data.

Server To Coin Nodes And Explorers

These upstream APIs are called by the Altbase server, not directly by the desktop wallet in normal use. Exact production node URLs and RPC credentials are configured on the server and are not shipped in the client source.

AdapterUpstream API typeMethods or paths usedPurpose
bitcoin-rpcBitcoin Core / Dash-like JSON-RPC over HTTP(S) with server-side Basic Auth.getblockchaininfo, getnetworkinfo, getmempoolinfo, getaddressbalance, getaddressutxos, getaddresstxids, scantxoutset, sendrawtransaction, validateaddress, estimatesmartfee.UTXO coin network, address, history, fee, validation, and broadcast data.
blockbookBlockbook-compatible REST API./, /tx/:txid, /address/:address, /utxo/:address, /sendtx/:hex, /estimatefee/:blocks.Blockbook coins such as Neoxa and Pearl.
quai-rpcQuai JSON-RPC plus Quaiscan-compatible explorer endpoints.quai_blockNumber, quai_getBalance, quai_getTransactionCount, quai_sendRawTransaction, /api/v2/addresses/:address, /api/v2/addresses/:address/transactions.Quai balance, gas, nonce, broadcast, and history.
remote-apiAnother Altbase-compatible API base URL.Forwards normalized routes such as network, address balance, address UTXOs, address history, broadcast, fee estimate, and privacy routes.Allows a coin to be served by a separate compatible backend.
zano-nodeZano node JSON-RPC and compact light index.getinfo, get_tx_details, get_blocks_details, plus raw proxy paths used by the local light wallet.Zano network status and scan data for the local native privacy wallet.
epic-nodeEpic node HTTP API./v1/status, /v2/foreign, and related owner/foreign proxy routes when configured.Epic network status and node interaction for the local native Epic wallet.

Price Data APIs

The desktop wallet requests prices from the Altbase API only. The server fetches prices from external providers, caches them, and returns a normalized result to the wallet.

ProviderEndpoint pattern in sourceCoins mapped in sourcePurpose
LiveCoinWatchPOST https://api.livecoinwatch.com/coins/singleBC2, BCH2, FIRO, PEPE, Kerrigan, SCASH, NEOX, TRC, JKC, RTM, QUAIPrimary USD market price source for many listed coins.
NonKYChttps://nonkyc.io/api/v2/ticker/{pair}CAP, EPIC, ZANOPair ticker source for coins traded there.
NestExhttps://trade.nestex.one/api/cg/tickers/{pair}LC2LitecoinII market price source.
SafeTradehttps://safe.trade/api/v2/peatio/public/markets/{pair}/tickersPRLPearl market price source.
CoinPaprikahttps://api.coinpaprika.com/v1/coins/{coinId}/marketsPRL fallbackFallback market data for Pearl when configured.
CoinGeckohttps://api.coingecko.com/api/v3/simple/priceQUAI fallbackFallback USD price for Quai.

Market API keys, when required, are configured on the server. They are not included in the desktop wallet.

Public Links And Explorers

The source also contains public website and explorer links used for downloads, support, legal pages, or opening transactions and addresses outside the wallet.

URLUsed for
https://altbase.io/downloadOfficial download page shown by the app update flow.
https://altbase.io/downloadsServer-side default base for published desktop update files.
https://altbase.ioPublic website link shown in wallet settings.
https://altbase.io/supportSupport link shown in wallet settings.
https://altbase.io/termsTerms link shown in wallet settings.
https://explorer.bitcoin2.orgBitcoin2 explorer link.
https://explorer.firo.orgFiro explorer link.
https://pepeblocks.comPepecoin explorer link.
https://quaiscan.ioQuai explorer and transaction history fallback source.
https://blockbook.pearlresearch.aiPearl Blockbook/explorer source.

Source Files Reviewed

The API behavior above is based on these source files:

  • src/services/coinApiService.ts
  • src/services/appUpdateService.ts
  • src/services/walletSnapshotService.ts
  • src/services/coinTxService.ts
  • src/services/quaiWalletService.ts
  • src/services/privacyCacheService.ts
  • src/services/nativeCoreService.ts
  • src/services/coinService.ts
  • src/wallet-engines/registry.ts
  • src/wallet-engines/utxo/utxoEngine.ts
  • src/wallet-engines/account/quaiEngine.ts
  • src/wallet-engines/privacy/privacyEngine.ts
  • server/gateway.cjs
  • server/config/default.cjs
  • server/adapters/index.cjs
  • server/adapters/bitcoinFork.cjs
  • server/adapters/blockbook.cjs
  • server/adapters/remoteApi.cjs
  • server/adapters/quaiRpc.cjs
  • server/adapters/zanoNode.cjs
  • server/adapters/epicNode.cjs
  • server/lib/priceFeed.cjs
  • server/lib/rpc.cjs
  • server/lib/utxoReadProfiles.cjs
  • server/lib/zanoLightIndex.cjs
  • native/core/src/privacy_light_wallet.cpp
  • native/epic_core/src/lib.rs
  • native/vendor/epic_wallet_src/impls/src/adapters/epicbox.rs

Deployment-specific production RPC URLs, node credentials, and API keys are intentionally not listed here because they are loaded from server configuration files and should not be published.