Published on 6 October 2026 by David
Every Hitchhiker carries a towel. Ours is a small program that holds your keys, says no on your behalf, and keeps the receipts. We call it the Towel. The software underneath it is OpenVTC, and this post is about why we chose it, where we mean to take it, and how to join in.
It is not a story about any one trial or any one place. It is about what our community needs from a thing like this, and why this particular thing fits.
The Question Every Act Raises
A Hitchhiker today does several kinds of work at once. They write on an open-source federated research platform, inspired in large part by federated wiki, often beside an AI that runs on a machine at home. They hold a name of their own, and the key that proves it. They give and receive hours in a timebank. Some of them hold an office in the mutual, with the right to sign for it.
Each of those acts raises the same five questions. Who is acting? For whom? As which identity? With what permission? And what is the evidence afterwards?
Most software answers none of them. An API key in a config file says nothing about who typed the command. A shared password says nothing about which steward used it. A chat transcript says nothing a verifier can check. We have been living on trust-me, and trust-me does not scale past a few friends.
Where Trust Went
The institutions we were taught to trust are losing it. In the United States, 17 per cent of people now trust the federal government to do what is right most of the time. In Britain, 45 per cent almost never trust a government of any party to put the nation before the party, up from 12 per cent when the question was first asked in 1986. Across the OECD, more people distrust their national government than trust it. The figures and their sources are on Trust in Government.
It is not only government. A decade ago technology was the most trusted industry in nine countries out of ten; now it leads in about half. In the United States, trust in the companies building AI fell from 50 to 35 per cent in five years. Two thirds of Americans say social media is harming their democracy, and half are more concerned than excited about AI in their daily lives, up from a third in 2021. The companies that asked us to trust them with our conversations, our photographs and now our thinking have the lowest standing they have ever had. More on Trust in Big Tech.
Underneath both, the ordinary fabric of trust has thinned. Robert Putnam called it bowling alone a quarter of a century ago: more people bowling, far fewer in leagues, and the clubs, unions and parent associations where strangers learned to rely on each other down by a third or a half. In 2023 the United States Surgeon General declared loneliness an epidemic affecting about half of adults. More on Bowling Alone.
Read together, the three are a triptych of trust. The OECD finds its single widest gap between people who feel they have a say in what happens to them and people who feel they do not. Trust has not vanished. It has retreated to where people can still see each other.
Squaring the Circle
The usual answers make it worse. One is more paperwork: more forms, more checks at every door, more documents to present. The other is more data: let the platform or the state watch everything, and call the watching trust. Both give the institution certainty about you and give you none about it. Both are why the trust left.
What we need looks impossible at first. An architecture that stops governments and companies mining our every movement, and at the same time lets us establish verifiable trust with large institutions and across a city or a country. Privacy pulls one way. Verification pulls the other. For most of history you could have one or the other.
There is a piece of mathematics that does exactly this, and it still feels like a trick the first time you meet it. A zero-knowledge proof lets you convince someone that a statement is true without showing them anything except the proof. You can prove you are over eighteen without revealing your date of birth. You can prove you are one of the forty-two members of a circle without revealing which one. You can prove a community vouched for you without handing over the document in which it did. The verifier finishes certain, and knowing nothing else.
The oldest picture of it is a friend who cannot tell red from green. They hold a red ball and a green ball, put both hands behind their back, swap them or not, and ask whether they swapped. You can see the colours, so you are right every time. After twenty rounds your friend is convinced the balls differ, though they still cannot tell which is which, and they could not convince anyone else, because your answers mean nothing to someone who was not there to pose the question. Certainty was transferred. Nothing else was.
That is the magic that squares the circle. The institution needs one fact. The person holds that fact and a great deal else. A proof carries the fact and nothing else across the gap. And because each proof is freshly made, two institutions comparing notes cannot tell they met the same person, and the community that issued the credential cannot tell where it was used. The tracking that every login button quietly performs is not restricted. It is impossible.
OpenVTC is designed to carry this in three strengths. The first lets you show one line of a credential and hide the rest, bound by a fresh signature from your own key so nobody can replay it. The second makes every presentation a new proof that cannot be linked to any other, so the same membership shown to the library and to the timebank leaves nothing to compare. The third proves membership and personhood while keeping a person uncorrelated across communities. Which strengths are switched on today, and which our lab has tested, is kept current on Zero Knowledge Proof.
Around the proofs sit the plainer parts, and OpenVTC is built from these too.
A key pair. You keep the private half and publish the public half. Anything you sign can be checked by anyone who holds the public half, and nobody can forge your signature without the private one. There is no password to share and no account anyone can lock you out of.
Identifiers you mint yourself. A decentralised identifier is a name derived from a key, not handed out by a registry. You can have as many as you need: one as a member, one as a steward, one for your AI. Nothing connects them unless you choose to connect them.
Credentials you hold. A community signs a statement about you, such as “this identifier is a member in good standing”, and gives it to you to keep. When you need to prove it, you present it, or a proof derived from it, to the verifier, who checks it against the community’s public key. The community is never called and never learns where, when or to whom you showed it.
Delegation as a signed object. A mandate is a credential too: this group authorises this person to do these things until this date. Anyone can check it, and it expires on its own.
Receipts nobody can quietly edit. Every action the Towel takes goes into a log where each entry carries the hash of the one before it. Change one record and the chain breaks for everyone who checks.
Put together, the verifier learns the fact and not the person. The issuer learns nothing about where the fact was used. The holder keeps the keys and the receipts. That is how trust can travel between strangers without a database in the middle. A community vouches for its members with its key. A federation agreement says which communities’ keys a council, a university or a ministry will accept. Verification is arithmetic that anyone can run, so it scales from forty-two neighbours to a nation without anyone having to be watched.
What OpenVTC Is
OpenVTC is an open-source project, written in Rust and published under the Apache 2.0 licence. It implements the Verifiable Trust Infrastructure specification from the Trust over IP Foundation. It ships two services.
The Verifiable Trust Agent holds one principal’s keys, identifiers, contexts, credentials, policies and audit trail. That is the Towel. The Verifiable Trust Community holds a community’s membership, roles, credential issuers and policy. One is agency; the other is association.
Every request to a Towel is a signed document, and the Towel decides under its policy whether to act. A policy can say that a particular act needs a human’s approval before the Towel will sign. That one feature is why we are here. It lets us make a rule and then enforce it: the AI never signs. The AI asks. The person approves. The Towel signs, and records both.
Why It Fits Hitchhikers
It runs at home. The Towel runs on a Raspberry Pi in a Hitchhiker’s own house, listening only to that machine. There is no cloud account behind it and nobody else holds a copy of the key. This is the same instinct as Your Right to a Name: the key lives with you, never with us.
It knows what a community is. Most identity software stops at the individual. We needed the community too. A mutual has offices, and an office that belongs to nobody can be used by anybody. With a Towel the office holds its own key, and its policy says when it signs: two of three stewards must ask, each signing as themselves. The office’s act is always traceable to people. Our rule follows from this. Every legal person in the federation has a Towel: each author, each author’s AI, each site, each office.
It keeps your lives apart. One person may be a member, a steward and an author. Those are different contexts in one Towel, with different keys, and a verifier who sees one cannot link it to the others. You can prove you are a member without showing which pages you wrote.
It refuses. We tested this on our own board. The Towel refuses to start if it has no identity. It refuses an unauthenticated request. When an AI agent asked to export a key, to read the access list, or to promote itself, it was refused every time, and every refusal is in the audit trail, chained so that nobody can quietly edit it.
We know what we are running. We built the same release twice, on two machines that had never met, and got the same binary to the last byte. We have the full list of its parts and a dependency policy that passes. That is a higher standard than we hold most of our own software to, and it is the standard this software has to meet.
We can give back. The code is open and the maintainers publish their own security review, including the gaps. We have drafted our first issues and one small fix. A commons that only takes is not a commons.
Where the Towel stands today, what has been tested, what has failed and what is still to build, is kept current on Towel Status. We publish the gaps because a Towel we oversold would be worth less than no Towel at all.
Join the Build
This is not a product launch. It is an open, iterative development process, and it is unfinished on purpose. The design is public. The lab notes are public, including the failures. The plan pages have checkboxes, and most of them are still empty. The code we build on is open, and what we learn goes back upstream.
There are four doors in, and each opens onto three wiki pages. Read and argue. Every judgement on the wiki is meant to be argued with, and a fork is the proper form of disagreement. Run a Towel. A Raspberry Pi at home is enough, and the lab wiki records exactly how we built ours and where it went wrong. Test it. The conformance matrix lists what nobody has tried yet. Bring a community. The first experiment needs forty-two people and one practical question, and Trust Without Tracking says what we would do with them.
Why a Towel
Douglas Adams wrote that a towel was about the most useful thing a hitchhiker could carry, and that a hitchhiker who knew where their towel was could be trusted with a good deal else. We did not pick the name for the joke. We picked it because that is exactly the test. Can you say, at any moment, who holds your keys, what they are allowed to do, and what they did? If you can, you know where your towel is.
See
- The triptych of trust: Trust in Government, Trust in Big Tech and Bowling Alone, or all three side by side
- Towel Status: where we are, what has been tested and what is still to build
- The four doors, three pages each: Read and Argue, Run a Towel, Test It and Bring a Community
- Zero Knowledge Proof: the arithmetic behind Squaring the Circle, and what OpenVTC has switched on
- Verifiable Trust Agent and Towel on the lab wiki
- Steel-Man the Towel and Where the Towel Breaks
- Every Site Is a Legal Person and The Journal Is the Receipt
- Towel Conformance Matrix, the Recovery Drill and What Would Make Us Stop
- Trust Without Tracking: what we would test with communities
- OpenVTC on GitHub and the Trust over IP Foundation
- Your Right to a Name