4 ms·
I wonder when the error was detected? It's hard to tell, but it sounds like the man notified PayPal himself. But I wonder if he hadn't, how long would it take t
by danso 13y ago
I wonder when the error was detected? It's hard to tell, but it sounds like the man notified PayPal himself. But I wonder if he hadn't, how long would it take to trigger some mechanism in PayPal...I mean, aside from him trying to transfer an amount in the quadrillions)? Would some kind of flag go off, triggering a human doublecheck, if he started transferring quantities in the millions every other week?
Of course, this leads to the obvious question: whatever error-detecting mechanism would be triggered...why isn't it in place at the point which the $92 quadrillion transaction is credited? A simple "customer.balance < TOTAL_KNOWN_SUM_OF_WORLDS_CURRENCY" would seem to suffice
- icebraining 13y ago> Would some kind of flag go off, triggering a human doublecheck, if he started transferring quantities in the millions every other week? People have got their account suspended for transferring and/or receiving a few thousands. Pretty sure he wouldn't be able to transfer anything close to a million before lock down, unless he had clearance. In any case, it should be noted that the error only occurred in his email statement. At no point in time could he have touched the money, since "So he logged online -- and reality bit back. His account balance read $0." > Of course, this leads to the obvious question: whatever error-detecting mechanism would be triggered...why isn't it in place at the point which the $92 quadrillion transaction is credited? A simple "customer.balance < TOTAL_KNOWN_SUM_OF_WORLDS_CURRENCY" would seem to suffice Since it was only in the statement, it was probably an error in the reporting engine, and not in his actual account ledger.
- jaydub 13y agoSince it was only in the statement, it was probably an error in the reporting engine, and not in his actual account ledger. Oh summer interns
- jpdoctor 13y ago> Pretty sure he wouldn't be able to transfer anything close to a million before lock down, unless he had clearance. Unless he started working with someone on the inside of PayPal of course. ("Dear Respected One, GREETINGS, Permit me to inform you of my desire of going into business relationship with you. I got your contact from the PayPal accounting department, and I have the believe you are a reputable and responsible and trustworthy person I can do business with from the little information so far I gathered....")
- aleyan 13y agoWe once had an error that booked quintillions of dollars notional position with a client. It was caught the same night and the client never saw it. Here is how it happened. An end of day aging process was supposed to look at all positions marked "old" and trade into ones marked "new". Some positions may go through several transition until all the resultant positions are "new", so the process recurses until it finds a fixed point for the day. This day the aging process for this very bespoke trade went a bit haywire and instead of booking "-1 old position, +1 new position" it booked "+1 old position, +1 new position". Seeing that is still has +2 old position, the process booked "+2 old position, +2 new position", it then booked "+4 old position, +4 new position". This went on for 16 iterations until the auto breaks kicked in and stopped the process. A quant on watch saw the process fail and restarted it causing the positions to double 16 more times. This was billion dollar deal that grew by 2^32 times plus now existed in old and new variants for a total notional in quintillions of dollars. It was 7pm when the quant called me over because I was the only other guy still there and by happenstance I heard of similar issue happen on my old team. I fixed the position for the night but the permanent solution was made later in normal business hours. As an aside, when a similar error happened on my old team, the recursion continued until the process ran out of stack. That was when the 16 recursion limit was put in. (The position didn't grow huge that time because it was booking "+0 old position, +1 new position", so the growth was arithmetic and not geometric)