fix a typo for nut08 #60
No reviewers
Labels
No labels
breaking change
bug
documentation
enhancement
needs discussion
needs implementation
new nut
ready
wallet-only
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo-admin/nuts!60
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "patch-1"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
ACK
998cb8de3a. I had noted the same thing a few weeks ago.We should make sure this change is disseminated widely however, because it is a breaking change in the serialization of the
PostMeltRequestobject.Note also that PR #55 renames the
prfield torequestin theCheckFeesRequestobject. We should make sure we use consistent wording across objects in the spec, and this fix might be better done as part of #55. @callebtc it's your call on this.Thanks for the PR but we can't merge this. This isn't a typo but renaming a field and would break the protocol.
@thunderbiscuit is right that we want to rename this field to a more generic name
requestwhich can harbor lightning invoices, on-chain addresses, or whatever else we might encounter along the way.https://github.com/cashubtc/nuts/blob/main/08.md#example-1
So what is
Everything here is the same as in [NUT-05](https://github.com/cashubtc/nuts/blob/main/05.md) except for outputs.?Yes, it allows for change to be returned if the routing fee is over paid.
Pull request closed