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
{{ message }}
This repository has been archived by the owner on Sep 12, 2019. It is now read-only.
In writing the new anchor guide, I was at first a little confused to find that I had to specify extra_memo in the payment parameters to the bridge server in order to trigger usage of the compliance server (in my first several attempts, I had left it empty and couldn’t figure out why I wasn’t seeing any compliance activity).
After looking through the source, I definitely understand that using extra_memo as a shorthand prevents hitting the receiver’s stellar.toml (especially since the compliance server will do it again), but from a user perspective, this still seems a little awkward. Maybe the compliance server could respond with a special status code to indicate that no compliance was necessary or maybe the bridge server could pass along the foreign stellar.toml data?
The text was updated successfully, but these errors were encountered:
In writing the new anchor guide, I was at first a little confused to find that I had to specify
extra_memo
in the payment parameters to the bridge server in order to trigger usage of the compliance server (in my first several attempts, I had left it empty and couldn’t figure out why I wasn’t seeing any compliance activity).After looking through the source, I definitely understand that using
extra_memo
as a shorthand prevents hitting the receiver’sstellar.toml
(especially since the compliance server will do it again), but from a user perspective, this still seems a little awkward. Maybe the compliance server could respond with a special status code to indicate that no compliance was necessary or maybe the bridge server could pass along the foreignstellar.toml
data?The text was updated successfully, but these errors were encountered: