8000
Add support for canonical source of truth for balance changes and payment success · Issue #589 · XRPLF/xrpl4j · GitHub
More Web Proxy on the site http://driver.im/
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
There is a quirk in the XRPL where sometimes the delivered_amount on a validated payment transaction is different from what's actually delivered as part of a payment. This only happens when a payment amount is so small, and the balance of a recipient is so large, that the balance change of the recipient is simply rounded to zero. In this case, the sender "delivered 0.01" but the receiver "received 0.00"
In these cases, it can be useful to know where to look for the de-facto truth about a payment amount. Typically, we can look no further than delivered_amount, except in these very unlikely, very edge-cases, where we should actually be inspecting meta-data to see which balances were updated (as a final source of truth).
Our client libraries in js and py have a helper method to summarize balance changes from the metadata for situations including ones like this. We should explore those methods, and consider adding something similar to xrpl4j.
The text was updated successfully, but these errors were encountered:
There is a quirk in the XRPL where sometimes the
delivered_amounton a validated payment transaction is different from what's actually delivered as part of a payment. This only happens when a payment amount is so small, and the balance of a recipient is so large, that the balance change of the recipient is simply rounded to zero. In this case, the sender "delivered 0.01" but the receiver "received 0.00"In these cases, it can be useful to know where to look for the de-facto truth about a payment amount. Typically, we can look no further than
delivered_amount, except in these very unlikely, very edge-cases, where we should actually be inspecting meta-data to see which balances were updated (as a final source of truth).Our client libraries in js and py have a helper method to summarize balance changes from the metadata for situations including ones like this. We should explore those methods, and consider adding something similar to xrpl4j.
The text was updated successfully, but these errors were encountered: