Loops HouseProvenExit

NEAR HACKATHON
Team
1 member- EROwner
Erhan Türker
Overview
Every VPN says "no logs", and users just have to trust it. ProvenExit makes that promise checkable.
The VPN exit runs inside an Intel TDX machine (Phala Cloud). Before any traffic leaves the user's machine, the client asks the exit for a fresh Intel-signed proof and checks 20 things: Intel's signature and TCB status, debug mode off, the exact build that is running, and that the exit's keys are bound to the proof.
NEAR is where trust lives. A registry contract on NEAR verifies Intel's attestation on-chain when an exit registers (13 checks), keeps the list of approved builds and operators, and has no access keys; its owner is a 2-of-3 council DAO. The client asks the registry before every connection: if the council revokes a build, or anyone changes one line of the exit's code, the next connection is refused before a byte is sent.
It is not one VPN but a check any VPN can pass: any approved operator can run an exit, and two-hop routing across different operators is built in. AI agents can use it through an MCP server (verify, then fetch through the exit).