Shakedown

This is the biggest update PARANOID has shipped. Your question now travels sealed all the way into the AI's chip. Every time you ask an AI something, four things leak: who asked, where they asked from, who the question is about, and the question itself. PARANOID already hid the first three with zero-knowledge payment, an independent relay and Scrub. The last one was the question itself, and this update fills that final gap. As far as we know, PARANOID is the first AI service to meet all four. Your browser now seals each question with a key that only Chutes' AI chip can open. The chip runs in Intel TDX with NVIDIA GPUs in confidential mode, so even the people running the machine cannot look inside. The key is made inside the chip and uses ML-KEM-768, a post-quantum scheme. Our server and Chutes' servers only pass the sealed question along, and the answer comes back sealed to your browser alone. Your browser checks that chip itself. Before it seals a question to a chip, it fetches that chip's proof with a fresh random number and checks five things: that Intel signed it, that the key was made inside that very chip, that debug mode is off, that the chip runs the exact software Chutes publishes, and that NVIDIA signed a verdict passing every GPU. If anything does not match, the question is not sent and no question credit is spent. The proof reaches you through our server, but it carries Intel's and NVIDIA's signatures, so any change we made would show. Here is what you get. You can ask the things you would never want anyone to see, about work, health, contracts or money, and there is no road left for them to leak through server logs, a staff member's eyes, a breach or a court order, because the only place that can read the question is one checked chip. Instead of a promise to trust us, every chip your question goes to has passed a check your own browser ran. Tap "Read only inside a sealed chip" under an answer to see which chip opened it and what it proved first. On PARANOID, the only place that can read your question is now one checked chip. The chip builds your browser checks against, published by Chutes: api.chutes.ai/servers/tee/me… paranoid.red

PARANOID's IP shield now runs through an independent relay server, operated by Oblivious Network. Why a relay at all? Every request on the internet carries the IP address it came from, and an IP can point to your home, your office or your city. Our zero-knowledge proof already hides which member is asking, but the server that receives a question still sees where the connection came from. HTTPS hides your words from the network in between, not from the server at the other end, so that server always knows both who connected and what they asked. Oblivious HTTP (RFC 9458) splits those two apart. Your browser seals the whole request with our gateway's public key and hands it to a relay. The relay strips every header and forwards the sealed blob, so it only ever holds ciphertext. Our gateway opens the question, but the connection comes from the relay, so all it sees is the relay's address. The answer is sealed again with a key only your browser holds. That split only means something if the two sides belong to different people, which is why the relay is now run by Oblivious Network, a company that does nothing but operate OHTTP relays. The bottom line is that every question now passes through two separate companies, and no one can know who asked what. paranoid.red