About
Hi, I'm Rick Dudley.
How do we assert that data has the provenance it claims, and how do we know a claim is correct? The environment keeps changing — a third party's server, a data provider, a language model — but the question doesn't.
I've been an IT consultant since 1999 and have worked on Ethereum since early 2015. I run Vulcanize, Inc. in New York City.
2026Making AI-written code accountable
Software written by a language model arrives with no independent account of whether it's correct. What I'm working on now: agreeing a specification with the person first, then establishing that the code meets it — so the result is trusted because it was measured, not because the model sounded confident.
2024Someone has to actually run it
Filecoin's developers needed a way to query their network's history and the standard tooling didn't work there. My company, Laconic, identified the software issues and provisioned the hardware required to fix the integration. We became the first subgraph provider to the Filecoin ecosystem.
2023Keeping score without a referee
Two parties who transact repeatedly shouldn't need a third to keep score. Laconic designed and built implementations of multi-party state channels, one written from scratch to run in a browser, so participants exchange thousands of updates privately and settle once on a public ledger — with neither side able to lie about what happened in between.
2022Code is not law, law is law
I was one of the contributors to a model law that gives decentralized organizations legal personality — drafted by an international working group of lawyers, academics and engineers, and presented at the UN's Internet Governance Forum. Where it could, it replaced a legal obligation with a technical guarantee that does the same job.
2021Verifiable data as a product
I founded a company to sell the 2017 idea properly. Its clearest result: one of the most widely used cryptocurrency wallets shipped an anti-phishing tool on my software, making it cheap enough for anyone to run a trustworthy copy of a list that had previously required trusting whoever published it.
2019Rewriting how blockchains charge their users
I was one of six authors of a change to Ethereum's transaction pricing. It took two years of public argument to pass, now governs every transaction on the network, and has been copied by most of its competitors.
2017An index that can prove itself
Most blockchain data tools read the events a developer chose to publish. I built one that captured raw state changes instead, so a query returned a result you could check rather than believe. It ran as the data layer for one of the largest financial applications on Ethereum.
2007A patent on moving property between untrusting parties
I filed a patent on a way to move virtual goods between different companies' servers, so that any of them could verify, item by item, which changes were authorized and which were forged. It went in nineteen months before the Bitcoin paper, and largely anticipated cryptographically secured digital assets. Game publishers working on the same problem have cited it since.