Bitvora

  • Name: Bitvora
  • URL: https://bitvora.com/
  • Category: Bitcoin wallet API / Lightning-and-onchain payments infrastructure / developer wallet control plane
  • Tags: bitcoin-ecosystem
  • Summary: Bitvora is a developer wallet backend for Bitcoin and Lightning. The point is programmable balance, invoice, address, and withdrawal control through one hosted API, not a consumer wallet brand.
  • What it does:
    • Gives developers an API-key wallet account and SDK-driven access to Bitvora on mainnet and signet environments
    • Exposes account balance and transaction-history endpoints for wallet operations and reporting
    • Supports Bitcoin withdrawals to an onchain address, a Lightning invoice, or a Lightning address, with fee-estimation before sending
    • Supports creation of Lightning invoices, Lightning addresses, and new onchain deposit addresses through the API
    • Publishes multi-language SDK and integration docs aimed at letting developers embed Bitcoin and Lightning flows in applications with less low-level wallet code
    • Markets Lightning-network integration for exchanges and shows Nostr-zap automation patterns built on top of the same wallet API
  • Key claims:
    • The homepage calls Bitvora “The Developer’s Bitcoin Wallet” and emphasizes multi-language SDKs so builders can focus on application logic instead of low-level Bitcoin operations
    • The Go SDK docs and README say Bitvora can retrieve balances and transactions, create Lightning invoices and Lightning addresses, create onchain deposit addresses, and withdraw to a chain address, Lightning invoice, or Lightning address
    • The Go SDK examples show fee estimation before withdrawal, which suggests Bitvora is exposing a fuller wallet-operations surface rather than only a payment-send endpoint
    • The Lightning Network Integration page says Bitvora offers a simple Lightning integration path for exchanges and frames Lightning around instant settlement and lower fees
    • The Zapvertiser tutorial shows Bitvora being used programmatically inside a Nostr zap bot that discovers Lightning addresses via Nostr metadata, retrieves LNURL callbacks, and pays the resulting invoice through the Bitvora API
    • The public GitHub organization exposes a broader developer footprint around the wallet API, with public repos and SDK work consistent with the site’s developer-wallet positioning
  • Whitepaper: No canonical standalone Bitvora whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, developer docs, SDK README, exchange-integration page, tutorial content, and public GitHub organization metadata; see ../whitepapers/bitvora-primary-sources-2026-05-03.md.
  • Sources:

Internal linkages

  • Stronger Lightning connectivity and backend anchors: alby and greenlight

  • Merchant-stack contrast when the real job is invoicing rather than wallet primitives: btcpay-server

  • Last reviewed: 2026-06-02 UTC