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
In some circumstances the pathfinder returns invalid paths, which trigger op_too_few_offers or op_over_source_max errors when used in path payment operations (with a 1.5% padding).
Example:
{
findPaymentPaths(
sourceAccountID: "GASKYWPPQ2VSO6KNIPIRVXMSSDGZLYZQ67CDTLVXOXYDG26SPZ66EDCQ",
destinationAsset: "BTC-GATEMHCCKCY67ZUCKTROYN24ZYT5GK4EQZ65JJLDHKHRUZI3EUEKMTCH",
destinationAmount: "0.0000010"
) {
sourceAsset {
id
}
destinationAsset {
id
}
sourceAmount
path {
id
}
}
}
In some circumstances the pathfinder returns invalid paths, which trigger
op_too_few_offers
orop_over_source_max
errors when used in path payment operations (with a 1.5% padding).Example:
Returns a path for XLM:
When this path is used in path payment with a sendMax parameter of 0.1725623 (sourceAmount + 1.5%) then the tx fails with
op_too_few_offers
.Horizon /paths doesn't identify this path at all but returns, e.g.:
(https://horizon.stellar.org/paths?source_account=GASKYWPPQ2VSO6KNIPIRVXMSSDGZLYZQ67CDTLVXOXYDG26SPZ66EDCQ&destination_account=GASKYWPPQ2VSO6KNIPIRVXMSSDGZLYZQ67CDTLVXOXYDG26SPZ66EDCQ&destination_asset_type=credit_alphanum4&destination_asset_code=BTC&destination_asset_issuer=GATEMHCCKCY67ZUCKTROYN24ZYT5GK4EQZ65JJLDHKHRUZI3EUEKMTCH&destination_amount=0.0000010)
The found astro path doesn't look plausible to me because you normally lose money when going XLM -> BTC -> BTC.
Could you guys have a look? @nebolsin @charlie-wasp
The text was updated successfully, but these errors were encountered: