Crypto and blockchain
Crypto and blockchain is the work of running shared digital ledgers, records that many computers keep in agreement without a central keeper, and the currencies, tokens and services built on them.
2009
On 3 January 2009 at 18:15 UTC the first block of Bitcoin's ledger was created, carrying the line "The Times 03/Jan/2009 Chancellor on brink of second bailout for banks". On 8 January Satoshi Nakamoto announced the first release of the software, "a new electronic cash system that uses a peer-to-peer network to prevent double-spending".
34
Milestones achieved across 6 domains.
11
To watch for: announced, not yet confirmed outside.
13
Open deliverables. Nobody has shipped them.
In one minute
Where it started
In 1991 Stuart Haber and W. Scott Stornetta showed how to chain records together by hash, a short digital fingerprint, so that no earlier record could be changed unnoticed. In 2008 Satoshi Nakamoto joined that idea to proof of work, a costly computing race, to make Bitcoin, a ledger anyone can help keep. In 2015 Ethereum added smart contracts, programs on the ledger that hold and move funds, and exchanges, wallet devices and stablecoins (tokens meant to stay at one dollar) grew up around both, along with a run of thefts and collapses from Mt. Gox in 2014 to FTX in 2022.
Where it stands
The US Securities and Exchange Commission approved spot bitcoin funds in January 2024, the United States passed a law for stablecoins in July 2025, and Hong Kong licensed its first two stablecoin issuers in April 2026. Losses have grown alongside: Americans reported $11.4 billion of crypto-related fraud to the FBI in 2025, by The Block's reading of the FBI's report, and Chainalysis counted $3.4 billion stolen from the industry that year, at least $2.02 billion of it by North Korean hackers. In July 2026 the FATF, the global standard-setter against money laundering, found only one of 149 jurisdictions fully compliant with its rules for crypto firms.
What is open
Many of the industry's headline numbers come from the firms that make them: how fast a block can be proven, whether an exchange holds what it owes, what a wallet screen shows before a user signs. The open jobs are outside tests and public records: wallet screens filmed against known attack transactions, exchange reserve checkers fed planted faults, AI auditors scored before contest results are out, and registers of chain halts, stablecoin reserves and frozen coins that this research found nobody keeping.
Domains
AchievedWatch forOpen
Domain
Progress
Last achieved
Watch for
Open
Ledgers and agreement
This is the work of keeping one shared record of who owns what, copied on many computers that agree on each new entry without a central keeper.
6 · 3 · 3
Last achievedSpeed claims measured2023
Watch forFinality in 150 milliseconds
3
openWallets and custody
This is the work of holding the secret keys that control coins, whether owners keep them on their own devices or a firm holds them for customers.
5 · 1 · 2
Last achievedSigners approve a theft2025
Watch forWallets that show intent
2
openExchanges
This is the work of running markets where coins and tokens are bought and sold, either by firms that hold customers' assets or by programs on a ledger.
7 · 2 · 2
Last achievedNineteen billion in a day2025
Watch forSpot crypto on futures exchanges
2
openStablecoins and payments
This is the work of issuing tokens meant to keep a steady value, usually one US dollar, and of paying with coins and tokens.
5 · 2 · 2
Last achievedA US law for stablecoins2025
Watch forRules for US issuers
2
openSmart contracts
This is the work of writing and checking programs that run on a ledger and hold or move funds by fixed rules, such as trading pools, lending pools and bridges between ledgers.
5 · 2 · 2
Last achievedA bridge emptied2022
Watch forAI agents that exploit contracts
2
openFraud and regulation
This is the work of setting and enforcing rules for crypto firms, and of tracing and stopping theft and scams.
6 · 1 · 2
Last achievedScam proceeds seized2025
Watch forA US market structure law
2
open
Advances to build with
2 research notes

Gemini 4 Carbon
Cyber defenders first
Google says cyber defenders got Gemini 4 Carbon first, and its 88.2% flaw-finding score is Google's own run on a 183-task subset with guardrails off.

Muse Ember
The jobs agents repeat
Meta's Muse Ember matched Claude Haiku 5.5 on an outside firm's tests at a third of the cost per task, though both list the same prices for text in and out.
Open in crypto and blockchain
3 of 13 open deliverables
Open · Ledgers and agreement
A register of chain halts
An open dataset of every time a major public chain stopped adding or finalizing blocks, found from the chains' own block times (any gap far beyond the normal interval), for the 30 largest chains since 2015. Each halt is matched to the chain's post-mortem and its cause coded: software bug, spam, consensus fault, upgrade or other.
Built with what exists
Public RPC endpoints and block explorer APIs for block times; DuckDB or pandas to find the gaps; an AI model to read post-mortems and propose cause codes, each checked by a person (see the Note "The jobs agents repeat").
Open · Wallets and custody
Signing screens put to test
A public set of 50 test-network transactions, each modelled on a known attack: a multi-signature wallet upgrade like the one behind the Bybit theft, unlimited token approvals, off-chain "permit" signatures and account delegations. Sign each on 10 hardware wallets and 10 software wallets, film what every screen shows, and have two raters score whether a careful user could tell what the transaction does.
Built with what exists
The Sepolia test network and faucet ether, so no real money moves; Foundry for building transactions; Safe multi-signature contracts deployed on Sepolia; ERC-7730 descriptions from clearsigning.org; a camera; a written scoring rubric.
Open · Exchanges
Reserve checkers given planted faults
Exchanges prove they hold customers' coins by publishing a Merkle tree, a structure that lets each customer check that their own balance is counted in the total. Build synthetic customer-balance data with known faults planted in it (a negative balance hidden in the tree, a customer left out, two customers sharing one ID, a shortened hash), run each exchange's published verification tool on it, and record which faults each one catches.
Built with what exists
The verifiers exchanges publish as open source; Python to generate balance trees; the 2022 paper's classes of fault as the test plan. No real accounts or money are involved.