Technical deep-dives, release announcements, and essays on agent identity
The v1.1 release brings two major additions to the Open Agent Specification: a complete taxonomy of eleven entity kinds and three progressive conformance levels. This post walks through the design decisions and what they mean for implementers.
As autonomous agents proliferate, the question of identity becomes existential. Without cryptographic lineage, there is no accountability. Without accountability, there is no trust. We explore why DID-based identity is the foundation of the agentic future.
FROST enables t-of-n threshold signing without a trusted dealer. We share our experience implementing FROST for Multi-Human Root identities, the challenges of coordinator-less DKG, and how we achieved sub-second signing rounds.
All seven OAS SDKs share a single Rust cryptographic core compiled to WASM. This ensures byte-identical signatures across TypeScript, Python, Go, Swift, Kotlin, and vanilla JavaScript. Here is how we built it.
Every OAS agent traces back to a human root through a chain of cryptographic proofs. We explain the HKDF-SHA256 key derivation model, how lineage chains are verified offline, and why this is non-negotiable for enterprise adoption.