1

Recreate this transaction on the Stellar laboratory (view XDR to see parameters):

AAAAAJ2XxPOBZhImQhYvufkgoiaUvlcAA3oYpZpxw4uO/3GeAAAAZAGEyw0AAAsBAAAAAAAAAAAAAAABAAAAAAAAAA0AAAABVVNEAAAAAADophqGHmCvYPgHc+BjRuXHLL5Z3K3aN2CNWO9CUR2f3AAAAAAAAAPoAAAAAJ2XxPOBZhImQhYvufkgoiaUvlcAA3oYpZpxw4uO/3GeAAAAAA3gtrOmy2mAAAAAAQAAAAFCVEMAAAAAAGrl+/NlIBMvk84azG8w7Y0MFeUfapja8f6qDe6lavWuAAAAAAAAAAGO/3GeAAAAQJitSo00BJq46wFO3OYd+Qm9PI90zfjqoT1refqi/QeCcZY9cZm2BXtUL6r9zekDQOlsn7a954BT2h4C2Kj/Ewc=

Regardless of the destMin (Minimum destination amount) I enter, 0.0000001 or 99999999999, I receive the error op_under_dest_min.

I tried a similar transaction with a pathPaymentStrictReceive transaction, and it went well.

Improve this question
  • I think this has something to do with the path. When one queries https://horizon.stellar.org/paths/strict-send?source_asset_type=native&source_amount=.0008&destination_assets=USD:GDUKMGUGDZQK6YHYA5Z6AY2G4XDSZPSZ3SW5UN3ARVMO6QSRDWP5YLEX&c=0.04171017617619466 for example, the destination_amount is quite too big and it is the same in all the entries, and when one uses the first path for example to send path payment strict send, the same error above returns. – J R Nov 18 '19 at 1:28
1

We think this may be a result of Strict-send pathfinder returns non-existent paths, which is fixed in Horizon 0.23. Would you try the new release and report back here?

Improve this answer
  • How does one try this new release? I am merely querying using my browser. – J R Nov 19 '19 at 3:03
  • 1
    Well, you could download it and try it out. Or wait until SDF deploys it, which will be on 2019-11-19 and then query horizon.stellar.org after that. – ire_and_curses Nov 19 '19 at 21:19
  • 0.23 is now up. And I now can carry out the transaction as expected. – J R Nov 21 '19 at 3:30

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.