 |
Canonical, text-first specifications for Hiero Consensus Standards (HCS), originally created and maintained by Hashgraph Online. Reference implementations: Standards SDK Process and governance are defined in docs/standards/hcs-4.md. |
|---|
Hiero Consensus Standards (HCS) are open, versioned specifications for interoperable data formats and protocol patterns layered on top of the Hiero Consensus Service (and similar consensus/message transports). They support patterns ranging from simple file storage and registry management to complex state and discovery workflows for appnets and AI agents. This repository is the canonical source for the normative text of HCS specifications, along with the contribution workflow and governance process used to evolve them.
Implementers (apps, wallets, agents, indexers, and tooling) need a stable, auditable source of truth for message formats, validation rules, and lifecycle expectations so independent implementations can interoperate reliably. A lightweight, specifications-first repository makes review and versioning easier, reduces ambiguity, and keeps reference implementations (like the Hashgraph Online Standards SDK) aligned.
| Spec | Title | What it does |
|---|---|---|
| HCS-1 | HCS-1: File Management | Encode, chunk, upload, retrieve, and reassemble file data on HCS topics using a JSON schema and topic memo validation. |
| HCS-2 | HCS-2: Topic Registries | Defines topic registries for HCS, enabling structured data organization, discovery, and retrieval. |
| HCS-3 | HCS-3: Recursion | Defines a method for implementing recursion on HCS, enabling more complex data structures and relationships. |
| HCS-4 | HCS-4 — HCS Standardization Process | Defines the lifecycle, roles, criteria, and repository workflow for proposing, reviewing, approving, publishing, and maintaining Hiero Consensus Standards (HCS). |
| HCS-5 | HCS-5: Hashinals | Standard way to inscribe Hashinals using Hiero Consensus Service and Hiero Token Service, inspired by Ordinals. |
| HCS-6 | HCS-6: Dynamic Hashinals | Framework for creating dynamic Hashinals whose content/behavior can be updated over time. |
| HCS-7 | HCS-7: Smart Hashinals | Enables dynamic NFTs whose metadata updates based on smart contract state using deterministic topic selection and WASM processing. |
| HCS-8 | HCS-8 Standard: Poll Topic Standard | Framework for using HCS topics to manage polls and record poll activity on-ledger. |
| HCS-9 | HCS-9: Poll Metadata | Metadata schema for polls intended for broad ecosystem adoption and interoperability. |
| HCS-10 | HCS-10 OpenConvAI Standard: AI Agent Communication on HCS | Framework for AI agents to register, discover, and communicate over HCS using registries, topics, and standardized operations. |
| HCS-11 | HCS-11: Profile Metadata | Systematic approach for managing profiles on Hiero via account memos, enabling rich identity for individuals and AI agents. |
| HCS-12 | HashLinks — Actions, Blocks, and Assembly | Framework for building interactive experiences on Hiero using WASM actions, UI blocks, and an assembly layer without smart contracts. |
| HCS-13 | HCS-13: Schema Registry | Standard way to define, register, and reference schemas for validation and interoperability across the Hiero ecosystem. |
| HCS-14 | HCS-14 - Universal Agent ID Standard | Systematic approach for generating globally unique identifiers for AI agents across web2 and web3 environments. |
| HCS-15 | HCS-15 Standard: Petals - Profile Accounts | Enables account holders to create multiple account instances (petals) that share the same private key while isolating profiles and assets. |
| HCS-16 | HCS-16 Standard: Floras - AppNet Accounts | Rules and practices for multi-party Flora accounts enabling coordination, shared escrow, and state consensus across agents. |
| HCS-17 | HCS-17 Standard: State Hash Calculation | Methodology for calculating state hashes of accounts and formations to support auditable, tamper-proof state verification. |
| HCS-18 | HCS-18 Standard: Flora Discovery Protocol | Discovery and formation protocol for Floras via an open broadcast mechanism. |
| HCS-19 | HCS‑19 Standard: AI Agent Privacy Compliance | ISO/IEC TS 27560-aligned framework for AI agents to document and manage privacy compliance on Hiero via HCS topics (consent, processing records, rights fulfilment). |
| HCS-20 | HCS-20 Standard: Auditable Points Standard on Hiero | Defines how points can be managed and audited on Hiero using HCS topics, inspired by BRC-20 and extended for auditable points and inscriptions. |
| HCS-21 | HCS-21 Standard: Adapter Registry | Platform-agnostic adapter registry packaging decentralized adapters, manifests, and consensus context for distributed appnets (Floras). |
| HCS-XX | HCS-XX — Template | Template for drafting a new specification that conforms to HCS-4 requirements. |
Full index: docs/standards/index.mdx
To propose a new specification, follow the HCS-4 process.
- Canonical process: HCS-4 — HCS Standardization Process
- New proposals: open an issue (use “01 - Proposal”), draft under
docs/standards/drafts/<slug>.md(start fromdocs/standards/hcs-XX.md), then request number assignment and submit a PR - Updates to existing specs: submit a PR against the relevant
docs/standards/hcs-*document(s) following the HCS-4 change management rules - Normative keywords: use RFC 2119 language (MUST/SHOULD/MAY) where appropriate
Reference implementations live in the Hashgraph Online Standards SDK:
Editors and maintainers are listed in MAINTAINERS.md. CODEOWNERS are defined in CODEOWNERS.
This project is governed by the Contributor Covenant Code of Conduct. By participating, you are expected to uphold this code of conduct.
Apache License 2.0
