Mt. Gox - SatoshiDICE payments


SUBMITTED BY: Guest

DATE: Jan. 5, 2013, 12:44 a.m.

FORMAT: Text only

SIZE: 1.6 kB

HITS: 1262

  1. There is the repeating situation where people are withdrawing from a Mt. Gox to an address which is incompatible with a hosted (shared) wallet like how Mt. Gox customer accounts use.
  2. SatoshiDICE is one of these. The betting site returns winnings (and commissions in losses as well) for all wagers to the sender's bitcoin address. There have been numerous reports of a party not knowing Mt. Gox accounts aren't compatible in this manner and using it anyway.
  3. While Mt. Gox isn't unique in maintaining a hosted (shared) wallet for its customer accounts, it is the largest. It might be good customer service to at a minimum maintain a blacklist of static bitcoin addresses where any BTC withdrawal requests from Mt.Gox are checked against this list. If there is a match either the request is rejected or at a minimum the user is warned before proceeding.
  4. There are multiple services like this ... SatoshiDICE, BTCDice, BitLotto, and a handful of others much smaller.
  5. There might even be a way to automate this where any service that is incompatible with EWallets can submit a request to be blocked. The request would be a standardized format and be submitted as a message using the message signing feature available in the Bitcoin.org client. There would probably be two messages for this, one to add a block, anther to clear a block. That's far down the road though.
  6. At present it is just a handful of addresses which would be best if they were excluded.
  7. Would Mt. Gox take the proactive step and add some method to either block or warn the user when these withdrawal requests are made?

comments powered by Disqus