16 karma · joined November 17, 2025
A simple example for the computation: It’s like placing boxes next to each other. Yes I could say 1 box + 3 boxes = 4 boxes, via explicit calculation. I could also simply place 1 box next to three boxes, and without having to explicitly calculate, by nature of the interaction, the result (4 boxes) has been produced
There is no background computation or storage. The universe IS computation and storage. Each spacetime quanta IS storage, and each interaction IS computation.
1. The site does not know who you are. This is the whole point. You generate a mathematical proof you possess a valid government ID that says “age >= n”
2. Yes. You are generating a zkp based on information anchored by the attester. In this case the ID issuing gov. That attester can be something other than a gov, but zkps are a bit useless if the site doesn’t know what exactly is being proved. In this case you are proving “I possess a government ID saying age >=n”. You must know about the government to care about this proof.
3. Not in this case. The attester only knows it has issued you an ID, but does not need to be further consulted. You could certainly construct a scheme such that you require a ZKP of recent written permission from some entity, but this is not inherent to ZKPs.
4. This is a UX question. If the ZK wallet and website are implemented in such a way that it’s always displayed when a credential is requested and what credential that is, then yes.
Regardless of the lack of vote, non-voting children are still governed by elected officials, giving them legitimate reason #3 to interact with politics, even if they can’t do so in the form of a vote yet.
You’ve picked a poorly thought out hill to die on.
What a strange non-fact to include.
In any case, this is cool that you built these tools, but I think it’s important to understand that this is technically not different than any other time you’ve used a cloud based LLM. LLMs are stateless, and every interaction feeds in the full context (or truncated summary) of your entire conversation. In that sense, your first prompt may go to data center A, and your second prompt may go to data center B, where A and B are many miles apart, and it’s no different than both prompts going to A. The LLM didn’t “teleport” from A to B, because LLMs are stateless and ephemeral. Anthropomorphizing LLMs is a bit disingenuous, because it’s not a stateful being.
Again, it’s cool you restored context automatically in a claude code session. In the web UIs for popular LLMs, you can typically see conversation history and resume across machines, it’s a shame this isn’t built into Claude code by default.