This yellow paper specifies the technical architecture and verification semantics of OpenAgenet (OAN), a protocol-neutral trust layer for heterogeneous Agent resources. The design combines did:oan decentralized identifiers (DIDs), verifiable credentials (VCs), on-chain infrastructure governance, and Root-verified resource packages. It defines the objects and lifecycle transitions that connect subject-control verification, Registrar admission, Root acceptance, authorized Discovery, and signed invocation. Infrastructure authorization requires both active governance state and a valid Root-issued credential; resource discovery additionally requires package integrity, current-version state, and authorized-domain coverage. Local OAN Identity signing material remains separate from public protocol objects. Integration profiles carry resource identity into the Model Context Protocol (MCP) and Agent-to-Agent (A2A) protocol through Skill, Runtime, Sidecar, and Gateway interfaces without redefining native task semantics. The paper distinguishes protocol requirements from implementation choices and sets out security properties, persistence and recovery expectations, and conformance criteria. Together, these rules provide a technical basis for independently implemented registration, discovery, and identity-protected interaction within an OAN trust domain.
OpenAgenet (OAN) is an open infrastructure project for trusted Agent interconnection across independently operated networks. It addresses the verification of resource identity, governance state, discovery authorization, and freshness before interaction. OAN combines decentralized identifiers (DIDs), verifiable credentials (VCs), and on-chain infrastructure governance with a routing-aware did:oan registration and discovery model. Registrars verify onboarding evidence; the Root service accepts resource identity versions and publishes verifiable packages; authorized Discovery nodes return signed results within their governed scope. Root also governs the semantic tag tree shared by registration and discovery. Public DID Documents and credentials remain separate from local OAN Identity signing material and from controller authorization. Skill, Runtime, Sidecar, and Gateway integration paths allow existing Agents to adopt this identity model progressively, including through the Model Context Protocol (MCP) and Agent-to-Agent (A2A) protocol, while retaining their native task and workflow semantics. Prototype evaluation and a public pilot support examination of the trust lifecycle and its operational bottlenecks. This white paper presents the architecture, governance model, ecosystem adoption paths, and standardization opportunities for OAN as a shared identity and trust infrastructure for heterogeneous Agent resources.