Skip to content

Standup Input: Week of 2026-03-02 #1372

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

Activity

  1. chavic commented on Mar 2, 2026

    @chavic
    Collaborator

    Shipped:

    • In rust-payjoin, last week I shipped C# CI stability updates and review support for downstream Dart integration work.
    • Helped @spacebear21 with C# CI SDK by pinning C# version in CI d06394e.
    • I reviewed rust-payjoin integration PRs #1364 and #1367, including follow-up discussion on #1364.
    • In uniffi-dart, I shipped named-argument API generation updates, opened and merged #112 in uniffi-dart, reviewed #115.
    • In uniffi-bindgen-cs, I moved UniFFI 0.30 C# parity work through upstream PR: #168 (still open), the branch is chavic/uniffi-0-30-csharp-gap-fixes.

    Focus:

    • Settle #168 through review and get the UniFFI 0.30 C# parity fixes merged.
    • Carry over from last week:
      • 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.
      • Track any follow-up fixes from rust-payjoin integration changes after #1364 and #1367.

    Blockers:

    • Reviewer bandwidth and maintainer turnaround on #168 is the main gating dependency right now.
  2. zealsham commented on Mar 2, 2026

    @zealsham
    Collaborator

    shipped: depreciating payjoin-directory and implementing db service pr

    FOCUS:
    still working on the db service PR, expecting review comments and some changes to be implemented, as well checks.

    Blocked:
    None

  3. DanGould commented on Mar 2, 2026

    @DanGould
    MemberAuthor
    • Shipped: What you landed last week (PR/issue links)
      • I'd like the robots to be working for us in a productive (i.e. we at least learn lessons and don't produce more work than we consume) while I sleep for at least an hour straight two nights in a row

      • AI Agents running ~50 minutes straight with minimal intervention two nights in a row. Haven't quite hit an hour, but I also gave them pretty narrowly scoped, can-do tasks.
      • ~10 issues addressed here and reviewed https://github.com/DanGould/rust-payjoin/pulls from this effort, I think they're much less sloppy than last & will be brought over this week
      • Audit public API to take arguments by reference where possible #1373
      • Forked all of the disparate research / impl repos into my own meta repo, spun up recursive agents, did some deep research of my own, asked Armin questions and got answers. Will make public in some form this week.
      • reviewed bump prs, timeline pr @ research docs 1 2
    • Focus: What you're working on this week
      • In order of importance
      • Mailroom running on our experimental server by EOW
        Mailroom running on someone else's server by EOW

      • The autonomy goal still stands, but should be able to double to 2h.
      • BTCPay x Liana off the ground with both teams this week, update integrations roadmap
    • Blockers: Anything stopping you — name who can help
  4. Mshehu5 commented on Mar 2, 2026

    @Mshehu5
    Contributor

    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

    • Probaby Yuval would like his opinon on whats the best approach to 919
  5. arminsabouri commented on Mar 2, 2026

    @arminsabouri
    Contributor

    Shipped: What you landed last week (PR/issue links)

    • Working on integrating the simulation with the analysis framework.
    • Dense Id System + Datalayout tx-indexer#9
    • Updated research timeline with an eye towards deprecating it and moving to new project tracker.
    • Benchmarked and parsed regtest and mainnet blocks

    Focus: What you're working on this week

    Blockers: Anything stopping you — name who can help

    • Review process on sim PRs is more involved and taking more cycles than anticipated. @0xZaddyy @Mshehu5 lets find some time to pair / do another office hours
  6. spacebear21 commented on Mar 2, 2026

    @spacebear21
    Collaborator

    Shipped: What you landed last week (PR/issue links)

    Focus: What you're working on this week

    • Mailroom running on our experimental server by EOW
      Mailroom running on someone else's server by EOW

    • I played around a bit locally with automated workflows to increase test coverage but wasn't really satisfied with the results, mostly it just wanted to add trivial tests just to make number go up. Will keep experimenting with this.

    Blockers: Anything stopping you — name who can help

    • Delivered the mailroom nixOS module for achow, who said she "can make it work probably, will just take a bit of time" due to her unique nix setup. I'll try my best to check in and push this along but don't know enough about nix to be really useful here. Perhaps @benalleng or @nothingmuch can help here.
    • bdkdart was very responsive in upgrading to uniffi-dart 0.1.0 with named parameters, which was previously a pain point for the BBM integration. Now waiting on BBM to update their bdk_flutter->bdkdart switchover PR to use named parameters.
  7. benalleng commented on Mar 2, 2026

    @benalleng
    Collaborator

    Shipped:

    Focus:

    Blockers:

    • Need to get some help on the liana wallet integration, its just been dragging on and I could use an additional set of eyes.
  8. DanGould commented on Mar 3, 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