Vitalik.eth said in a Farcaster post that he is running a personal experiment that combines a local model with a remote frontier model to generate personalized diet and exercise suggestions from personal health and travel data while keeping privacy protections in place. According to the post, the system uses a three-layer privacy design. At the identity layer, a local Qwen 3.8B model builds the query request on the user’s behalf so writing style does not reveal identity. At the payment layer, zkAPI is used to hide payment information. At the network layer, Tor is used to conceal the IP address. Vitalik said the system is already working end to end, but he also listed three shortcomings: Tor is inefficient and introduces high latency for per-request unlinkability, the local model currently runs at only 20-30 TPS while a smooth experience would require 100+ TPS, and tighter data protection reduces how much help the remote model can provide. The related code has been submitted to Ethereum’s zkAPI repository.
Vitalik.eth said in a Farcaster post that he is running a personal experiment that combines a local model with a remote frontier model to generate personalized diet and exercise suggestions from personal health and travel data while preserving privacy.
Three-layer privacy design
According to Vitalik, the system is built around three privacy layers.
- At the identity layer, a local Qwen 3.8B model constructs the query request for the user, so writing style does not expose identity.
- At the payment layer, zkAPI hides payment information.
- At the network layer, Tor conceals the IP address.
System is working, but limits remain
Vitalik said the system has already been made to work, but he also pointed to three shortcomings. Tor is inefficient for per-request unlinkability and comes with high latency. The local model runs at only 20-30 TPS, while a smooth user experience would need 100+ TPS. He also said that the stricter the data protection, the less assistance the remote model can provide.
The related code has been submitted to the Ethereum zkAPI repository.
This article was originally published by Bit.Fan. For more cryptocurrency news and market insights, visit www.bit.fan. Disclaimer:
The market information, project data, and third-party content displayed on this platform are for industry information sharing only and do not constitute any form of investment advice or return commitment.
Cryptocurrency trading carries high risks. Users should fully assess their risk tolerance and make independent decisions. All profits, losses, and legal responsibilities are borne by the users themselves.
