Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Which begs the question of whether it was accidentally early.

It may well be that the 'early' trader knew they weren't the only one with early access to the data and intentionally set their trades to be a tiny bit early, to increase their chances of getting out ahead of the people who schedule their trades for just-after the scheduled announcement.

Which may well indicate a larger problem than one guy with a tip.



Couldn't it also just be clock skew on a host or local datacenter which set off a chain reaction?

I mean, I know that traders are probably pretty anal about accurate clocks, but mistakes do happen.


> "mistakes do happen."

Absolutely. I'm just saying there isn't much justification to assume it was a mere mistake.

Particularly given the trades that show up just after the report was released, but before a person could conceivably process them and initiate the relevant strategy.

That alone suggests gamesmanship, even if the "early" trader went earlier than he meant to.


> Particularly given the trades that show up just after the report was released, but before a person could conceivably process them and initiate the relevant strategy.

Couldn't they be trading based on some natural language processing algorithm?


Could be. Are those sufficiently advanced that anyone would be confident-enough to wager amounts, based on their results, of the order at issue here?




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: