Topic: [ANN Mt.Gox] It’s been an epic few days: What happened? - page 2. (Read 4042 times)

The point is that when merely using UDP, unlike TCP, the source can block ALL incoming traffic which makes it immune to DDoS. As casascius points out, UDP is like a radio broadcast signal. TCP is like the postal service with delivery confirmation.

I don't think you understand how DDoS works on this level. Your UDP stream would have to have a source, which would have to have an IP, which then would get flooded to crap. It's the routers that pop, not the machines.

Also MtGox could take a position on my UDP streams idea, which could be any of the following without commitment:

a) Great idea, we haven't thought of it, and you're right, it would totally get information out immune to DDoS, we'll consider it but like anything else will take time
b) Great idea, but we don't agree it would work as well as you think it will, or for (specific technical reason) won't work on our platform
c) We haven't got a clue as to what this means
d) I don't have a clue what this means because I'm not a developer or tech guy myself, but I have relayed your suggestion to someone more technical, and he says (response).  (Hopefully this suggestion is more valuable than to merely forward it blindly like the latest facebook meme, since MtGox's reputation is suffering and this will actually solve the claimed issue at hand)

Just to be clear, using UDP to broadcast ticker data would be, for all intents and purposes, IMMUNE from DDoS attacks, because such a stream consists solely of outbound traffic which is not influenced by inbound traffic.  Unlike a normal stream, there is no inbound overhead for packets to acknowledge or to keep the connection in sync, packets which can be drowned out in a DDoS attack.  UDP is much more like a point-to-point radio broadcast: the signal gets sent from point A to B even if nobody's listening

Mt.Gox has been suffering from its worst trading lag ever, 502 errors, and at one point some users were not able to log in their account.

Thanks for the excellent feedback.

Mar 04 19:15:17 blu3gr1ffon ;;goxlag
Mar 04 19:15:22 gribble 106.133771 seconds

Mar 06 04:46:15 Ukto ;;goxlag
Mar 06 04:46:15 gribble 78.10124 seconds

Mar 06 05:17:03 Chaang-Noi ;;goxlag
Mar 06 05:17:05 gribble 456.476647 seconds

Mar 06 11:41:29 dub ;;goxlag
Mar 06 11:41:46 gribble 245.37453 seconds

Mar 07 01:58:34 kakobrekla ;;goxlag
Mar 07 01:58:37 gribble 471.638897 seconds

Mar 11 09:35:00 jurov ;;goxlag
Mar 11 09:35:01 gribble 2025.557307 seconds
Mar 11 09:35:10 jurov what is the record?

Mar 12 03:53:17 dub ;;goxlag
Mar 12 03:53:18 gribble 38.016469 seconds

Mar 12 04:12:36 smickles ;;goxlag
Mar 12 04:12:36 gribble 157.044926 seconds

Mar 12 04:23:10 gesell ;;goxlag
Mar 12 04:23:11 gribble 199.519792 seconds

Mar 29 00:34:07 Bitesaak ;;goxlag
Mar 29 00:34:07 gribble 288.72481 seconds

Mar 29 00:40:41 thestringpuller ;;goxlag
Mar 29 00:40:41 gribble 167.450794 seconds

Apr 03 09:24:23 ThickAsThieves ;;goxlag
Apr 03 09:24:24 gribble MtGox lag is 219.524796 seconds. During this time, light travels 0.439925233262 AU. You could have sent a bitcoin from the Sun to Mercury (0.39 AU).

Apr 03 11:50:16 dub ;;goxlag
Apr 03 11:50:16 gribble MtGox lag is 468.536678 seconds. During this time, light travels 0.938942256714 AU. You could have sent a bitcoin from the Sun to Earth (1 AU).

Apr 03 17:52:42 TomServo ;;goxlag
Apr 03 17:52:42 gribble MtGox lag is 6048.679827 seconds. During this time, light travels 12.1214866489 AU. You could have sent a bitcoin from the Sun to Saturn (9.54 AU).

Apr 03 18:03:07 thestringpuller ;;goxlag
Apr 03 18:03:07 gribble MtGox lag is 5455.751923 seconds. During this time, light travels 10.933265768 AU. You could have sent a bitcoin from the Sun to Saturn (9.54 AU).

I really hope so because to date both services have fallen well short of the mark in keeping users informed.

We, Coinlab & Mt.Gox, will announce something on this matter soon.

Prolexic sucks, they are resellers. Go with Black Lotus and make them agree to guaranteed uptime protection they'll do it. You could also clone a backup elastic cloud image on Amazon that ssh's to your secure db and switch to it whenever you get hammered beyond 10Gbps

Alex, you mentioned the verification issue.

It's really unclear to me what is going to happen with this when US/Canadian users get transferred to CoinLab.  Will the accounts which are currently awaiting verification still be verified by MtGox or will US/Canadian customers be verified by CoinLab following the transition (ie, will those US/Canadian customers currently awaiting verification by MtGox need to start the verification process again with CoinLab)?  

The lack of recent information about the transition is worrying as customers were initially told that they needed to agree to CoinLab's ToS if they wanted to use MtGox following the transition but the information on the CoinLab site says that the funds of US/Canadian customers will automatically be transferred to the US.  

This implies that people will need to withdraw their funds from MtGox before the transition if they don't want those funds transferred to the US bank (which may present difficulties for unverified customers given the backlog on verification) or they'll have to register as a CoinLab user whether they want to or not in order to withdraw their funds.

It was previously stated that MtGox user data would not be transferred to CoinLab without user agreement (ie, MtGox users accepting CoinLab's ToS), but if the funds are being transferred automatically then how will users be able to access them without using CoinLab?

I know you have a lot going on, but the transition to CoinLab has to the potential to be disastrous if you don't keep your users fully informed and - quite frankly - you don't need any more things happening right now which undermine people's confidence in you.

Thought the top was $147?

Dear Mt.Gox users and Bitcoiners,

It’s been an epic few days on Bitcoin, with prices going up as high as $142 per BTC. We all hope that this is just the beginning!