RIPPLE: Bitstamp Destination Tags now include Bitstamp account #

[Marbit]

I noticed today that Bitstamp changed my destination tag to be 9 + my Bitstamp account number. Since destination tags can be publicly viewed, doesn't this seem like a bad idea? To give out 50% of the login information for my Bitstamp account? It seems to me that it is just bad practice to provide tags that are linked to our login information. I am bewildered as to why Bitstamp would make such a change.

Am i overreacting?  

[1714954244]

1714954244

[1714954244]

1714954244

[1714954244]

1714954244

[mr_random]

Isn't the bitstamp account number just an incremented integer for each new customer (ie something predictable and easy to guess, unlike user email addreses).

[Marbit]

Isn't the bitstamp account number just an incremented integer for each new customer (ie something predictable and easy to guess, unlike user email addreses).

I have no idea. That's one of the reasons I ask. It just seemed to me that exposing logins to the public is just something that there is never any cause for.

It's also pretty uncool that Bitstamp didn't tell anyone about this. People already have their destination tags set up in their contacts... hopefully IOUs sent to the old tags will be credited properly. If not.... really fucked up.

[MAbtc]

https://ripple.com/wiki/Require_a_destination_tag_for_inbound_payments#Mapping_suggestions

According to the Ripple wiki, tags should be random and not sequential. I just don't get it.

I'm probably more concerned about the prospect of old destination tags not getting supported. If that happens without adequate notification, shit show will ensue, and people will be very unhappy with Bitstamp.

[MAbtc]

Isn't the bitstamp account number just an incremented integer for each new customer (ie something predictable and easy to guess, unlike user email addreses).

Do you mean incremented like, sequential? Account numbers aren't sequential.

[hazek]

Thank you for raising this concern. We fixed the issue and the new destination tags are now entirely random numbers. Old destination tags will still work for a while.

If you should experience any problems with them, please contact our support at: https://www.bitstamp.net/support/

[xilin]

Thank you for raising this concern. We fixed the issue and the new destination tags are now entirely random numbers. Old destination tags will still work for a while.

If you should experience any problems with them, please contact our support at: https://www.bitstamp.net/support/

How long is the old one can be used? I can see that the deposit dt in textbox is different from the button that the button is still showing the old one. What's more, when i tried to send btc to the new one in ripple client, it just send back and charged some fee.
Will we get a notice when the change begin?

[Marbit]

Thank you for raising this concern. We fixed the issue and the new destination tags are now entirely random numbers. Old destination tags will still work for a while.

If you should experience any problems with them, please contact our support at: https://www.bitstamp.net/support/

That's great to hear! I'm glad you guys fixed this so quickly. It makes me feel better not having login information exposed on the ripple ledger! 

Thank you for raising this concern. We fixed the issue and the new destination tags are now entirely random numbers. Old destination tags will still work for a while.

If you should experience any problems with them, please contact our support at: https://www.bitstamp.net/support/

How long is the old one can be used? I can see that the deposit dt in textbox is different from the button that the button is still showing the old one. What's more, when i tried to send btc to the new one in ripple client, it just send back and charged some fee.
Will we get a notice when the change begin?

^^^ Could you elaborate on how this happened? What "button"? Was it the new random 8 digit DT? Was it during the short time that they were showing dt=0? Was it the 9+account number?

I would also like to know how long the old tags can be used.

[hazek]

The old tags will remain active for one more month.