Weekly Check-in: Week of 2026-06-29

[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: @benalleng, @zealsham, @Mshehu5

[payjoin-bot]

DanGould

@DanGould

Shipped

PRs merged:

• Rename Receiver<Monitor>::check_for_broadcast to check_for_transaction, etc.
• Mailroom metrics requests
• Mailroom fd hygiene

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR awaiting review: Feat/v2 receiver event split

[DanGould]

Shipped

Indeed got the fd & metrics stuff out as planned

Focus

This week is ALL payjoin-1.0. Hard deadline for my focus which needs to be full time on operations next week.

I'm particularly interested in fixing critical bug w/ #1685 and seriously considering #1692 to prevent stale status from showing in our 1.0 release, especially crucial for exchange integrations on the horizon to be robust to reorgs.

Bottleneck

timezone handoff / back-and-forth review cadence. I'll make myself available at the beginning of east coast times.

[payjoin-bot]

spacebear21

@spacebear21

Shipped

PRs merged:

• Upgrade to uniffi 0.31.2
• Update uniffi-dart and uniffi-bindgen-cs
• Prepare v0.2.1+v0.31.2 release
• Upgrade docker/login-action to v4
• Bump payjoin-mailroom version to 0.1.2

PRs reviewed:

• Remove Completed at history column
• Constrain toml dep to be consistent with other uniffi crates
• Rename Receiver<Monitor>::check_for_broadcast to check_for_transaction, etc.
• chore: bump uniffi-rs to 0.31.2 to ensure reproducible builds
• Offset cron job timing on directory health check
• Mailroom fd hygiene
• Allow cancel on closed sessions to reprint fallback tx
• Fix replayEventLog report closed session as expired.
• Mailroom metrics requests

Issues opened:

• Release v0.2.1+v0.31.2
• Release payjoin-mailroom-0.1.2

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR awaiting review: chore: update cargo.lock

[spacebear21]

Shipped

• Upgraded to payjoin-mailroom 0.1.2: payjo.in, lets.payjo.in as well as the benalleng, vinteum, bobspace, and achow instances.

Focus

• payjoin 1.0
• rebase & update bull bitcoin mobile PR

[payjoin-bot]

benalleng

@benalleng

Shipped

PRs merged:

• Offset cron job timing on directory health check
• Allow cancel on closed sessions to reprint fallback tx
• Constrain toml dep to be consistent with other uniffi crates

PRs reviewed:

• feat: port payjoin core to no_std
• Upgrade to uniffi 0.31.2
• Update uniffi-dart and uniffi-bindgen-cs
• Set anti-fee-sniping nLockTime in payjoin-cli
• Upgrade docker/login-action to v4
• Bump payjoin-mailroom version to 0.1.2
• Fix replayEventLog report closed session as expired.
• Mailroom metrics requests
• Introduce arbitrary crate
• Rename Monitor method

Issues opened:

• docker/login uses node.js 20

Last Week

Review your previous thread: Last week's thread

Auto-detected signals:

• PR awaiting review: Cli auto cancel
• PR awaiting review: Remove Completed at history column
• PR awaiting review: V2 metrics enhancement

[benalleng]

Shipped

• created https://github.com/benalleng/payjoin-pico2 for post 1.0 to add the no_std feature. in the long run I would like to explore defmt to test this further
• I reorganized the payjoin-cli-1.0 vs payjoin-cli-1.1 and beyond barrier to better understand what we actually need.

Focus

• get the current in flight cli PRs across the finish line in preparation for the 1.0 release

Bottleneck

Review on my PRs. Though I am a bit stretched on the PRs themselves. I can't reasonably have anymore inflight PRs without losing context on some of them

[DanGould]

@benalleng May you request my review on PRs blocked by review? I'm not seeing requests, although I reviewed some today so maybe that's why.

[payjoin-bot]

chavic

@chavic

Shipped

PRs reviewed:

• feat: preserve callable defaults
• chore: bump uniffi-rs to 0.31.2 to ensure reproducible builds

Last Week

Review your previous thread: Last week's thread

[chavic]

Shipped

Merged rust-payjoin:

• Expose InputPair outpoint over FFI. Closes the opaque InputPair gap; unblocks privacy-preserving selection and reading the settlement amount from the proposal. Expose InputPair outpoint over FFI #1654

Merged BTCPay Payjoin plugin (own):

• Sign receiver inputs inside rust-payjoin finalize callback. Scoped signing, no more sign-all + broad clear. Sign receiver inputs inside rust-payjoin finalize callback ValeraFinebits/btcpayserver-payjoin-plugin#64

Open PRs (BTCPay Payjoin plugin, under review):

• Use rust-payjoin privacy-preserving receiver input selection (reworked on top of Expose InputPair outpoint over FFI #1654). Use rust-payjoin privacy-preserving receiver input selection ValeraFinebits/btcpayserver-payjoin-plugin#59
• Check input/output ownership against the wallet and persist seen inputs. Check input/output ownership against the wallet and persist seen inputs ValeraFinebits/btcpayserver-payjoin-plugin#58

Reviews (uniffi-dart):

• Preserve callable defaults. feat: preserve callable defaults Uniffi-Dart/uniffi-dart#143
• Bump uniffi-rs to 0.31.2 for reproducible builds. chore: bump uniffi-rs to 0.31.2 to ensure reproducible builds Uniffi-Dart/uniffi-dart#146

Reviews (BTCPay Payjoin plugin):

• Increase max proposal poll attempts. test: Increase max proposal poll attempts ValeraFinebits/btcpayserver-payjoin-plugin#65
• Bump version 0.2.3 preview. chore: bump version 0.2.3 preview ValeraFinebits/btcpayserver-payjoin-plugin#63

Focus

Last week's PRs took longer than expected, with the new thoughts on accounting, much of this week is continuing what got pushed back.

BTCPay Plugin, finish the correctness pass:

• Land whole-wallet ownership + seen-inputs (Check input/output ownership against the wallet and persist seen inputs ValeraFinebits/btcpayserver-payjoin-plugin#58) and privacy-preserving selection (Use rust-payjoin privacy-preserving receiver input selection ValeraFinebits/btcpayserver-payjoin-plugin#59) past requested changes.
• Credit the observed on-chain settlement output value, not the expected invoice amount.
• Pin the settlement amount from the proposal and validate against the invoice.
• Make the settlement script crash-safe (derive from the committed PSBT on reconciliation).
• Fee estimation from NBXplorer + per-store config. Derive the receiver fee cap from estimation and make it configurable ValeraFinebits/btcpayserver-payjoin-plugin#60
• Decide + document the fallback-broadcast policy.
• Sweep the low-items: OHTTP key TTL, event-log retention, reservation lifetime, change-address churn, non-segwit inputs.

Blockers

• New accounting questions may become relevant; we need to quickly review concerns that may have been overlooked. This was briefly mentioned in reference to questions from Bull Bitcoin

[DanGould]

re accounting questions, ask your LLM how Bria handles it. It's the most thought out system of bitcoin accounting I've ever seen.

[DanGould]

Got that csharp 1.0 branch too? Might be the thing to contribute to the payjoin-1.0 release schedule

[payjoin-bot]

zealsham

@zealsham

Shipped

PRs merged:

• Fix replayEventLog report closed session as expired.

PRs reviewed:

• Remove Completed at history column

Last Week

Review your previous thread: Last week's thread

[zealsham]

FOCUS

• Doing mostly PR reviews this week

[payjoin-bot]

Mshehu5

@Mshehu5

Shipped

No activity found.

Last Week

Review your previous thread: Last week's thread

[Mshehu5]

Shipped

based of comments from https://github.com/orgs/payjoin/discussions/1644#discussioncomment-17334495 made changes to bdk-cli integration in bitcoindevkit/bdk-cli@bdb7f38
would appreciate a review on that commit. seems final review for PR will soon take place

Focus

working on seperating #1514 code to main crate and cli (current code is only in cli)

Bottleneck

I was sick for most of the past week, so progress was slower than expected. I will work on catching up and making up for the lost time.

[payjoin-bot]

0xZaddyy

@0xZaddyy

Shipped

No activity found.

Last Week

Review your previous thread: Last week's thread

[ValeraFinebits]

Shipped

Issues opened:

• Update rust-payjoin submodule to match payjoin/rust-payjoin#1686 ValeraFinebits/btcpayserver-payjoin-plugin#68

Began work on:

• Enhance relay and directory handling: support multiple entries, add retry logic ValeraFinebits/btcpayserver-payjoin-plugin#49

Focus

• Continue working on the plugin.

[bc1cindy]

Shipped

Issues Opened:

• Add Wallet::send (Bitcoin Core's send RPC) alpenlabs/bitcoind-async-client#125
• Retry transient directory errors, and a shared retry policy #1670
• Anti-fee-sniping nLockTime diverges #1676
• Add core RelaySelector #1694

PRs Opened:

• feat!: add Wallet::send for native anti-fee-sniping alpenlabs/bitcoind-async-client#126
• Resume v2 polling on transient directory errors #1671
• Set anti-fee-sniping nLockTime in payjoin-cli #1678
• Add core RelaySelector #1696

PRs Reviewed:

• Allow cancel on closed sessions to reprint fallback tx #1673
• Fix replayEventLog report closed session as expired. #1672
• OHTTP keys should be rotated #1449
• Payjoin-cli should cache ohttp-keys for re-use #1035

Request Review:

• OHTTP keys should be rotated #1449
• Document ohttp relay best practice #1547
• Decouple directory poll timing #1658
• Set anti-fee-sniping nLockTime in payjoin-cli #1678
• Add core RelaySelector #1696

Focus

• Tracking: relay-observable behavioral fingerprinting #1586
• Anti-fee-sniping nLockTime diverges #1676

[xstoicunicornx]

Shipped

• continued to refine Non-blocking Interface for Payjoin State Machine  #1446

Focus

• finish refactor for Non-blocking Interface for Payjoin State Machine  #1446
• open issue for ambiguous state when persisting MaybeTerminalSuccessTransition
• update Add comments to FFI interface #1653 to also include updates to the main payjoin crate doc strings to make the doc strings consistent between payjoin-ffi and payjoin crates
• look at Be specific about error handling for methods that don't return state transitions #1422

Bottleneck

Was unexpectedly out of "office" for large part of the last week, should be getting back into gear this week.

[caarloshenriq]

/check-in

[payjoin-bot]

Shipped

PRs reviewed:

• Remove Completed at history column

[caarloshenriq]

Bottlenack

I came to Casa21 for a week of deep-dive sessions, so I was out of the office last week. This week, I hope I can get back to focusing on the project.

Focus

• I bought an STM32F411 to test feat: port payjoin core to no_std #1615
• Review PRs