-
Notifications
You must be signed in to change notification settings - Fork 57
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
gateway_balances introduces breaking change to API V1 due to invalidHotWallet return code (Version: 2.3.0) #1825
Labels
Milestone
Comments
kuznetsss
added a commit
to kuznetsss/clio
that referenced
this issue
Feb 3, 2025
…RPLF#1830) Fixes XRPLF#1825 by removing the check in the gateway_balances RPC handler that returns the RpcInvalidHotWallet error code if one of the addresses supplied in the request's `hotwallet` array does not have a trustline with the `account` from the request. As stated in the original ticket, this change fixes a discrepancy in behavior between Clio and rippled, as rippled does not check for trustline existence when handling gateway_balances RPCs Co-authored-by: Sergey Kuznetsov <skuznetsov@ripple.com>
kuznetsss
added a commit
to kuznetsss/clio
that referenced
this issue
Feb 3, 2025
…RPLF#1830) Fixes XRPLF#1825 by removing the check in the gateway_balances RPC handler that returns the RpcInvalidHotWallet error code if one of the addresses supplied in the request's `hotwallet` array does not have a trustline with the `account` from the request. As stated in the original ticket, this change fixes a discrepancy in behavior between Clio and rippled, as rippled does not check for trustline existence when handling gateway_balances RPCs Co-authored-by: Sergey Kuznetsov <skuznetsov@ripple.com>
kuznetsss
added a commit
to kuznetsss/clio
that referenced
this issue
Feb 4, 2025
…RPLF#1830) Fixes XRPLF#1825 by removing the check in the gateway_balances RPC handler that returns the RpcInvalidHotWallet error code if one of the addresses supplied in the request's `hotwallet` array does not have a trustline with the `account` from the request. As stated in the original ticket, this change fixes a discrepancy in behavior between Clio and rippled, as rippled does not check for trustline existence when handling gateway_balances RPCs Co-authored-by: Sergey Kuznetsov <skuznetsov@ripple.com>
kuznetsss
added a commit
that referenced
this issue
Feb 4, 2025
#1873) Port of #1830 into release/2.3.1. Fixes #1825 by removing the check in the gateway_balances RPC handler that returns the RpcInvalidHotWallet error code if one of the addresses supplied in the request's `hotwallet` array does not have a trustline with the `account` from the request. As stated in the original ticket, this change fixes a discrepancy in behavior between Clio and rippled, as rippled does not check for trustline existence when handling gateway_balances RPCs
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
The rippled implementation of
gateway_balances
does not returninvalidHotWallet
as an error if one of the addresses provided inhotwallet
does not have a trustline withaccount
, but instead simply does not include a balance for the address in its response.Clio, however, returns the
invalidHotWallet
error code when an address inhotwallet
does not have a trustline withaccount
. Although this is the correct behavior according to the xrpl.org documentation, this discrepancy between rippled and Clio should be considered a breaking change in the v1 API.Steps to Reproduce
Call
gateway_balances
on rippled and provide a hot wallet that does not have a trustline to the issuer:This returns
If you run the same RPC against https://s1.ripple.com which is Clio, Clio returns this
Expected Result
Clio should return a successful response to
gateway_balances
even if one of thehotwallet
does not have a trustline withaccount
. Hot wallets that do not have a trustline toaccount
should not be included in the response'sbalances
array.Actual Result
Clio returns
invalidHotWallet
error codeEnvironment
N/A
Supporting Files
The text was updated successfully, but these errors were encountered: