纪念比特币白皮书15周年之「考古」:我是如何在2011年获得比特币空投的?

Odaily星球日报Pubblicato 2023-11-01Pubblicato ultima volta 2023-11-01

Introduzione

在比特币白皮书发布 15 周年之际,我想分享一段私人的「数据考古」旅程。这是关于我如何在 2011 年获得比特币空投的故事,这其中还涉及到了知名的 Mt. Gox 被盗事件。

回顾整个过程,很可能是因为 Mt. Gox 用户被盗 2.5 万 BTC 后,科技媒体增加了对比特币的关注,然后我又在这个过程中关注到了这个事件并创建了第一个比特币钱包。

Google Reader & Dropbox:我的数据宝库

你可能听过很多关于「在某年买了某些比特币,但后来私钥丢了」的故事。但幸运的是,我很喜欢备份和存档数据,所以凭借着之前存档的数据,我把当年第一次创建比特币钱包、领取比特币的过程给还原了出来,甚至我还翻出了一些当时媒体报道的比特币的文章,包括科技媒体、果壳网、CoolShell。

对于一个发生在十多年前的事情,要复原它其实并不是这么简单。毕竟在这十几年中,我的笔记本电脑都换了很多台,就算我有经常备份数据的习惯,也可能会丢失很多数据,甚至连备份介质都不一定可靠(比如硬盘和光盘也都有其寿命)。

纪念比特币白皮书15周年之「考古」:我是如何在2011年获得比特币空投的?

而这次得以恢复数据,主要靠的是 Google Reader 和 Dropbox。Google Reader 是一个 RSS 阅读工具,当时我主要用它订阅一些科技媒体、设计和生活类的博客等。对于优质的内容我经常会用收藏功能,方便之后查阅。后来 Google Reader 在 2013 年 7 月停止运营,不过他们提供了数据导出功能,我就把我所有收藏的内容导出了,然后存在了 Dropbox 中。

之前还没想过这个数据会有什么价值,但是没想到被十多年后翻出来还是能找到一些蛛丝马迹的。

数据挖掘:追溯报道比特币新闻的足迹

我从个人的 Google Reader 存档文件中检索了所有与「BTC」、「比特币」、「Bitcoin」相关的数据,找到了近 10 篇相关的文章,目前仍有 5 篇可以访问。

最早的一篇: 2011 年 6 月 18 日

酷壳 CoolShell 的陈皓(又名左耳朵耗子,也就是今年 5 月意外去世的技术专家,他时常批评比特币)在一篇文章中提及比特币和其分叉项目 Namecoin

果壳编译发布 WIRED 的文章《比特币兴衰史》

为何创建比特币钱包

比特币在 2011 年时并没什么交易价值。当时,一些比特币爱好者为了推广和扩大比特币的影响力,创建了各种「水龙头(faucet)」网站,好奇的用户可以通过简单的操作,如填写验证码(抗女巫),免费领取一定数量的比特币(约 0.01 BTC)。

于是我当时也在寻找和浏览了一些水龙头网站后,成功领取了 0.01 BTC。 又因为备份数据的习惯,我也保存了这个比特币钱包的私钥文件至今。

后来当我把这个文件从硬盘中翻出,找出公钥和私钥,并通过区块浏览器搜索后发现,领取水龙头的时间是正好是 2011 年 6 月 18 日,也就是我收藏的那篇《黑客已经开始盗窃 Bitcoin 货币》文章的同一天。

其实 2011 年 6 月是一个很特殊的时间,正好是著名交易所 Mt. Gox 失窃的时间。

On 13 June 2011, the Mt. Gox bitcoin exchange reported some BTC 25, 000 (US$ 400, 000 at the time) had been stolen from 478 accounts. (Wikipedia)

包括上面 cnbeta 网站的文章中也提及了这次事件,所以很可能是因为 6 月 13 日的被盗事件让科技媒体增加了对比特币的报道,因此被更多人关注到。而我也因为这个负面事件,最终创建了比特币钱包并领取了比特币「空投」。

结局

虽然持有着这个地址的私钥,但我依然一无所有。哪怕至今持有这 0.01 BTC,也并不算什么。

根据区块浏览器来看,我这个比特币钱包中的 0.01 BTC 在 2013 年 11 月转出了,至于当时为什么要转出,以及转到哪里了,我暂时也没找到确切的线索。但我的确记得当年好像做过什么操作,可能是换钱包,或转去了交易所。

所以这其实是一个悲伤的故事,从 2011 年接触到比特币,到 2017 年再次关注和进入这个行业,已经过去了 6 年的时间。这件事对于我自己的启发是,或许我们现在还能有机会接触或瞥见一些极具潜力的新技术,但它可能真的需要更多的时间,才能被社会接受和理解,而我最适合做的就是继续保持好奇心,加上一点耐心。

Letture associate

U.S. Government Bans Foreign Nationals from Using Fable 5, Anthropic Issues Rebuttal

U.S. Government Bans Foreign Access to Fable 5, Anthropic Issues Rebuttal On June 12th, the U.S. government ordered AI company Anthropic to immediately suspend all foreign access—including foreign nationals within the U.S. and Anthropic's own foreign employees—to its newly released Fable 5 and Mythos 5 AI models, citing national security concerns. This forced Anthropic to temporarily disable access to both models for all users globally, as it cannot technically differentiate user nationality at scale. The models, released just three days prior, represent Anthropic's highest public capability tier. Fable 5 is the first publicly available model from the advanced "Mythos" family, while Mythos 5 is a less-restricted version for approved cybersecurity and critical infrastructure partners. The government's directive was reportedly triggered by claims from another company that it could "jailbreak" Mythos 5, raising alarm within the Trump administration. Anthropic, in a detailed public statement, strongly challenged this rationale. The company argues the demonstrated "jailbreak" is a narrow, non-generalized technique that merely involves identifying minor, known software vulnerabilities—a capability common to other publicly available models like OpenAI's GPT-5.5 and routinely used by cybersecurity defenders. Anthropic stated it has complied with the order but disagrees with the government's standard, warning that applying it industry-wide would halt all new frontier model deployments. The company criticized the lack of a transparent, fact-based legal process and expressed confidence the situation stems from a misunderstanding. It is working to restore access and will release more technical details within 24 hours. Other Anthropic models remain unaffected.

链捕手8 min fa

U.S. Government Bans Foreign Nationals from Using Fable 5, Anthropic Issues Rebuttal

链捕手8 min fa

The Revelation from the Raydium Theft Incident: New DeFi Vulnerabilities Lurking in Forgotten Old Contracts

**Raydium Exploit Reveals DeFi's Hidden Risk: Forgotten "Zombie" Contracts** A recent attack on Raydium's deprecated V3 AMM pools resulted in a loss of approximately $1.34 million. The hacker exploited pools that were no longer supported by Raydium's current UI or SDK but remained fully functional and accessible on-chain. This incident highlights a critical, often overlooked category of risk in DeFi: inactive or legacy smart contracts that projects fail to properly decommission. Since March 2025, there have been at least 8 publicly reported attacks targeting such abandoned contracts, with total losses around $10.8 million. Including older pools and deprecated features, the count rises to 10 incidents with roughly $22.5 million in losses. These "zombie contracts" represent a lifecycle management failure rather than a code vulnerability, yet they are typically misclassified under general "code bug" categories in security reports, masking the true scale of the problem. The root cause is that projects often merely document a contract as "deprecated" without taking essential technical steps to secure it: withdrawing remaining assets, disabling external call functions, and implementing ongoing monitoring. These forgotten, under-monitored components become prime targets for attackers. To address this, the industry needs to recognize "zombie contracts" as a distinct risk category and establish standardized decommissioning protocols. Essential steps should include: 1) a formal retirement announcement, 2) removal of all front-end integrations, 3) withdrawal of locked assets, 4) disabling key contract functions, 5) ongoing security monitoring, 6) clear user communication, and 7) a post-mortem analysis. The value of a DeFi project lies not only in its current TVL but also in the security of its historical codebase, which has now become a new attack surface.

Foresight News1 h fa

The Revelation from the Raydium Theft Incident: New DeFi Vulnerabilities Lurking in Forgotten Old Contracts

Foresight News1 h fa

Robots Begin to 'Consume Data': The Hidden Production Chain from Indian Data Factories to Billion-Dollar Humanoid Robots

Robots have started to 'consume data,' driving the formation of a new industrial supply chain focused on producing training data for embodied AI. Unlike large language models, which are trained on vast internet text corpora, embodied AI models face a 'data desert' in the physical world. This has created a massive demand for first-person perspective video data (Ego Data), captured by workers wearing cameras in places like Indian garment factories. Companies like Neocambrian AI are establishing 'data factories' where workers perform standardized tasks (e.g., sorting clothes, kitchen organization) to generate thousands of hours of video. Research, such as NVIDIA's EgoScale, demonstrates that scaling this human demonstration data predictably improves robot performance, particularly for dexterous manipulation. This has validated a training path combining large-scale human data for pre-training with smaller amounts of robot-specific data for fine-tuning. The value of different data types varies significantly, forming a 'data pyramid.' The base consists of low-cost, large-scale internet and Ego Data. Higher layers include more expensive motion-capture data (e.g., from data gloves), simulation/synthetic data, and the most costly and scarce layer: real robot teleoperation data. This demand has spawned a layered ecosystem of data suppliers: low-cost data factories, motion capture and alignment specialists, robot-native teleoperation service providers, simulation data companies, and platforms aiming for data standardization. Robot companies themselves are adopting a 'layered procurement' strategy: outsourcing generic Ego Data while building in-house capabilities for robot-specific adaptation data and the critical deployment/failure data generated in real-world applications. The industry is shifting focus from hardware and basic mobility to the data pipelines required for general-purpose capability. While parallels exist to data labeling companies like Scale AI in the LLM boom, the physical complexity of robot data—involving action success ambiguity and sim-to-real gaps—requires more integrated solutions for data collection, annotation, and a continuous feedback loop. The race is on to build the data engines that will teach robots to operate reliably in the unstructured real world.

marsbit4 h fa

Robots Begin to 'Consume Data': The Hidden Production Chain from Indian Data Factories to Billion-Dollar Humanoid Robots

marsbit4 h fa

Trading

Spot
Futures
活动图片