-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
temREDUNDANT when swapping Gatehub USD with Bistamp USD (Version: 2.1.1) #4994
Comments
For Swaps with the same currency code, you should specify the Paths field. rippled/src/ripple/app/tx/impl/Payment.cpp Lines 121 to 130 in c88166e
|
Why that? Is that a feature or a bug? |
It is a very long-standing process and I don't know about it. |
Ok, at least there is a solution! |
@tequdev I tried many combination with what I found on https://xrpl.org/docs/concepts/tokens/fungible-tokens/paths/ and https://xrpl.org/docs/references/http-websocket-apis/public-api-methods/path-and-order-book-methods/ripple_path_find/ But I always end up with either a temBAD_PATH, temBAD_PATH_LOOP or tecPATH_DRY (trustlines are set, and partial payment flag is on). I didn't find anything about paths for AMM, maybe it's different? The only path accepted by rippled engine that threw tecPATH_DRY is this one :
EDIT: ripple-path-find method don't return any path
|
it would work with the following Paths field "Paths": [
[
{
"currency":"XRP"
},
{
"currency":"USD"
"issuer":"rvYAfWj5gh67oV6fW32ZzP3Aw4Eubs59B"
}
]
] When specifying both destination_amount and source_amount in path_find, the amount you want to send should be specified in source_amount, and the value of destination_amount should be "-1". rippled/src/ripple/app/paths/PathRequest.cpp Lines 177 to 182 in c88166e
Your code is incorrect, so it is not making the expected path_find result. |
I'll try the path later, for the path request, I'm not using source_amount, this is not the problem (I'm not getting the amount malformed exception) |
I just tried your path, and it works! I was asking myself "why add XRP in the path since XRP is not involved?"
It works too. As simple as that. Thx for the help ;) |
Issue Description
When executing a swap transaction between Gatehub USD and Bitstamp USD, a temREDUNDANT error is thrown by the rippled engine.
Same currency with different issuer is the only reason I can see behind this bug, since it only appears for this swap pair.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: