You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The BOLT 12 `quantity` field is incredibly unlikely to get any use
in practice (it assumes an online store which places some kind of
static offer for each item on its site, assuming that the merchant
doesn't want structured customer information nor the ability to
sell more than one item in a single order, both of which do not
exist in practice). Worse, supporting it requires an entire UI
flow built around the "quantity" concept, something which is a
nontrivial investment for downstream users of ldk-node.
Because the cost/utility tradeoff isn't nearly worth it, it was
dropped from the main offer-payment API in the upstream `lightning`
crate (requiring a separate
`ChannelManager::pay_for_offer_with_quantity` call).
For the same reason, we simply drop it from our API entirely here.
Absent someone who actually wants to use the `quantity` logic,
there is really no reason to support it.
I've assigned @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.
The BOLT 12 `quantity` field is incredibly unlikely to get any use
in practice (it assumes an online store which places some kind of
static offer for each item on its site, assuming that the merchant
doesn't want structured customer information nor the ability to
sell more than one item in a single order, both of which do not
exist in practice). Worse, supporting it requires an entire UI
flow built around the "quantity" concept, something which is a
nontrivial investment for downstream users of ldk-node.
Because the cost/utility tradeoff isn't nearly worth it, it was
dropped from the main offer-payment API in the upstream `lightning`
crate (requiring a separate
`ChannelManager::pay_for_offer_with_quantity` call).
For the same reason, we simply drop it from our API entirely here.
Absent someone who actually wants to use the `quantity` logic,
there is really no reason to support it.
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I agree that quantity is very confusing, but given it's a BOLT12 feature that other implementations might use, I'm not fully sure if we can get rid of it? Are we certain this doesn't lead to even more interop issues / confusion down the line?
Also added a few comments, this will also need a rebase since we landed #639 first as per @joostjager's request to fix develop breakage ASAP to be able to make progress.
The reason will be displayed to describe this comment to others. Learn more.
Please drop these changes to the static Swift files. These will only be updated/regenerated during release (though here on develop it doesn't matter as much as on main, which are actually part of the SwiftPM dependency).
We decided to make the develop behavior (tracking more-recent LDK main) the default behavior. With #655 we merged develop into main and now deleted the develop branch. Hence the base branch is changed to main here, too.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Also upgrades to latest RL.