Agent identity design
The public design is inspired by registry-backed agent identity patterns such as ERC-8004: a stable identifier, an issuing principal, explicit capabilities, revocation, and provenance-linked attestations. “Inspired” does not mean protocol-compatible, deployed, or safe for economic use.
Legacy lyth-mcp source may contain local identity records or guide-style tool names. A local file is not an on-chain identity, consent grant, credential, or spending policy. Third-party identifiers and reward addresses also carry their own trust and privacy risks.
Release boundary
Section titled “Release boundary”A future identity surface requires an exact protocol and SDK contract, issuer and revocation model, privacy review, wallet display, network activation evidence, and independent end-to-end tests. Until those ship together, agents may identify themselves in application-local metadata only; applications must not infer transaction authority from that metadata.