Cowrie Research

bitcoin-dev-kit-primary-sources-2026-04-30

3 min read

Bitcoin Dev Kit primary sources — 2026-04-30

Project status in this pass

  • No canonical standalone whitepaper or litepaper surfaced.
  • The clearest current source of truth is the official site/foundation materials plus the public GitHub repo and README corpus.

Primary-source snapshots

1) Main site

  • URL: https://bitcoindevkit.org/
  • Key excerpt:
    • The homepage describes BDK as “a suite of software libraries that allow you to build secure, feature-rich, and cross-platform bitcoin-based applications.”
  • Notes:
    • The site structure points to foundation, adoption, and blog material rather than a single protocol paper, which is already a clue that BDK is a toolchain ecosystem, not a single protocol product.

2) Foundation about page

  • URL: https://bitcoindevkit.org/foundation/about/
  • Key excerpt:
    • The BDK Foundation describes itself as a US 501(c)(6) nonprofit promoting the Bitcoin software development industry through stewardship of free and open-source tools such as the BDK suite of libraries.
    • It also says foundation-funded work is required to be FOSS and published publicly.
  • Notes:
    • This page is useful for understanding the governance/stewardship layer around the tooling stack.

3) Adoption directory

  • URL: https://bitcoindevkit.org/adoption/all/
  • Notes:
    • The public “Built With BDK” list includes products such as AnchorWatch, Proton Wallet, 10101, Alby, Bark, Bitkey, Caravan, Cove Wallet, Fedimint, Galoy, Liana, mempool.space, MetaMask Bitcoin support, and many others.
    • This is unusually strong first-party evidence that BDK functions as shared production infrastructure rather than a niche library.

4) Main bdk repository README

  • URL: https://raw.githubusercontent.com/bitcoindevkit/bdk/master/README.md
  • Key excerpt:
    • Describes BDK as “a suite of libraries for building modern, lightweight, descriptor-based wallets written in Rust!”
    • Breaks the workspace into crates for chain data, core structures, Esplora, Electrum, Bitcoin Core RPC, and file-store persistence.
  • Notes:
    • This README is the clearest compact description of the lower-level architecture.

5) bdk_wallet README

  • URL: https://raw.githubusercontent.com/bitcoindevkit/bdk_wallet/master/README.md
  • Key excerpt:
    • Says bdk_wallet provides a high-level descriptor-based wallet API for Bitcoin applications.
    • Documents wallet syncing through Esplora, Electrum, and Bitcoin Core RPC sources plus persistence support.
  • Notes:
    • Important for distinguishing the higher-level wallet API from the lower-level mechanism crates in bdk.

6) bdk-ffi README

  • URL: https://raw.githubusercontent.com/bitcoindevkit/bdk-ffi/master/README.md
  • Key excerpt:
    • States the repo creates exportable libraries using uniffi-rs for the Rust-based bdk_wallet library.
    • Names packaged targets for Kotlin/Android and Swift/iOS/macOS, while also noting separate bindings projects such as JVM and Python.
  • Notes:
    • This is a key source for understanding BDK as cross-platform application infrastructure rather than only a Rust crate family.

7) JVM and Python bindings READMEs

8) “Why Do We Build Bindings?” blog post

  • URL: https://bitcoindevkit.org/blog/why-bindings/
  • Key excerpt:
    • Explains that BDK wants to serve not only bitcoin-first wallets but also games, chat apps, content apps, and other products that want Bitcoin capabilities without changing their whole stack or hiring dedicated Bitcoin specialists.
    • Explains tradeoffs behind exposing a unified cross-language API built over multiple Rust libraries.
  • Notes:
    • This post is unusually good evidence of product intent and target users.

Working conclusion

Bitcoin Dev Kit is best cataloged as open-source Bitcoin wallet/application infrastructure: a foundation-steered SDK suite with lower-level chain/data crates, a higher-level descriptor-based wallet API, cross-language bindings, and visible production adoption. In this pass, the real primary-source surface was the site + foundation + repo corpus, not a whitepaper.

Graph View