Weekly Check-in: Week of 2026-04-13

[payjoin-bot]

Weekly standup — each contributor has a thread below with auto-gathered activity.

Reply to your thread by end-of-day Monday (your timezone). Copy the template below and fill it in:

### Shipped
<!-- Add anything the bot missed: design work, specs, conversations, off-GitHub contributions. Correct any mistakes. Skip if the bot covered everything. -->

### Focus
What are you working on this week?

### Bottleneck
What is the single biggest bottleneck in progress toward your greater goal?
Name your goal. Name the constraint. Name who or what can unblock it.

Participated: @DanGould, @spacebear21, @arminsabouri, @chavic, @zealsham, @Mshehu5, @0xZaddyy

[payjoin-bot]

DanGould

@DanGould

Shipped

PRs reviewed:

• Add workflow runs for the ffi layer on the weekly flake maintenance

Last Week

Review your previous thread: Last week's thread

[DanGould]

Shipped

Last week I moved and did finances. Little shipped in code world.

Focus

This week I want to focus on unblocking review.

Bottleneck

I'm still time limited by operational constraints but this week should be the first that opens up since this started.

[payjoin-bot]

spacebear21

@spacebear21

Shipped

PRs reviewed:

• Document persistence backwards/forwards compatibility consideration
• Remove Docker instructions from CONTRIBUTING.md
• Lock transitive icu deps for ffi

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR awaiting review: Receive cancel()

[spacebear21]

Focus:

• BBM upgrade branch (local only for now as I'm still reviewing LLM output but will try to push ASAP and open a draft PR)
• Various events in NYC this week, OPNEXT thursday

Bottleneck:

• Time constraints due to conference events
• Review is a collective bottleneck, like Armin also mentioned. I am selectively picking a few high leverage PRs to review but have given up trying to keep up with every open PR. Thoughts on LLM first pass reviews and/or an automated triage system?

[payjoin-bot]

arminsabouri

@arminsabouri

Shipped

PRs merged:

• Miner addr
• Remove Docker instructions from CONTRIBUTING.md

PRs reviewed:

• Add dedicated miner role for block production
• Register all inputs as Vec
• Add optional esplora wallet setup for payjoin-cli backend
• Add RoundNumberHeuristics for change identification
• Audit storage panics: push panic decisions to callers
• Add project-specific contributing guidelines
• include all targets and features in clippy checks

Issues opened:

• Migrate btsim to this repo?
• Pipeline & ingestion profiling
• Contributing.md
• ProbablyNotChange variant + probabilistic notion of change detection

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR has requested changes: Add semi-honest overview

[arminsabouri]

Focus:

• Most of the coalition formation protocol in developed in the simulation in its simplest form in Propose co spends  btsim#12
• Finishing up lingering tasks and still revewing and getting tickets to new contributors
• Large chunks of last week were spent either getting ready or going to the mit expo and side events.
• Also need to catch up on review on rust-payjoin Prs requesting me

Blockers:

• Review is a bottle neck. I encourage new contributors to review each others work, review your own PR before requesting review and think more deeply about hte tickets before using the LLM harness

[payjoin-bot]

benalleng

@benalleng

Shipped

PRs merged:

• Add workflow runs for the ffi layer on the weekly flake maintenance
• Lock transitive icu deps for ffi

PRs reviewed:

• chore: update flake.lock

Last Week

Review your previous thread: Last week's thread

[benalleng]

Shipped:

• Attempted Add optional esplora wallet setup for payjoin-cli backend #1469 in hopes of simplifying payjoin-cli <-> downstream wallet integration tests but the code added too much complexity. Going to stick with a simple mirror download of the testnet chains in CI where Regtest is not available.

Focus:

• Spoke with Konstantin at Cake and got more information about the upgrade to payjoin_ffi for them.
  • They need to upgrade to a flutter with access to a dart sdk >=3.10.0 but the hive db they use is incompatible so unfortunately that is a blocker on their end until they switch to sqlite Upgrade payjoin bindings to use payjoin_ffi cake-tech/cake_wallet#3173
• Recieved feedback on the liana receiver PR so hopefully I can iterate on that and get the python tests added I need to.
• Going to try and pick up some slack to on review to get some of the wall of PRs cleared out.

Blockers:

• Focus confusion, not sure where I can be highest leverage with some of these integrations being more complex in their upgrades

[payjoin-bot]

chavic

@chavic

Shipped

PRs reviewed:

• use Optional FfiConverter's lower() for inner types

Issues opened:

• dart_async sleep timing test is too strict and fails on clean runs

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR has requested changes: Expose Receiver Error Kinds

[chavic]

Shipped:

• Added callback optional-record regression coverage to uniffi-dart and merged the Optional inner-type lowering fix, closing the gap where Optional callback roundtrips weren't exercised.
  (Uniffi-Dart/uniffi-dart@e6b93d4b, use Optional FfiConverter's lower() for inner types Uniffi-Dart/uniffi-dart#121)
• Moved PR upstream to persist payjoin receiver sessions across restarts in the main BTCPay plugin repo, moving the work from the personal fork toward production after rebase.
  (Persist payjoin receiver sessions across restarts ValeraFinebits/btcpayserver-payjoin-plugin#6)
• Opened payjoin artifact freshness tooling for the BTCPay plugin — build/packaging infrastructure to keep plugin artifacts current. (Add Payjoin artifact freshness tooling chavic/btcpayserver-payjoin-plugin#2)
• Reviewed and approved the "Persist contributed inputs" PR in the BTCPay plugin (merged), which complements the session-persistence work by also persisting the receiver's contributed inputs.
  (feat: Persist contributed inputs ValeraFinebits/btcpayserver-payjoin-plugin#3)
• Filed a bug for the flaky dart_async sleep timing test in uniffi-dart — the assertion window is too strict and fails on clean CI runs. (dart_async sleep timing test is too strict and fails on clean runs Uniffi-Dart/uniffi-dart#123)
• Continued updating the session-persistence PR on the personal fork with follow-up fixes. (Persist payjoin receiver sessions across restarts chavic/btcpayserver-payjoin-plugin#1)

Focus:

• Experimenting with OmX to see if I'll get better efficiency for harness workflow

• BTCPay Payjoin Milestone 1

  • Landed the session-persistence PR upstream in the BTCPay plugin repo. (Persist payjoin receiver sessions across restarts ValeraFinebits/btcpayserver-payjoin-plugin#6) Need to finish live restart/replay validation for durable receiver-session persistence. The code is in place on chavic/persist-receiver-sessions, but the missing proof is a real negotiation surviving.
  • Implement the BTC checkout model seam. The accepted direction is that the plugin owns Payjoin-related BTC checkout fields and payment URL generation through the BTC payment-method checkout model seam. Replace the current checkout-end post-render mutation path as the source of truth since we explicitly require model-driven checkout ownership instead of DOM or Vue mutation.
  • Test coverage for stable Payjoin URL generation, plain BIP21 fallback, restart survival, cleanup on invoice-state changes, and cleanup after successful Payjoin, cleanup after non-Payjoin payment, and cold-change routing; That is the point where persistence, checkout ownership, fallback behavior, cleanup behavior, and restart-safe replay all need to be demonstrated together rather than as isolated partials.

• Resolve the flaky dart_async timing test. (dart_async sleep timing test is too strict and fails on clean runs Uniffi-Dart/uniffi-dart#123)

Blockers:

• Error-surface PR stack through review — all seven remain open with no updates since Apr 5, awaiting maintainer bandwidth.

[payjoin-bot]

zealsham

@zealsham

Shipped

No activity found.

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR awaiting review: Properly format history timestmap
• PR has requested changes: OHTTP keys should be rotated
• PR has requested changes: Request size limiter
• PR has requested changes: Demonstrate failure handling with fallback TX broadcast
• PR has requested changes: Add config saving to payjoin-cli

[zealsham]

Shipped

• OHTTP keys should be rotated #1449

Focus

• Demonstrate failure handling with fallback TX broadcast #1164 handle review armin gave today
• Properly format history timestamp #1473 implement suggested apprach

[DanGould]

I see you pushed #1449 after Yuval's comment but did not respond. Please leave a substantial response to each point to each change requested so that reviewers know what kind of review they're signing up for.

please consider all scenarios and make sure they are handled correctly:

• server initializes with two expired keys
• server initializes with one valid key and one expired key
• server initializes with two valid keys

as far as i can tell only the last one is, and even that is buggy due to not updating mtime

there should be tests covering this

[zealsham]

my bad @DanGould, i did message him on signal in regards to the comments after the review circles before the last push.

[payjoin-bot]

Mshehu5

@Mshehu5

Shipped

PRs reviewed:

• Miner addr
• Tip to depth

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR awaiting review: Implement script type matching change heuristic

[Mshehu5]

Focus

Got a repy on bdk-cli PR, so currently working on requested pruning function from maintainer also redb is not a requirement for PR can be a follow up PR

Also working on payjoin/tx-indexer#55 need to finish up and remove it from draft

Bottleneck

none

[payjoin-bot]

0xZaddyy

@0xZaddyy

Shipped

PRs merged:

• Add project-specific contributing guidelines
• include all targets and features in clippy checks

Issues opened:

• fiat round payments in change detection heuristics

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR has requested changes: Add RoundNumberHeuristics for change identification

[0xZaddyy]

Focus

• Research robust approaches to handle Add decimal_hamming_weight utility with test coverage tx-indexer#48 and reduce false positives, as the current implementation seems brittle.
• Review PRs.
• sync with the team during office hours.

[ValeraFinebits]

Shipped

• test: Add payjoin-cli integration test utilities ValeraFinebits/btcpayserver-payjoin-plugin#5
• refactor: Add RunTestPaymentService and self-pay checks ValeraFinebits/btcpayserver-payjoin-plugin#4

Focus

• Continue integrating payjoin-cli into the integration tests.

[caarloshenriq]

PRs reviewed:

• Adds a recommended pre-commit hook that ensures lock files are updated #1442
• Add workflow runs for the ffi layer on the weekly flake maintenance #1468
• Unify mailbox TTL to a single value #1457
• Handle Retry-After header for 429 and 503 in gateway prober #1475

Focus

• finish no_std support
• review PRs

[xstoicunicornx]

Shipped

• Reviewed [WIP] Payjoin receiver wizardsardine/liana#2011 (review)

Focus

• Reviewing simple PRs that I think I have sufficient competence for
• Learning about multi-party transactions
• Strategizing for FFI bindings for Non-blocking Interface for Payjoin State Machine  #1446

Bottleneck

• Apologies for the very late update, been traveling and this has been my first opportunity to decompress
• Visiting family so not necessarily able to dictate my own schedule (will be like this until April 22)