|
Title: Bitstamp BTC withdrawal processing suspended Post by: AmazonStuff on February 11, 2014, 06:31:41 PM https://www.bitstamp.net/article/bitcoin-withdraws-suspended/
Title: Re: Bitstamp BTC withdrawal processing suspended Post by: adam9317 on February 11, 2014, 07:31:42 PM Not good!
Title: Re: Bitstamp BTC withdrawal processing suspended Post by: fonzie on February 11, 2014, 07:34:46 PM Stamp about to become Gox 2.0?
Title: Re: Bitstamp BTC withdrawal processing suspended Post by: adam9317 on February 11, 2014, 07:35:22 PM Stamp about to become Gox 2.0? You've probably just nailed it! Title: Re: Bitstamp BTC withdrawal processing suspended Post by: js1985 on February 11, 2014, 07:49:34 PM Stamp about to become Gox 2.0? I doubt it, they have been extremely professional and good support while mtgox are a wreck, also their fiat withdrawals are fine Title: Re: Bitstamp BTC withdrawal processing suspended Post by: BTCtrader71 on February 11, 2014, 08:30:59 PM Stamp about to become Gox 2.0? I doubt it, they have been extremely professional and good support while mtgox are a wreck, also their fiat withdrawals are fine I also doubt that stamp is about to become Gox 2.0, for the reasons stated above. However, this does lend a tiny bit more credibility in my eyes to the claim that Gox's tech problems are genuine, as opposed to a cover-up for insolvency. I certainly HOPE that is the case! Title: Re: Bitstamp BTC withdrawal processing suspended Post by: thecomputerscientist on February 11, 2014, 08:53:08 PM This malleability thing can be handled and I'm sure Bitstamp will fix it (a lot faster than MtGox).
The problem, I suspect, is how change is being handled. As outputs need to be fully spent, you normally produce a transaction with 2 outputs; the desired target address and an address with change that goes back to the exchange itself. However, that change needs to be frozen until the transaction becomes confirmed. Most exchanges probably thought that since it owns the private keys it should be safe to instantly reuse the transaction hash of the change for some other withdrawal, but due to malleability it is not possible to do so. To get good throughput the coins at an exchange probably needs to be split up in reasonable chunks. It all reminds me of how you implement malloc() in C with free lists for each bucket size. Instead of using a stack (for each free list) you should probably use a round robin strategy. Anyone being an expert in Bitcoin programming who wants to chime in here? |