Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

req-pj behavior is described in the spec but not enforced in the code #433

Open
nothingmuch opened this issue Dec 7, 2024 · 0 comments
Open

Comments

@nothingmuch
Copy link
Collaborator

BIP 77 mentions using the BIP 21 req- prefix to compel the sender to use payjoin.

It looks like bip21/bitcoin_uri supports this handling of this, but the implied semantics in BIP 77 are that the sender should not fall back in case the receiver compelled payjoin usage, but this distinction is not exposed by the bip 21 parsing or PayjoinExtras struct, so the sender state machine doesn't know if pj or req-pj was used.

Secondly, on the theoretical/spec side of things, how should expiry be interpreted in the event req-pj was specified?

@nothingmuch nothingmuch changed the title req-pj behavior is described in the spec but not enforced in the req-pj behavior is described in the spec but not enforced in the code Dec 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: No status
Development

No branches or pull requests

1 participant