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 small hosted Bitcoin wallet API. The point is programmable balance, invoice, address, and withdrawal control through one vendor backend, not a consumer wallet brand and not a category anchor.
• 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 is enough to treat Bitvora as a real wallet-operations API rather than a one-endpoint payment sender
  • The Lightning Network Integration page says Bitvora offers a simple Lightning integration path for exchanges and frames Lightning around instant settlement and lower fees, which reinforces that the real product is hosted wallet plumbing for apps, not wallet UX
  • 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:
  • https://bitvora.com/
  • https://developers.bitvora.com/docs/sdks/go
  • https://raw.githubusercontent.com/bitvora/go-bitvora/master/README.md
  • https://bitvora.com/solutions/lightning-network-integration
  • https://developers.bitvora.com/blog/zapvertiser-bot
  • https://api.github.com/orgs/bitvora

Internal linkages

• Stronger wallet-connectivity and hosted-control-plane reads: alby and secret-key-labs.
• Data-and-event-heavy Bitcoin-platform contrast: hiro.

Control surface

• Practical authority sits in API-key admission, hosted wallet defaults, invoice and address generation policy, withdrawal permissions, and how much of the Lightning and onchain stack the developer is willing to let Bitvora abstract away.

• Read it as small hosted wallet plumbing. Useful, but still well below the stronger Bitcoin access and connectivity notes.

• Last reviewed: 2026-06-15 UTC