Independent record. Not associated with, endorsed by or operated by Binance. This site is read-only: there is nothing to sign in to, pay for or connect.

All sources

Hacker News comment

Publisher
Hacker News (Social media)
Original
https://news.ycombinator.com/item?id=50303172
Published
First seen
Last captured
Watched for edits
No

Capture history

Newest first. The raw hash is the SHA-256 of the stored copy exactly as fetched. We keep the copy privately and publish its hash. The text hash is of the text extracted from it, which is what is compared between captures.

Captured (UTC)Fetched viaHTTPRaw sha256Text sha256Text changed
http20021dfaf0a7ed09b192f6a8540be9ec7ed4f8eb7f78edd9993da4f2ccec5ab36b51ba80ef91d08d7a16c383e40e71dd7788a61054cecd54409b1bc6023b54d61a8No

Changes between captures

No text changes detected between captures of this source.

Claims quoted from this source

Theoryroot causeStatement 1101

A Hacker News commenter suggested that the speed of the transfers indicated that either some or all of the attack was automated or the attackers had prepared in advance with some inside knowledge of Binance architecture.

I disagree. Assuming the start of the timer is when they first encountered Binance systems they moved very quickly to make the transfers. It suggests to me either some or all of this was automated or they had prepared in advance with some inside knowledge of Binance architecture.

Speaker
Not recorded
Publisher
Hacker News (Social media)
Original
Hacker News comment
Captured
Stored copy
sha256 21dfaf0a7ed0
Published