Who actually verifies the verifier? That was my biggest question about zkTLS. If the attestor signing your web proof can cheat, the whole setup falls apart. Look at how @primus_labs handles this: • Attestor nodes run inside Phala TEE, isolated so even node operators cannot tamper with them • Every proof includes a verifiable TEE quote that anyone can check independently • The nodes are registered directly across contracts on Base, HashKey Chain, and Ink Most people talk about hiding data, but making sure the middleman cannot fake signatures is just as critical. Are TEE secured attestors the best fix for Web3 data trust?