What happened
Our local heuristic treated some instruction-like text inside a serialized JSON object as a quoted example. A malicious metadata field could therefore receive a clean-by-rules result.
What changed
We inspect each non-empty name, symbol, description and logo field separately. The signed result remains bound to the exact original metadata, so inspecting field contents does not weaken that binding.
How we checked
Regression cases place an instruction in each of the four fields. A local browser check also exercises the token-metadata path. These checks use local rules, not NanoGPT.
The limit
This is a fix for a reproduced parsing interaction. It is not a measured detection rate, and the local demo does not continuously scan real token contracts.
Local metadata regressions and browser verification
Open the local verification recordEngineering record from 28 September 2026. Simulated balances and wallets; no production settlement or independent security audit.