What is real is smaller and, I think, more interesting. oConsent is an idea from a 2022 paper with a working reference implementation: a way to record consent as a signed, independently timestamped agreement, anchored on a public chain, that anyone can verify later without trusting the company that collected it. The lifecycle works. The signatures work. The timestamping works. The contracts have tests. You can run the CLI today.

So I rebuilt the site to say that, and only that.

Why bother being this blunt

Because the entire pitch of this project is that you should not have to take a company’s word for what you agreed to. A site for that project, full of claims you have to take on faith, is self-defeating. The new status page lists what is built, what is half-built, and what does not exist yet, including the part the old site leaned on hardest: the zero-knowledge proofs are a placeholder right now, not the real thing. The code admits it in a comment. Now the site does too.

There is a smaller tell worth mentioning. This site uses cookieless analytics, sets no cookies, and serves its own fonts, so reading it does not feed you into anyone’s tracking. That should be the baseline for a privacy project, not a feature.

What I want help with

This needs contributors more than it needs an audience. The most useful thing you can do is read how it works, then try to find the case where the record proves nothing. After that, the open problems are concrete: real zero-knowledge proofs, support beyond Ethereum, finishing the licensing, and better docs.

If any of that sounds like your kind of problem, the code is here and the contribute page tells you where to start. If you just want to follow along, the RSS feed is the no-tracking way to do it.