Ripple

[edge777]

Have a great Day everyone!

Edited December 27, 2017 by edge777

[Sukrim]

1 hour ago, edge777 said:

If you guys could guide us, it will be very helpful. Point us in right direction.

email partners@ripple.com asap.

Also pinging @nikb, @miguel, @JoelKatz and @mDuo13 to make sure that's the proper address or to follow up in private.

For your concrete issue: you need to set the RequireDestTag flag for your main deposit account (typically a "warm" wallet that moves funds every day or week to the hot wallet and/or to cold storage) - see https://ripple.com/build/listing-xrp-exchange/#deposit-xrp-into-exchange step 1a ("To use this, Alpha Exchange should have set the asfRequireDest flag on all of its accounts to require all incoming payments to have a destination tag like Charlie's."). The guide links to https://ripple.com/build/transactions/#accountset-flags

Since you seem to use Ripple-REST (why?!) you might have some problems to actually create that transaction and get it signed and broadcasted. Some options are: You could either create the necessary JSON yourself and run it against a local rippled server and let it handle all the transaction signing stuff or (first code audit, then) use a more fully featured web wallet (preferably in offline mode) like http://ripplerm.github.io/ripple-wallet/ or you could do a bit of scripting and so on with ripple-lib if you are into JavaScript.

Also it seems like you are thinking Destination Tags need to be "enabled": They always are enabled, this flag only disables NOT setting one to make sure payments that don't set one always fail (so you only need to deal with the cases where people mistype them, not when they don't set one at all).

[Sukrim]

5 hours ago, edge777 said:

Have a great Day everyone!

Seriously?! I took some time to reply and you don't even say "thank you" but instead edit out your initial question so nobody but you can benefit from the information.

Some people... :-(

[nikb]

I can no longer see the original post, so I have no way of contributing anything beyond what Sukrim already wrote.

[Sukrim]

Yeah, sorry about that: It was in essence "We are a quickly growing exchange, get a lot of new users and they get bloody cranky about the 20 XRP reserve - how do we enable destination tags and since ripple-rest is discontinued, how would we even do that?"

Edited December 28, 2017 by Sukrim

[Sukrim]

1 hour ago, nikb said:

I can no longer see the original post, so I have no way of contributing anything beyond what Sukrim already wrote.

Ah, would be partners@ripple.com the correct place to refer people to by the way? support@ripple.com was completely unresponsive the last two times I reported a phishing website (they just tell you to follow instructions in an automated mail and then never followed up).

[mDuo13]

Yes, partners@ripple.com is the right place for asking about help integrating an exchange or other business.

I should really write a clearer explanation of source & destination tags, why they're useful, and how they're different from Bitcoin-style deposit addresses...

 

P.S. please don't use Ripple-REST. It's old and broken and you could lose money (paying excessive XRP transaction costs) if you're not careful.

[Sukrim]

14 hours ago, mDuo13 said:

P.S. please don't use Ripple-REST. It's old and broken and you could lose money (paying excessive XRP transaction costs) if you're not careful.

Please move such projects temporarily or permanently to https://github.com/ripple-unmaintained, it is sometimes really hard to guess which ones are still active and which aren't.