Skip to content

Receiver Monitor follow-ups #2034

Open
Open

Description

@spacebear21
  • Expose contested_prevouts: this would be useful for wallets to build an index of their sessions. IIRC we had decided to ship this step improvement and see what API demands come up, before committing to a new public interface.
  • A classifier on SessionHistory that also works for closed and canceled sessions. Same as above, I'm not convinced it's a strict requirement for the next release.

Originally posted by @spacebear21 in #1971 (review)

Activity

  1. DanGould commented on Nov 6, 2026

    @DanGould
    Member

    cancel --no-broadcast seems like fail broken? shouldn't the positive --broadcast be the flag? Maybe we already discussed

  2. xstoicunicornx commented on Nov 6, 2026

    @xstoicunicornx
    Collaborator

    I'm not sure I entirely understand the question, but the original intention was that the standard flow should be that cancel will broadcast your transaction as well close the session. If broadcast fails, like when the fallback is double spending an already broadcast/mined transaction, then cancel will fail and cancel --no-broadcast can be used instead. This seems like the better flow to me but I don't think there was much discussion around which should be the default behavior.

  3. spacebear21 commented on Nov 6, 2026

    @spacebear21
    CollaboratorAuthor

    Yeah i think broadcasting the fallback is generally the default behavior we want to demonstrate. Maybe the --no-broadcast flag could be renamed if it's the negation you're concerned about.

  4. spacebear21 commented on Nov 9, 2026

    @spacebear21
    CollaboratorAuthor

    Updated the issue do drop follow-up items resolved by #2043

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions