Skip to content

docs: integrate ERC-8004, ENSIP-17, and ENSIP-25 into specs#23

Merged
Swaagie merged 4 commits intomainfrom
docs/erc8004-ens-integration
Apr 16, 2026
Merged

docs: integrate ERC-8004, ENSIP-17, and ENSIP-25 into specs#23
Swaagie merged 4 commits intomainfrom
docs/erc8004-ens-integration

Conversation

@scourtney-godaddy
Copy link
Copy Markdown
Contributor

Summary

  • TRUST_INDEX_SPEC.md: ENS_ENSIP25 signal strength (Strong), ERC8004_VALIDATION (Moderate), escape difficulty split (.eth vs ENSIP-17 DNS), agent wallet vs. owner in solvency, gas-weighted on-chain feedback, token transfer lifecycle
  • DESIGN.md: ERC-8004 in "Relationship to other standards" with canonical ANS service entry format, ERC-8004 agentId as cross-RA correlation identifier

Synced from gdcorp-engineering/ans-registry-poc PRs #833 and #835.

Test plan

  • Verify no internal hostnames, infrastructure names, or operational parameters leaked (SECURITY_EXTERNAL.md rules)
  • Confirm DESIGN.md §1.2.1 ERC-8004 section uses example.com for all examples
  • Confirm TRUST_INDEX_SPEC.md signal strength table entries are self-contained conditions

🤖 Generated with Claude Code

TRUST_INDEX_SPEC.md:
- Add ENS_ENSIP25 (Strong) and ERC8004_VALIDATION (Moderate) to signal strength table
- Split ENS_ENSIP25 escape difficulty: native .eth (Medium) vs ENSIP-17 DNS (Easy)
- Solvency: check agent wallet, not token owner; freshness penalty on token transfer
- Behavior: weight on-chain feedback by transaction cost, not count; persist across transfers
- Integrity: add ERC-8004 token transfer as lifecycle event signal

DESIGN.md:
- Add ERC-8004 to "Relationship to other standards" with canonical ANS service entry format
- Add ERC-8004 agentId as cross-RA correlation identifier

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@scourtney-godaddy scourtney-godaddy requested a review from a team April 16, 2026 06:25
scourtney-godaddy and others added 3 commits April 16, 2026 02:31
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
AIM definition expanded from DNS-only checker to the RA's verification
worker. Checks DNS, certificates, principal bindings (ENS/DID/LEI),
credential signatures, and on-chain identity (ERC-8004). §5.4 table
adds five verification type rows.

Informational note in TRUST_INDEX_SPEC.md: when the RA's AIM has
verified a credential before sealing, the TI is not required to
re-verify it.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Swaagie Swaagie added this pull request to the merge queue Apr 16, 2026
Merged via the queue into main with commit 9e5259e Apr 16, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants