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 rippled implementation of gateway_balances does not return invalidHotWallet as an error if one of the addresses provided in hotwallet does not have a trustline with account, but instead simply does not include a balance for the address in its response.
Clio, however, returns the invalidHotWallet error code when an address in hotwallet does not have a trustline with account. 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:
If you run the same RPC against https://s1.ripple.com which is Clio, Clio returns this
{
"result": {
"error": "invalidHotWallet",
"error_code": 5004,
"error_message": "Invalid hot wallet.",
"status": "error",
"type": "response",
"request": {
"method": "gateway_balances",
"params": [
{
"account": "rMxCKbEDwqr76QuheSUMdEGf4B9xJ8m5De",
"hotwallet": [
"rKm4uWpg9tfwbVSeATv4KxDe6mpE9yPkgJ"
],
"ledger_index": "validated",
"strict": true
}
]
}
},
"warnings": [
{
"id": 2001,
"message": "This is a clio server. clio only serves validated data. If you want to talk to rippled, include 'ledger_index':'current' in your request"
}
]
}
Expected Result
Clio should return a successful response to gateway_balances even if one of the hotwallet does not have a trustline with account. Hot wallets that do not have a trustline to account should not be included in the response's balances array.
Actual Result
Clio returns invalidHotWallet error code
Environment
N/A
Supporting Files
The text was updated successfully, but these errors were encountered:
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: