thunderbiscuit
May 7, 2024
This article explores the reasons why the Bitcoin Dev Kit Foundation supports a number of language bindings libraries as part of its core offering, and the challenges and decision tradeoffs we face along the way.
thunderbiscuit
Jun 2, 2023
tldr; we can't produce and maintain bindings for all Rust crates we get requests for, but we are working to help others build their own bindings by (1) making our architecture composable and reusable, and (2) building strong examples and documentation on how to do it for other crates.
Alekos Filini
Oct 3, 2022
Over the past few months the work on [bdk_core] quietly continued behind the scenes, and as the time went on it started expanding beyond the scope of just improving the syncing mechanism of BDK. Being a new fresh project it allowed for iterating much faster, and we soon realized we could make large improvements to the general architecture of BDK to fix many of the issues and shortcomings found over time.
bdk_core: a new architecture for the Bitcoin Dev Kit Lloyd Fournier
May 9, 2022
The Bitcoin Devkit (BDK) lets you do a lot of useful things through convenient high level
abstractions. It works great when these abstractions map nicely onto what you are trying to do. My
goal is to develop a new bdk_core library for when they don't. I want bdk_core to expose all the
useful mechanisms that BDK has inside it without them being tied to any particular usage policy
and with very minimal dependencies.
Alekos Filini
Dec 10, 2021
This is the second part of a two-part blog series in which I talk through the changes made to BDK to make a Taproot transaction. If you haven't read it yet, check out [Part 1].
Alekos Filini
Nov 15, 2021
This is the first of a two-parts blog series in which I will try to explain all the changes that I made to BDK (and some of its dependencies) to make our first Taproot transaction in mainnet, which also
turned out to be the first ever use of the new OP_CHECKSIGADD opcode.