Skip to content

Receiver<Monitor>::check_payment needs rename #1656

@DanGould

Description

@DanGould

Which crate is this issue for?

payjoin

Motivation

not checking for a payment, checking for transaction broadcast. Payment != detected != settlement. IMO "payment" is best reserved for lightning. If this is looking for the txid of the

Possible solution

candidates for the rename include

  • check_for_counterparty_broadcast
  • detect_session_transaction
  • watch_for_transaction

I'd look at bitcoin core and other places for naming inspiration. This is a matter of taste where I've been expressing settlement ~= payment everywhere it feels important to be consistent. And this function doesn't quite check for confirmed settlement afaiu. It needs to be made clear

This is for payjoin but will knock onto payjoin-ffi. If this can be done before 1.0, great. If not, we'll have to #[deprecate]

Useful Skills

No response

Guidance for new contributors

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueDoes NOT mean "an LLM can do this." Please discuss the constraints and intended approach.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions