Skip to content

payjoin-2.0 tracking issue #1823

Open
Open

Description

@spacebear21

1.0 is finally out, which means we can officially start thinking about 2.0! This is a list of known breaking changes that have been in the works but were postponed until after 1.0.

Note that being listed here doesn't preclude a feature from being added as a feature in a minor release. The feature it replaces can be simply deprecated and removed in 2.0 when the time comes.

Activity

  1. added this to the payjoin-2.0 milestone on Aug 18, 2026
  2. benalleng commented on Sep 15, 2026

    @benalleng
    Collaborator

    As this is a breaking change we should think about how we should address API changes like in #1870

  3. DanGould commented on Sep 15, 2026

    @DanGould
    Member

    I would take inspiration from Rust Bitcoin as the model for this and then yeah, look at the other ecosystem players to figure out the best path forward.

  4. DanGould commented on Sep 15, 2026

    @DanGould
    Member

    We also almost definitely need to do a breaking change when Rust-Bitcoin 0.33 comes out. We probably want to schedule our changes to align with that if we can.

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

    apitrackingHigh-level tracking issues

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions