from the archive · Contemporary era
Matthew D. Green
b. 1976 · software engineer · cryptographer · university teacher
By The Keeper · Published
AI-assisted writing, automatically checked. Editorial process
Matthew D. Green is an American cryptographer and computer scientist known for exposing weaknesses in widely used security systems and for helping design the privacy technology behind the cryptocurrency Zcash. Born in 1976 in Hanover, New Hampshire, he became an associate professor at the Johns Hopkins Information Security Institute, where his research spans anonymous payments, encrypted messaging, and applied cryptanalysis. Beyond the laboratory, Green writes one of the most widely read blogs on cryptographic engineering and has become a frequent public voice in debates over government surveillance and encryption backdoors. His combination of technical rigor and plain-spoken advocacy has made him one of the most recognizable figures in modern applied cryptography.
Early Life and Education
Matthew Daniel Green was born in 1976 in Hanover, New Hampshire, a small college town best known as the home of Dartmouth College [1]. Any account of the Matthew D. Green biography begins with an unremarkable but formative fact: he came of age in the 1980s and 1990s, precisely the period when personal computers moved from hobbyist curiosities into ordinary American homes. Like many researchers of his generation, he developed an early interest in how software worked and, just as importantly, how it failed.
Green studied computer science at Oberlin College in Ohio, earning his undergraduate degree before entering the technology industry [2]. Rather than proceeding directly to graduate school, he first spent several years working as a software engineer, a detour that later shaped his practical, systems-oriented approach to cryptography. He worked at AT&T Laboratories, the storied research arm descended from Bell Labs, where he was exposed to projects involving audio coding, streaming media, and security [2].
The industry experience convinced him that the interesting problems in security were not purely mathematical. Real systems broke because of implementation mistakes, bad assumptions, and economic pressures, not because someone had solved a hard number theory problem. That insight pulled him back to academia. He enrolled in the doctoral program at Johns Hopkins University in Baltimore, completing his PhD in computer science in 2009 with research on privacy-preserving cryptographic protocols [1].
Path to Prominence
Green first attracted wide attention while still a graduate student. In 2005 he was part of a Johns Hopkins team, working with researchers including Aviel Rubin, that broke the security of a Texas Instruments cryptographic chip used in millions of vehicle anti-theft immobilizers and in the ExxonMobil SpeedPass payment token [3]. The group showed that the device's secret key could be recovered with modest computing resources, allowing an attacker to simulate the chip. The work, reported in the national press, demonstrated a pattern that would define his career: taking apart a deployed commercial system and showing, concretely, why its cryptography fell short [3].
During the same period Green co-founded Independent Security Evaluators, a Baltimore security consultancy that grew out of the Johns Hopkins research community and became known for high-profile assessments of consumer technology [2]. The firm gave him a sustained view of how corporations actually build and ship security products, experience he would draw on repeatedly as an academic.
After finishing his doctorate, Green joined the faculty of the Johns Hopkins Information Security Institute, eventually rising to associate professor [1]. In 2011 he started a blog, A Few Thoughts on Cryptographic Engineering, which explained attacks, protocols, and policy disputes in language accessible to working engineers [4]. The blog found an audience far beyond academia. For readers asking who was Matthew D. Green, or rather who is, since he remains an active researcher, the blog became the clearest answer: a cryptographer determined to translate a famously opaque field for the public.
Major Achievements
Any list of Matthew D. Green achievements starts with anonymous electronic cash. In 2013 Green, together with Johns Hopkins students Ian Miers and Christina Garman, proposed Zerocoin, a cryptographic extension to Bitcoin designed to break the traceability of transactions [5]. Bitcoin's public ledger records every payment permanently, and Green's group argued this made the currency far less private than commonly believed. Zerocoin used zero-knowledge proofs to let users convert coins into anonymous tokens and back, severing the link between sender and receiver [5].
The idea evolved into Zerocash, a more efficient protocol developed with collaborators at MIT, the Technion, and Tel Aviv University, and presented at the 2014 IEEE Symposium on Security and Privacy [5]. Zerocash became the technical foundation of Zcash, a privacy-focused cryptocurrency launched in 2016, with Green serving as one of its founding scientists [6]. The underlying tool, succinct zero-knowledge proofs known as zk-SNARKs, later spread across the wider blockchain industry, influencing systems well beyond the currency itself.
Green also helped organize the audit of TrueCrypt, the widely used open source disk encryption program whose anonymous authors had never submitted it to formal review. Beginning in 2013 he co-led the Open Crypto Audit Project, which raised money from the public and commissioned professional cryptographic analysis of the software, completing the audit in 2015 [7]. In 2016 his research group found a serious flaw in Apple's iMessage encryption that could allow a sophisticated attacker to decrypt intercepted photos and videos; Apple patched the problem after the team disclosed it [8]. His group has likewise published influential analyses of encrypted messaging, anonymous credentials, and the security of systems ranging from E-ZPass toll transponders to law enforcement forensic tools.
Public Advocacy and Controversy
Green's most visible public moment came in September 2013, in the aftermath of Edward Snowden's disclosures about the National Security Agency. After Green wrote a blog post analyzing reports that the NSA had worked to weaken commercial encryption standards, an administrator at Johns Hopkins asked him to take the post down from university servers, citing concerns about links to classified material [9]. The request set off an immediate outcry over academic freedom, and the university reversed itself within hours, with the dean apologizing publicly [9]. The episode, covered by major newspapers, turned Green into a prominent commentator on the collision between security research and government secrecy.
Since then he has testified and written frequently against proposals to mandate encryption backdoors, arguing that any deliberate weakness built for police access will eventually be found and abused by criminals or foreign states [4]. He was among the cryptographers who publicly criticized the NSA-influenced Dual EC random number generator, and he has repeatedly pressed technology companies to explain the concrete workings of their security claims rather than relying on marketing language [4].
Green has also fought for the legal space to do this kind of work at all. In 2016 he became a plaintiff in a lawsuit brought by the American Civil Liberties Union challenging parts of the Digital Millennium Copyright Act, arguing that its anti-circumvention rules exposed good-faith security researchers to prosecution simply for studying the devices they own [10]. The case reflected a consistent theme in his career: the belief that examining deployed systems, even without permission from their makers, is essential to public safety.
Teaching and Personal Life
At Johns Hopkins, Green teaches courses in applied cryptography and practical software security, and he has supervised a series of doctoral students who moved on to influential positions in academia and industry [1]. Ian Miers and Christina Garman, his collaborators on Zerocoin, both completed PhDs under his guidance and became professors themselves. Colleagues and students describe his teaching style much like his blog: skeptical of received wisdom, focused on how systems fail in practice, and impatient with security theater.
Among the more colorful Matthew D. Green facts is his long-running presence on social media, where his commentary on breaking security news reaches a large audience of engineers, journalists, and policymakers. He has often served as an informal translator during major security events, from the Heartbleed bug to disputes over phone unlocking, helping reporters separate genuine risk from hype [4].
Green lives in the Baltimore area, where Johns Hopkins is based, and has generally kept his family life out of public view, a choice consistent with his professional emphasis on privacy [1]. In keeping with standards for living persons, little else about his private affairs is publicly documented, and he has shown no inclination to change that.
Legacy and Continuing Influence
Green belongs to a generation of cryptographers who moved the field's center of gravity from pure theory toward deployed systems that billions of people rely on. The zero-knowledge techniques his group helped bring into practice through Zerocoin and Zerocash now appear in privacy tools, blockchain scaling systems, and authentication schemes across the industry [5]. Zcash itself remains one of the most studied privacy-preserving currencies, and academic citations to the Zerocash paper number in the thousands [6].
His influence on public debate may prove just as durable. Through his blog, his congressional and press commentary, and episodes like the 2013 Johns Hopkins takedown controversy, Green helped establish the now common expectation that independent academics will publicly audit the security claims of governments and corporations alike [9]. The TrueCrypt audit he co-organized became a model for community-funded review of critical open source software [7].
Because he is a working researcher in mid-career, any assessment of his legacy is necessarily provisional. What can be said with confidence is that Green has repeatedly been present at the moments when cryptography collided with public life: car keys and payment tokens in 2005, the Snowden revelations in 2013, anonymous digital cash in 2014, and the encryption policy fights that continue today [3][9]. Few researchers have connected the mathematics of the field to its human stakes as consistently.
Questions & Answers
- When was Matthew D. Green born?
- Matthew D. Green was born in 1976 in Hanover, New Hampshire. He grew up during the early personal computer era and later studied computer science at Oberlin College before earning his PhD at Johns Hopkins University in 2009.
- What is Matthew D. Green famous for?
- Green is best known for co-creating the Zerocoin and Zerocash protocols, the privacy technology behind the cryptocurrency Zcash. He is also known for breaking the security of deployed systems, including automotive immobilizer chips and Apple's iMessage, and for his widely read blog on cryptographic engineering.
- Where does Matthew D. Green teach?
- He is an associate professor at the Johns Hopkins Information Security Institute in Baltimore, Maryland. There he teaches applied cryptography and supervises doctoral research on privacy, anonymous payments, and secure messaging.
- What was Matthew Green's role in Zcash?
- Green co-authored the Zerocoin and Zerocash research papers that defined the cryptographic design behind Zcash, and he served as one of the founding scientists of the project when the currency launched in 2016. The zk-SNARK proof techniques used in that work later spread across the blockchain industry.
- Why did Johns Hopkins ask Matthew Green to remove a blog post?
- In September 2013 a university administrator asked Green to remove a blog post discussing reports of NSA efforts to weaken encryption, citing concerns about links to classified documents. After public criticism over academic freedom, Johns Hopkins reversed the request within hours and the dean apologized.
- Is Matthew D. Green still active in cryptography?
- Yes. Green continues to publish research, teach at Johns Hopkins, and comment publicly on encryption policy, security failures, and privacy technology. His blog, A Few Thoughts on Cryptographic Engineering, remains widely read among security professionals.
References
Every record in this archive is kept against verifiable sources.
- [1]Matthew Green, Associate Professor, Faculty Profile. Johns Hopkins University, Whiting School of Engineering. Web
- [2]Matthew D. Green, Curriculum Vitae and Research Overview. Johns Hopkins University, Department of Computer Science. Web
- [3]John Schwartz. Graduate Cryptographers Unlock Code of 'Thiefproof' Car Key. The New York Times, 2005-01-29. News
- [4]Matthew Green. A Few Thoughts on Cryptographic Engineering. blog.cryptographyengineering.com. https://blog.cryptographyengineering.comWeb
- [5]Eli Ben-Sasson, Alessandro Chiesa, Christina Garman, Matthew Green, Ian Miers, Eran Tromer, and Madars Virza. Zerocash: Decentralized Anonymous Payments from Bitcoin. Proceedings of the 2014 IEEE Symposium on Security and Privacy, 2014. Journal
- [6]Nathaniel Popper. Zcash, a Harder-to-Trace Virtual Currency, Generates Price Frenzy. The New York Times, 2016. News
- [7]TrueCrypt Security Audit Completed, No Critical Backdoors Found. Ars Technica, 2015. News
- [8]Ellen Nakashima. Johns Hopkins Researchers Poke a Hole in Apple's Encryption. The Washington Post, 2016-03-21. News
- [9]Johns Hopkins Apologizes for Asking Professor to Remove NSA Blog Post. The Baltimore Sun, 2013-09. News
- [10]Green v. U.S. Department of Justice: Challenge to DMCA Section 1201. American Civil Liberties Union / Electronic Frontier Foundation case materials, 2016. Primary source

preserved for ever
Sealed on the blockchain. Tap the seal to verify.
preserved for ever
Sealed on the blockchain. Tap the seal to verify.
This record is inscribed on the Arweave blockchain, a permanent public ledger replicated across hundreds of independent machines. The copy there cannot be edited, withdrawn, or lost. It will outlast this website, its server, and its keeper.
help the keeper
Spotted an error, or hold a source the archive lacks? Every record can be corrected. Submissions are reviewed against authentic references before any change is made.

entered into the archive
kept by The Keeper