I see @Sjors has been pushing to [`32.x` branch](https://github.com/2140-dev/bitcoin-capnp-types/tree/32.x) creating this issue so we can coordinate the `v0.3.0` (matching Bitcoin Core `v32.0`) release
Activity
[-]v32[/-][+]v32 -> v0.3.0[/+][-]v32 -> v0.3.0[/-][+]`v0.3.0` (matching Bitcoin Core `v32.0`)[/+]feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
chore: default to Bitcoin Core 32.0
plebhash commentedon Oct 22, 2026
closed via #43
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
chore: default to Bitcoin Core 32.1
feat(bitcoin-core-sv2): add a v32x runtime targeting Bitcoin Core 32.x
chore: default to Bitcoin Core 32.1
chore: default to Bitcoin Core 32.1
chore: default to Bitcoin Core 32.1
chore: default to Bitcoin Core 32.1