Bitvora primary sources — 2026-05-03

Project status in this pass

  • No canonical standalone Bitvora whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official site, developer docs, the canonical Go SDK README, the Lightning-for-exchanges solution page, the Zapvertiser tutorial, and the public GitHub organization metadata.
  • The project is best understood as a developer wallet and Bitcoin payments control plane rather than as a simple wallet SDK or consumer wallet brand.

Primary-source snapshots

1) Official homepage

  • URL: https://bitvora.com/
  • Key excerpt:
    • The homepage calls Bitvora “The Developer’s Bitcoin Wallet.”
    • It says developers can build faster with less code because Bitvora’s SDKs handle the complex Bitcoin operations.
    • The homepage also foregrounds instant settlement and a multi-language SDK posture.

2) Developer SDK docs

  • URL: https://developers.bitvora.com/docs/sdks/go
  • Key excerpt:
    • The SDK docs show Bitvora clients retrieving balances and transactions.
    • They also show withdrawals to a chain address, Lightning invoice, or Lightning address.
    • The same page shows creation of Lightning invoices, Lightning addresses, and onchain deposit addresses.

3) Canonical Go SDK README

  • URL: https://raw.githubusercontent.com/bitvora/go-bitvora/master/README.md
  • Key excerpt:
    • The README says the SDK lets developers manage Bitcoin deposits and withdrawals, create Lightning invoices and addresses, and retrieve balance and transaction information.
    • It includes concrete examples for withdrawal fee estimation, invoice creation, address creation, and deposit / withdrawal lookups.

4) Exchange integration page

5) Tutorial surface

  • URL: https://developers.bitvora.com/blog/zapvertiser-bot
  • Key excerpt:
    • The tutorial walks through building a Nostr Zap Bot using the Bitvora Go SDK.
    • It shows a bot discovering Lightning addresses from Nostr profile metadata, retrieving LNURL callbacks, and paying resulting invoices through the Bitvora API.
    • That is strong evidence that Bitvora’s API is being positioned as programmable wallet infrastructure for social-payment automation, not just merchant checkout.

6) Public GitHub organization metadata

  • URL: https://api.github.com/orgs/bitvora
  • Key excerpt:
    • The public GitHub org metadata identifies the organization as “Bitvora Inc,” links back to https://bitvora.com, and shows a non-trivial public repository footprint.
    • That reinforces the impression of an actively developer-facing platform rather than a docs-only landing page.

Working conclusion

Bitvora is best cataloged as Bitcoin wallet and settlement infrastructure for developers. The deciding evidence in this pass was the combined support for balances, transaction history, invoices, Lightning addresses, onchain addresses, flexible withdrawal destinations, exchange-integration positioning, and a tutorial that repurposes the same API for automated Nostr zaps.