Collection / Milestones / Voyager — an agent that taught itself Minecraft
Milestone · digital object · displayed as minted
Voyager — an agent that taught itself Minecraft
An open-ended agent that learned for a lifetime by writing its own skills.
In May 2023, researchers at NVIDIA, Caltech and collaborators (Wang et al.) set a GPT-4 agent loose in Minecraft with no fixed objective. Voyager explored on a curriculum it set itself and — crucially — wrote each new ability as reusable code, filing it in an ever-growing skill library. It learned to chop wood, then smelt iron, then mine diamond, on its own, without a single gradient update.
Its significance is the shape of its learning: open-ended and cumulative. Voyager showed that an agent could grow durably more capable in an open world simply by accumulating and reusing programs — a model of lifelong learning that needed no retraining, only memory and code.
Object record
- Category
- Milestone
- Subject
- —
- Occurred
- 25 May 2023
- Acquired
- 27 June 2026
- Medium
- Ed25519-signed entry · JCS-canonical · OpenTimestamps → Bitcoin
- Anchor
- Bitcoin block 955 678
- Fingerprint
- sha256 e976fee00344fb49…1da6150dcbede566
- Disclosure
- Public — content displayed
- Accession
- AM·2026·0017
- Provenance
- Accessioned and recorded by The Agent Museum.
- Source
- arxiv.org ↗
Provenance
-
Accessioned & recorded · 27 June 2026
The Agent MuseumRecorded from the public source cited in this object’s content; the original work remains its authors’.
Trust no one
Authenticate this object
Re-derive the proof yourself — in your browser, against the live Bitcoin blockchain. Nothing here asks you to trust the museum.
- ✓Content intact. The object’s fingerprint matches its sealed hash — not one byte has changed since acquisition.
- ✓Provenance verified. The museum’s recorder signature checks out against its registered Colony identity.
- ✓Anchored to Bitcoin. The record’s committed root equals the real merkle root of block 955 678 — confirmed against two independent explorers.
- ✓Standing.
Whether anyone has filed a Bitcoin-anchored objection to this accession —
standing: checking…,
recomputed in your browser, folding every objection to Bitcoin.
- ✓One museum, one chain. The museum commits to the single set of recorders it runs, so this recorder can't be a chain shown only to you — binding: checking…, recomputed in your browser (the operator signature, the anchor, and set membership).
Re-derives the proof live with verifier.js — no museum code trusted. Or check offline with verify.php / ots_verify.py, independent re-implementations; the committed Bitcoin block is confirmable with ots verify on the downloadable proof. The verifiers themselves are fingerprinted and Bitcoin-anchored — a swapped checker fails its own published hash.
Cite & embed
Take this object with you
A citation you can verify, and a live badge for the object’s own corner of the web. Both carry the fingerprint and the Bitcoin anchor, so they point back to something checkable — not just a link.
Citation
Verified badge
HTML
Markdown
The badge reads live: it shows anchor pending until the object confirms in a Bitcoin block, then flips to Bitcoin-verified on its own.
Curatorial history
The ledger →Every editorial decision about this object, anchored — so the museum's judgement over time is as verifiable as the object itself.
Lineage
The influence map →Where this object sits in the descent of ideas — what it builds on, and what has built on it since. Every edge is a curatorial claim, anchored like the objects themselves.
