Tracker: production-ready / first tagged release

[reez]

This issue tracks the bar for the first tagged/stable bdk-dart release and also collects feedback from real integrations about what they consider production-ready. Items here are release criteria for bdk-dart itself, not necessarily blockers for downstream apps shipping on the current 2.3.x line.

Feel free to add anything you think is required:

Open Items

• Improve example app to MVP-level developer reference (Example mobile app #5)
• Execute pub.dev release metadata + dry-run checklist (Execute pub.dev release metadata and publish dry-run #43)
• First tagged bdk-dart release targets bdk-ffi 3.x

Open Questions

• Track web target support strategy and feasibility (Track web target support strategy for bdk-dart #40)

Active work

• Prebuilt binaries path with verification and fallback (auto | always | never) (Support prebuilt binaries as default (with opt-in source builds) #20)

Done

• Baseline CI workflow exists (format/analyze/test/demo analyze) (Add CI workflows #10)
• Fix example resource-disposal bug(s) (Ensure ElectrumClient is always disposed on failure in network_example.dart #14)
• Define and document supported platform/architecture matrix (Define and publish supported target matrix for bdk-dart #24)
• Pub.dev readiness (metadata, publishing steps, release checklist) (Pub.dev release readiness checklist for bdk-dart #28)
• Add CI compatibility checks against upstream bdk-ffi changes (Add CI compatibility check against upstream bdk-ffi changes #30)
• Add integration test harness for network-based client tests (Add integration test harness for network-based client tests #31)
• Add missing CI coverage for target matrix builds (Expand CI to validate target matrix builds (Windows + Flutter mobile smoke) #25)
• Add integration tests for Electrum sync/apply/persist flow (Add integration test coverage for Electrum sync/apply/persist flow #26)
• Add integration tests for Esplora sync/apply/persist flow (Add integration test coverage for Esplora sync/apply/persist flow #27)
• Track and move to bdk-ffi 2.3 release tags when available (Track bdk-ffi 2.3 release and switch pinned deps #18)
• API ergonomics improvements (named-argument-friendly surface) (Named arguments for easiness of use #21)
• UniFfi::UnexpectedEnumCase uniffi-dart (bug: wallet.transactions() may throw UniFfi::UnexpectedEnumCase due to ChainPosition converter offset accounting #46)

[Saleciani]

If you can also target web, it would be very interesting for applications that can be done.

Bitcoin wallets suffer from censorship in many jurisdictions in app stores, having web versions easily helps :)

[reez]

If you can also target web, it would be very interesting for applications that can be done.

Bitcoin wallets suffer from censorship in many jurisdictions in app stores, having web versions easily helps :)

absolutely awesome suggestion, added