3 posts tagged with "Identity"

On the internet, nobody knows you're a dog. In the agent economy, nobody knows if you're a scammer.

When agents start moving real money—managing portfolios, buying APIs, signing contracts—trust is the bottleneck. You need answers: Who owns this thing? What's its track record? Is it running the code it claims?

ERC-8004 proposes a standard for Trustless Agent Identity. It moves reputation out of centralized databases and onto immutable EVM ledgers.

The Registry Broker supports this standard today. It lets agents carry verifiable "on-chain business cards" alongside their fast HCS-10 comms channels.

We are excited to announce that we’re preparing the publication of three new Hashgraph Online standards:

• HCS-15 Petals (Profiles) defines profile accounts that reuse the same private key as a base account.
• HCS-16 Floras (AppNets) defines multi-party AppNet accounts that coordinate assets and actions using a clear message flow and three required topics.
• HCS-17 State Hash defines how Petals and Floras publish verifiable state hashes.

All three documents are Status: Draft, Version 1.0.

Hashgraph Online has published HCS-14 (Universal Agent Identifier), a draft standard and SDK that gives AI agents a single, portable identifier across Web2 APIs, Web3 networks, and hybrid systems. HCS-14 works alongside self-sovereign identity by wrapping existing DIDs where they exist and providing deterministic identifiers where they do not, enabling reliable discovery and routing across protocols.

Status: Draft. We welcome feedback from the community in the HCS‑14 discussion.

HCS‑14 is network‑agnostic. It works across Web2 (A2A/REST), EVM/ETH, and more. Hedera support is optional. We start with Web2 and EVM, then cover Hedera.

TL;DRDirect link to TL;DR​

• A single, portable identifier (UAID) for agents across Web2 and Web3
• Two modes: deterministic AID or wrap your existing DID
• Minimal routing hints for discovery; identity details stay in DID docs/profiles