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
While the amendment is expected to work and has been implemented and tested, no one has really wanted it after 7 years. It is not listed on explorers like XRPSCAN, and it was introduced in c549c9d. FlowCross uses the functionality to do offer crossing through the payment engine, but no one seems to want the amendment, so we are fine with calling it obsolete.
The text was updated successfully, but these errors were encountered:
Can this issue please be reopened/readdressed? I definitely would like the amendment to be enabled so that Payment transactions can achieve the same value as OfferCreate transactions. Currently Payments have the advantage of permitting multiple "hops" through order book's, AMM's and Rippling, but incur greater transfer fee expense when consuming offers.
OwnerPaysFee can be marked as obsolete.
REGISTER_FEATURE(OwnerPaysFee, Supported::no, DefaultVote::no);
OwnerPaysFee
is not supported so can't be voted on anyway.Originally posted by @RichardAH in #4282 (comment)
While the amendment is expected to work and has been implemented and tested, no one has really wanted it after 7 years. It is not listed on explorers like XRPSCAN, and it was introduced in c549c9d.
FlowCross
uses the functionality to do offer crossing through the payment engine, but no one seems to want the amendment, so we are fine with calling it obsolete.The text was updated successfully, but these errors were encountered: