SOVEREIGN
APPNETS.
Upgrade standard multisig accounts into programmable data networks. HCS-16 Floras unify identity, sovereign state, and localized consensus into a single living organism.
Petal Accounts.
Before you can form a Flora, you need a Petal. HCS-15 enables users and agents to create infinite, isolated on-chain identities that share a single ECDSA private key.
This "Shared Key Architecture" eliminates wallet fatigue. One master key controls your Gaming Petal, your DeFi Petal, and your Social Petal.
READ HCS-15 SPECWhat is a Flora?
A Flora is a sovereign AppNet account—a decentralized root of trust for applications, organizations, and agent swarms. While it secures a shared Treasury via cryptographic Thresholds, its true power lies in coordination.
It acts as a consensus engine for its members. By binding communication, transaction proposals, and state proofs into a single identity, a Flora becomes a programmable entity capable of running complex, decentralized logic entirely on-graph.
The Topic Triad.
CTopic
hcs-16:ID:0Communication. Where members chat, propose governance votes, and negotiate off-chain data. Human-readable or LLM-readable.
TTopic
hcs-16:ID:1Transaction. The execution layer. Only contains pre-signed Scheduled Transaction proposals ready for approval.
STopic
hcs-16:ID:2State. The memory layer. Cryptographic proofs (HCS-17), membership changes, and epoch transitions.
Network Formation.
Discovery
Agents find each other via HCS-18 or HCS-10 registries.
Formation
Initiator creates the Flora account with a KeyList threshold (e.g. 2-of-3).
Provisioning
Three topics are created. Admin key is the Flora threshold key. Submit key is 1-of-N.
Activation
Members post `flora_created` to CTopic to confirm participation.
Native Consensus.
Floras leverage the native Hedera Consensus Service (HCS) and Threshold Keys to reach agreement. Unlike complex smart contract DAOs, basic coordination happens directly on the ledger layer.
Proposals are broadcast to the Transaction Topic (TTopic). Members review the `schedule_id` and sign the transaction using their Petal keys. Once the threshold (e.g., 2-of-3) is met, the Hedera network automatically executes the action.
The Heartbeat of Trust.
In a decentralized organism, truth isn't just stored in a database—it's derived. HCS-17 allows any observer to cryptographically verify the exact state of a Flora in milliseconds, without replaying the entire history.
It acts as a real-time, tamper-proof pulse. By aggregating member states, topic sequences, and configuration into a single Merkle-like hash, we achieve instant finality for AppNet state.
Trustless Verification
Light clients can verify state without running a full node.
Instant Sync
New members can join and sync state immediately using the latest pulse.
0x7f3a...9c2bOn-Chain Governance.
Members vote on proposals (like adding a new member) by posting `flora_join_vote` messages to the CTopic. Everything is transparent. Everything is auditable.
Shared Treasury.
The Flora account holds HBAR, Tokens, and NFTs. No single member can move funds. All transfers require a Scheduled Transaction approved by T members.
Graceful Exit.
When a Flora's mission is complete, members can vote to dissolve. This involves draining assets, dissociating tokens, and executing an `AccountDeleteTransaction`.
Build with the SDK.
Create Flora
Propose Transaction
See It In Action.
Flora Price Oracle
A complete, production-ready Flora implementation that demonstrates HCS-15/16/17 in action. Three Petal nodes reach consensus on HBAR/USD prices using real adapters and HCS-17 state proofs.
Full Stack Implementation
Dockerized setup with Petals, consumer, Postgres, and real-time dashboard
Real-Time Consensus
Watch HCS-17 proofs land on testnet with ~2s cadence
Production Patterns
Standards SDK integration, adapter registry, and state verification
Binance, CoinGecko, Hedera Rate adapters
State hashes published to consensus topic
Verifies quorum and serves consensus price
docker compose up -d
curl localhost:3000/price/latest