Add support for SEP 29. This is important to provide a simple way to protect users from forgetting memos when submitting payments to exchanges.
What would you like to see?
[ ] Add server.checkMemoRequired(tx) with support for SEP0029.
If any of the operations included in tx are of type payment, pathPaymentStrictReceive, pathPaymentStrictSend, or mergeAccount, then the SDK will load the destination account from Horizon and check if config.memo_required is set to 1 as defined in SEP0029.
While you could do the check in parallel, we decided to do a sequential check to avoid getting rate limited by SDF's public horizon which is used by default by many clients (read more here).
[ ] Change server.SubmitTransaction to always check if memo is required.
[ ] Allow the the check to be bypassed by setting skipMemoRequiredCheck to true, but default to requiring the check:
Add support for SEP 29. This is important to provide a simple way to protect users from forgetting memos when submitting payments to exchanges.
What would you like to see?
[ ] Add
server.checkMemoRequired(tx)with support for SEP0029. If any of the operations included intxare of typepayment,pathPaymentStrictReceive,pathPaymentStrictSend, ormergeAccount, then the SDK will load the destination account from Horizon and check ifconfig.memo_requiredis set to1as defined in SEP0029.[ ] Change
server.SubmitTransactionto always check if memo is required.[ ] Allow the the check to be bypassed by setting
skipMemoRequiredChecktotrue, but default to requiring the check:[ ] The check should be skipped automatically if the transaction includes a memo.
You can use the following implementations as a reference:
JS SDK: https://github.com/stellar/js-stellar-sdk/pull/516Go SDK: https://github.com/stellar/go/pull/2396Refs: https://github.com/stellar/stellar-protocol/issues/575