01 / Overview

Standards & interoperability

Infrastructure becomes significantly more valuable when independent organizations can implement it without requiring a shared vendor or trust boundary. Standardizing primitives is how distributed systems scale.

02 / Ecosystem

Agent Name Service

HCS-14ANS Resolution via Web & DNS

Summary

Defines how HCS-14 resolvers discover ANS-registered agents through DNS and Web metadata, with optional transparency verification.

Why it matters

Makes DNS-anchored ANS identities resolvable across ecosystems without requiring every resolver to implement ANS-specific branching.

RoleAuthor
StatusDraft · v0.1.0

HCS-27ANS Transparency Log Checkpoints

Summary

Defines how append-only ANS transparency logs publish Merkle-root checkpoints to Hedera Consensus Service.

Why it matters

Lets auditors verify inclusion and append-only consistency against independently timestamped commitments without putting full registry data on-ledger.

RoleAuthor
StatusDraft · v1.0
03 / Ecosystem

Agentic AI Foundation

AAIFAgentic AI Foundation Working Groups

Summary

Direct participation in AAIF technical meetings and working groups focused on open, interoperable agent infrastructure.

Why it matters

Brings Internet naming, DNS, PKI, security, and production-infrastructure experience into the broader ecosystem defining how agents operate across platforms and organizational boundaries.

RoleActive participant
StatusOngoing
04 / Ecosystem

IETF

draft-mozleywilliams-dnsop-dnsaidDNS Agent Identity Discovery

Summary

DNS-based agent discovery leveraging SVCB records and discovery profile support.

Why it matters

Leverages the existing globally distributed DNS primitive to discover agent capabilities while incorporating downgrade resistance.

RoleAcknowledged contributor
StatusActive Internet-Draft · -02

REGEXTRegistration Protocols Extensions

Summary

Participation in EPP and RDAP extensions mapping to global registrar operations.

Why it matters

Ensures that extensions to domain registration protocols remain interoperable and backward-compatible across disparate global systems.

RoleDocumented participant
StatusIETF 118 & 121