PDK Dev Call Updates – August 11th, 2025

[arminsabouri]

PDK Dev Call Updates – August 11th, 2025

Armin

• Met with Liana developers and presented integration code (same update at Ben's below)
• Began decoupling v2 from v1 receiver typestates (Decoupling receiver typestates with common abstractions #943).
• Opened Receiver create_session should accept an amount param #895.
• Reviewing several open PRs; owes Zele a follow-up review Make max fee rate sticky per payjoin-cli session #934 .
• Constraint: Running Dart tests remain a blocker Add amount to recv session context #920 (comment). Suggestion from team was to run them a few times. Dart int. tests are flacky because of the docker redis dependency which should be removed in Replace redis with file based mailbox storage #915

Ben

• Met with Pyth (Liana dev) to discuss their development cycle and requirements for integrating Payjoin into their wallet.
• Squashed Liana integration POC commits into a single commit and opened a PR. Expecting review this week. In general their team has expressed that they will review highlevel arch. decisions this cycle (1 month) and next month they can take a more active role in the integration.
• Reached out to Yash for an update on the promised wireframes.
• Opened a PR for full mutation coverage Full mutant coverage #928
• Discussed review feedback on Full mutant coverage #928 and requested input on testing a specific one-liner.

Chavic

• Submitted a small PR adding formatting to generated Dart code.
• Completed creating all issues required for a v1 release.
• Preparing a PR to linearize git history.
• Implemented several organizational process improvements in the dart-uniffi repo.

Dan

• Noted satisfaction with ongoing development progress.
• Continued work on the sender refactor Refactor sender to validate PjParam by version #901
• Spending majority of time on operational tasks.
• Payjoin Foundation announcement for Riga was a success!

Nothingmuch

• Created the Payjoin Directory tracking issue (Directory Service Tracking Issue #941).
• Progressed on the Redis removal PR; code cleanup still needed before merge Replace redis with file based mailbox storage #915
• Planning to review open PRs
• Discussed a general multiparty Payjoin design with Armin.
• Began block indexing work.

Spacebear

• Conference week; available part-time.
• Focusing mainly on reviewing PRs.

Shehu

• Continued work on Sled-to-Rusqlite migration Migrate payjoin-cli from sled to rusqlite #873
• Investigating the system time precision issue std::time::SystemTime has nanosecond precision but Payjoin only sees u32 UnixTime second precision #893 . Has a follow up comment where a fix is proposed. Looking for feedback
• Looking into Payjoin Directory Axum refactor. Part of the larger directory tracking issue Directory Service Tracking Issue #941

Zealsham

• Responding and working through directory prometheus metrics PR Introduce metrics Collection via prometheus for payjoin directory #848. Struggling to expose the metrics endpoint (?)
• Opened a PR to add configuration saving; Ben identified an MSRV issue payjoin-cli should have allow saving configs #896
• Continuing work on key expiration and rotation Ensure key rotation is accounted for in server and client implementations #445
• Reading the OHTTP RFC for deeper understanding before opening a PR
• Reminder from Nothingmuch: reach out directly if blocked on any issues related to Directory Service Tracking Issue #941

Zele

• Opened PR Make max fee rate sticky per payjoin-cli session #934 to make the max fee rate sticky per payjoin-cli session
• Opened issue Refactor SessionContext into precise, state-specific structs (remove bogus Option<T> fields) #929 to refactor SessionContext into precise, state-specific structs.
• Continuing work on PR Make max fee rate sticky per payjoin-cli session #934 and will shift to Refactor SessionContext into precise, state-specific structs (remove bogus Option<T> fields) #929 if time allows.