Could draft clarify two verificationTier rules before Review?
registerAgent() accepts an initial tier, but permission to register an identity may differ from permission to issue verification. Could a caller register at tier 4 without satisfying the checks required by updateVerificationTier()?
I would suggest requiring either:
Registrations MUST start at tier 0 and promotion uses updateVerificationTier()
Non-zero initial tiers MUST satisfy the same authorization and evidence requirements as later promotions
I prefer the first for separate audit transitions.
Also, how does VerificationTier.validityPeriod affect isVerified()? It’s documented as verificationTier > 0, while AgentIdentity exposes no dedicated verification timestamp or expiry. Should expired Gold verification still return true until explicitly downgraded?
A dedicated timestamp or expiry, with defined effective-tier semantics, would help. Reputation updates to lastUpdate should not renew verification. I would suggest making this invariant explicit: a non-zero effective tier means an authorized verifier issued or approved it and the verification has not expired.
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | ERC-8419: Know-Your-Agent (KYA) Framework | 0 | 9.74 | 19-10-2026 |
| 2 | ERC-8107: ENS Trust Registry for Agent Coordination | 0 | 9.8 | 18-10-2026 |
| 3 | ERC-8434: Agent Identity (AID) | 0 | 9.38 | 19-10-2026 |
| 4 | ERC-8126: AI Agent Verification | 0 | 13.06 | 17-10-2026 |
| 5 | ERC-8414: Token-Bound Task Tenders | 0 | 9.19 | 19-10-2026 |
| 6 | ERC-8004: Trustless Agents | 0 | 5 | 10-07-2026 |
| 7 | EIP-TBD: Resolution — Non-Self-Authorizing State Transitions | 0 | 11.57 | 19-10-2026 |
| 8 | Add ERC 8217: Agent NFT Identity Bindings | 7 | 8 | 08-07-2026 |
| 9 | ERC-8240: Trust Infrastructure for Agents and Assets | 0 | 5 | 08-07-2026 |
| 10 | From LLM Reasoning to Autonomous AI Agents: A Comprehensive Review | 0 | 7.7 | 01-06-2026 |