Repository navigation
FFI Tracking Issue #739
Description
This is a tracking issue for high-level items related to FFI and language bindings.
FFI
- Complete the payjoin-ffi transfer from LtbLightning #734
- Test payjoin_ffi backwards compatibility with v1 #736
- Audit payjoin-ffi's
ImplementationErrorFromimplementation #737 - Squash payjoin-ffi/uniffi feature into default behavior after dart-uniffi bindings work #790
- Delete duplicate InMemoryPersister reimplementations across language bindings #1529
Individual language bindings
- Uniffi dart #829
- Upgrade Bull Bitcoin Mobile from payjoin-flutter to payjoin_dart
- Upgrade Cake Wallet from payjoin-flutter to payjoin_dart
- Kotlin bindings (relevant draft PR: Add initial scaffolding for Kotlin Multiplatform (Android target only for now) LtbLightning/payjoin-ffi#72)
- Swift bindings
- demand from FullyNoded Feature: Payjoin Fonta1n3/FullyNoded#271
- Support WASM with wasm_bindgen and conditional compilation #740
Activity
DanGould commentedon May 6, 2026
@spacebear21 you mentioned this was stale in #1513. How does this track separately than the ffi label? Is it just external? is it a nebulous idea of
payjoin-ffi-1.0(if there is a such a goal, I have no such goal yet)? something else?spacebear21 commentedon May 6, 2026
IMO we can close #736 as wontfix, make standalone issues for each language we may want to support (kotlin/swift which should both be pretty easy since they're supported natively by uniffi), and close this tracking issue. payjoin-ffi-1.0 doesn't really make much sense IMO as it's just a glue library. What matters is downstream language releases and publishing those to the repective package managers.