Hedera

Hedera is a public hashgraph-based network with governance organised through the Hedera Council. It provides services for ordering messages, managing tokens and executing contracts. HBAR is used to pay for network operations, including the services selected by an application.

Service selection depends on the problem. Recording evidence, issuing a token and running arbitrary business logic do not necessarily require the same component. Distinguishing these needs helps determine whether a product requires its own EVM contract or can use a native service with an appropriate integration.

Hashgraph uses event propagation and virtual voting to agree on operation ordering. The Consensus Service, or HCS, records messages with consensus ordering and timestamps. The Token Service, or HTS, provides native asset functions, while the Smart Contract Service executes EVM-compatible contracts.

Fees are denominated in dollars and charged in HBAR under network conversion rules. This supports budgeting, but costs depend on the operation, its resource use and current fees. A single universal price should not be promised for every transaction or application workflow.

A document registry can retain a document outside the network and submit a verifiable reference to HCS. The evidence establishes the recorded message and its order, not the document's truth or the issuer's identity unless those controls are designed separately.

For assets, HTS offers functions such as authorisation, freeze and administrative keys without implementing every primitive from scratch. Those powers need documentation and protection. Mirror nodes provide data access for queries and monitoring, playing a different role from consensus nodes and introducing their own integration requirements.

Council governance is a characteristic a project should accept deliberately, rather than a guarantee of compliance or regulatory approval. Selection also requires checking wallets, custodians and assets needed by the product. The reputation of participating organisations is not sufficient evidence for the application architecture.

Before deploying Solidity, check execution differences, addresses and native services. Prototypes should cover issuance, transfer and administration, including lost permissions and delayed queries. HTS reduces custom code but still requires review of configuration, keys and integration logic across the full operating process.