Reviewing KYABridge8004 against the thread’s principle that a value which can change a verdict belongs to the identity of what is evaluated. In _resolveLevel a missing assertion sets level = 0, and per the contract notes revoked or expired ones also end at responseMap[0]. configureScheme only requires responseMap[i] <= 100, so an operator can set responseMap[0] to a non-zero value and every agent with no assertion gets that score, or use a non-monotonic map. Should the spec require responseMap[0] == 0 and a non-decreasing map for ordered levels? Also: is it intended that “never checked” and “checked, level 0” look identical to an 8004-only client?
| # | Наименование новости | Тональность | Информативность | Дата публикации |
|---|---|---|---|---|
| 1 | ERC-8259: AI Agent Identity, Reputation & Threat Registry (Draft v2 – Request for Feedback) | 0 | 8.5 | 17-10-2026 |
| 2 | ERC-8414: Token-Bound Task Tenders | 0 | 9.19 | 19-10-2026 |
| 3 | ERC-8447: Swarm AI Framework | 0 | 8 | 18-10-2026 |
| 4 | ERC-8370: Inheritable Agent Mandates | 0 | 8.79 | 14-08-2026 |
| 5 | ERC-8004: Trustless Agents | 0 | 5 | 10-07-2026 |
| 6 | ERC-8004: Trustless Agents | 0 | 10 | 14-08-2026 |
| 7 | A map of the agent-mandate ERCs — what each one actually does | 0 | 11.48 | 14-08-2026 |
| 8 | EIP-8442: 64-bit Opcodes for the EVM | 0 | 12.83 | 19-10-2026 |
| 9 | Add ERC 8217: Agent NFT Identity Bindings | 7 | 8 | 08-07-2026 |
| 10 | ERC-7303: Token-Controlled Token Circulation | 0 | 5 | 08-07-2026 |