question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

A unified address tag for withdrawing XRP, XMR, XLM, etc

See original GitHub issue

I’ve got a question about withdrawal API for currencies that require memo/message/tag/paymentId or variations for deposit/withdrawal.

Here’s a short list of affected currencies (likely there are more):

  • AEON
  • BTS
  • GXS
  • NXT
  • SBD
  • STEEM
  • STR
  • XEM
  • XLM
  • XMR
  • XRP

As far as I’ve seen, for fetch/create deposit addres API (where available/implemented) for most of the exchanges aren’t returning that value - so, nothing much that we can do about that. Binance is one example where they return the value (rather an exception). Perhaps we can add (map) it to the return array of fetch/create deposit address calls (new key). This should be easy to do, but we’d need to agree upon key name (if accepted).

Other thing that I’m wondering is if we could find a unified way to handle this parameter in withdraw/deposit calls: Thing is - every exchange that has withdrawals enabled usually accepts this optional param, and currently we’d have to pass it within optional params array. However, since the key name differs per exchange, so all clients need to do this mapping on their own - and this something that we could handle on library level IMO.

Adding new parameter is a BC break, I suppose that’s something we’d like to avoid… I’m open to any suggestions you may have. Thank you!

Issue Analytics

  • State:closed
  • Created 6 years ago
  • Reactions:1
  • Comments:7 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
kroitorcommented, Jan 16, 2018

@kornrunner alright, I would prefer the shortest one – let’s call it tag then ) Quite straightforward and recognizeable )

1reaction
kornrunnercommented, Jan 16, 2018

In XRP world it’s called Tag. Other coins have their own names for that (thus memo, message, paymentId). As it differs per currency, I’d put something generic. addressTag that binance uses is fine, tag is also fine by me…

Read more comments on GitHub >

github_iconTop Results From Across the Web

What is Destination Tag for XRP, XLM and Monero
Destination Tag is a technology that defines the specific recipient of the transaction. You can notice that you have the same XRP address...
Read more >
How to Send and Receive XRP and XLM?
Ask your recipient whether is there a destination tag/memo for the XRP/XLM address · Is the receiving address generated by a centralized or...
Read more >
What is Destination Tag in XRP, XLM and XMR transfers
Destination Tag free · 20 XRP is a non-refundable deposit to activate new address. Any other custody-free Ripple wallet with a unique address...
Read more >
What is XRP destination tag and XLM memo and how does it ...
A destination tag is a special identifier used in XRP transactions. In Stellar, the destination tag is called memo. Many custodial services, including ......
Read more >
Exchanges — ccxt 2.4.71 documentation
Python exchange = ccxt.binance ({ 'rateLimit': 10000, # unified exchange ... GXS, NXT, SBD, STEEM, STR, XEM, XLM, XMR, XRP, an additional argument...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found