Skip to content

Standup Input: Week of 2026-03-16 #1417

Closed

Description

@DanGould

Please reply by Monday end-of-day (your timezone).

Format:

  • Shipped: What you landed last week (PR/issue links)
  • Focus: What you're working on this week
  • Blockers: Anything stopping you — name who can help

cc @DanGould @spacebear21 @arminsabouri @benalleng @chavic @zealsham @Mshehu5 @0xZaddyy

Activity

  1. chavic commented on Mar 16, 2026

    @chavic
    Collaborator

    Shipped:

    • Focused on researching AI workflows and upskilling at an AI workshop
    • Partially reviewed Uniffi Dart #117
    • Promoting demo for Rust x C# Integration for the BTCPay Community on X/Twitter

    Focus:

    • Prepare packaging and library for Rust Payjoin C# package on NuGet, plus version pinning
    • Prepare for work on BTCPay Payjoin Plugin (scoping out the task)
    • Catch up on review of Uniffi Dart #117, and any other pending reivew work.
    • close remaining review rework from #1351 and land any unresolved Tokio runtime / cert-aware OHTTP follow-up changes.
    • update C# tests with the validations from #1263.
    • continue test-gap fixes under #1264.

    Blockers:

    • Maintainer turnaround on #168 has been lagging, so we can assume we move on with my fork for now.
  2. DanGould commented on Mar 16, 2026

    @DanGould
    MemberAuthor

    Shipped

    • Async standup v2 #1387
    • Buttondown is actually sending emails from payjoin.org now, thanks .@thebrandonlucas. We can post stuff to our most 'owned' audience: email. (nostr tries but people don't read as much)

    PRs reviewed:

    Focus

    • Unblock integrations:
      1. Triage the Cake/Bull Bitcoin unreliability, Get it specifically identified, QA around it. If other integrations aren't reliable because of a problem we introduced here it's useless to try and do others.
      2. Review LDK-Node integration. Our closest next integration Add Payjoin Receiver Support (BIP 77) lightningdevkit/ldk-node#746
      3. Unblock Ben if possible, Liana gonna be in my town next week

    Bottleneck

    Trying to do too much at once. When our team is focused on a single release or integration we get it done. I'm not sure which one that is (Boltz is super high leverage, BB exchange, Liana, LDK-Node, BDK-CLI w/ persistence, BTCPay all in progress. If Cake's broken because of us we need to fix). Will find out tomorrow.

  3. zealsham commented on Mar 16, 2026

    @zealsham
    Collaborator

    Shipped

    • db metrics pr
    • request-size limit pr
    • reviewed fold ohttp into mailroom pr
    • reviewed fetch ohttp once pr

    focus

    • get db metrics pr in if review lead to changes
    • unique shortid counters metrics using hyperloglog for daily,weekly and hourly .

    Blockers

    • none
  4. Mshehu5 commented on Mar 16, 2026

    @Mshehu5
    Contributor
  5. benalleng commented on Mar 17, 2026

    @benalleng
    Collaborator

    Shipped

    Focus

    • Try to get further review on [WIP] Payjoin receiver wizardsardine/liana#2011
    • Figure out why the current payjoin-cli doesn't work with external nodes to be able to test with a mainnet node for Cake and BB integration testing.
    • Begin to think about transitioning payjoin-cli away from per-session relay selection to per-request

    Blockers

    • Hopefully the review cycle for the liana payjoin receiver PR gets some momentum going for it.
  6. arminsabouri commented on Mar 17, 2026

    @arminsabouri
    Contributor

    Shipped:

    Focus:

    • need to review sim PRs
    • tickets for co spend proposal cost function
    • Generalizing the fingerprint / general sub tx model for payjoin.

    Blocked:

    • Trying to do too much at once.
  7. spacebear21 commented on Mar 17, 2026

    @spacebear21
    Collaborator

    Shipped:

    Focus:

    • Mailroom is in a good enough place now that I can turn focus back to pushing in-flight integrations. Reviewing LDK-node, bdk-cli, and Liana PRs this week.
    • I'd like to publish the FFI payjoin packages to their respective package manager and document that process, so downstream implementations can actually pull from pub.dev/pypi/npm/etc. We currently just have placeholders for namesquatting but working ones.

    Blockers:

    • vinteum/localhost mailrooms hosting
    • Boltz docker env, last tried setting it up in ~November and hit a wall before turning to other things, will try setting it up again from scratch so we can restart integration work.
  8. DanGould commented on Mar 17, 2026

    @DanGould
    MemberAuthor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    standup-inputWeekly standup input issue

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions