Credit
The Independent 100 list was curated by dan (@irl_danB) and published on 2026-09-24 at independent.prose.md (announcement). The ranks and section names are his, and number 100 is his open wild-card slot. This study is ours and is not endorsed by him or by anyone on the list.
What they publicly do
Technologist in security and cryptography. He co-founded and chairs Alliance for the Future, a Washington, D.C. AI-policy nonprofit [Reported: thesohoforum.org/upcoming-events/2026/1/27/perry-metzger-vs-brian-merchant; x.com/perrymetzger/status/1767521624012509240]. He created the Cryptography mailing list where the Bitcoin whitepaper was first posted [Reported: ludlowinstitute.org/board-of-advisors] and co-authored 1995 IPsec ESP RFCs, including RFC 1829 [Reported: researchr.org/alias/perry-metzger].
- X profile: x.com/perrymetzger
- Also: x.com/perrymetzger
- Also: reason.com/podcast/2026/01/30/will-ai-benefit-everyone
Public work
- Alliance for the Future other no license stated last activity 2026-09-24
An AI-policy nonprofit announced in 2024 with him on the board [Reported: announcement on X, Soho Forum speaker page].
- Soho Forum debate with Brian Merchant talk no license stated last activity 2026-01-27
A January 2026 public debate on AI [Reported].
- RFC 1829: The ESP DES-CBC Transform paper no license stated last activity 1995-08
A 1995 IPsec specification co-authored with Phil Karn and William Allen Simpson [Reported: researchr].
- Post on a Lean result about ZF consistency other no license stated last activity 2026-09-22
A 2026-09-22 post saying that Lean's core type theory with excluded middle but without choice proves ZF consistent, a result he says was found with AI [Verified: post exists; the mathematical claim itself was not verified].
Licenses of GitHub repositories are from the authenticated GitHub license API on 2026-09-25, one row per repository in evidence/licenses.jsonl (“no license file” means the API found none; “license file present, not recognised by GitHub” means GitHub could not classify it). Other licenses are as the source states. Check the license file before reusing anything.
Relevance to our work
2 of 5 lenses: security, verification
Context for AI-policy debate, plus a long record in cryptography standards. Nothing here is adoptable as a tool. The Lean post is a pointer to AI-assisted formal results, but it is secondhand.
Scored 0 to 5 against the study’s relevance rubric: 5 means public, openly licensed work squarely in our lanes that we could study or adopt now, and 1 means little connection to our work. The score is one reviewer’s judgement of how much this public work bears on our own work. It is not a ranking of people and says nothing about the person or the quality of their work.
What we would study next
- Trace the Lean/ZF-consistency claim to its primary source before citing it in any verification work (x.com/perrymetzger/status/2102535036838838755). If true and reproducible, it is an example of AI-found formal results, relevant to AI-assisted Lean proof work. As it stands it is an unsourced social post. Effort: small.
Before reusing anything: No code or licensed artifacts were found. His X posts include sharp criticism of named individuals; nothing from those is used here.
Sources
- thesohoforum.org/upcoming-events/2026/1/27/perry-metzger-vs-brian-merchant
- ludlowinstitute.org/board-of-advisors
- researchr.org/alias/perry-metzger
- x.com/perrymetzger/status/1767521624012509240
- x.com/perrymetzger/status/2102535036838838755
Overall confidence in this record: Medium. Sources were read on 2026-09-24 and every link was checked on 2026-09-25. The full record is line 10 of people.jsonl.
Limits
Not verified: Any current GitHub or code work (no account was found under 'perrymetzger'). The primary source for the Lean/ZF claim. The rfc-editor page for RFC 1829 was not opened.
This record comes from a first-pass survey of public material by an AI agent session on 2026-09-24, edited for publication on 2026-09-25. Nothing was installed or run for it. Roles, stars and licenses change; see the study’s limits.
Request a correction
Is something about this record wrong or out of date, or would you rather not be covered? Open a correction (a GitHub issue form with this page’s address filled in). A request to remove a record is honoured without argument; accepted corrections are recorded in the changelog with the date.