Hot answers tagged

2

At any given time, the latest Horizon release can be found here: https://github.com/stellar/go/releases Horizon 0.23 is released here. Anyone can download and run it, although it requires a small amount of technical know-how. You can follow the Quickstart guide to get something up quickly to play with. It should only take a few minutes. Alternatively, you ...


2

The parameter order is wrong, it should be: strictSendPaths(sourceAsset, sourceAmount, destination)


1

The sender of a path payment does not need to trust the asset on the receiving end of the path payment. That's the beauty of them! I touch on this in Understanding Stellar Path Payments as well. Path payment operations simplify the process by eliminating the need for the sender to have a trustline, and by bundling transfer and conversion into a ...


1

The derivation path for stellar is defined in SEP-5 and only uses the first three levels. The default path is m/44'/148'/0' The fourth level would have been a flag for change addresses, which doesn't apply to stellar. The apostrophe indicates the usage of hardened addresses which doesn't apply to change at all, so it must not be at the 4th level even if it ...


1

Horizon always returns the optimal path. The E->F part is redundant in this particular case as you requested payment path from E to A. And that's what we clearly see here: EXY->DXY->CLM->BCZ->AXY.


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?


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?


Only top voted, non community-wiki answers of a minimum length are eligible