Hedera — DLT with HTS native tokens and EVM contracts
Hedera's hashgraph consensus offers high throughput with deterministic finality. HTS tokens are first-class (no smart contract needed) and an EVM module supports Solidity.
Hedera's accounting story has two surfaces. The Hedera Token Service (HTS) provides native fungible and NFT tokens — issuance, transfer, freeze, KYC controls — without requiring a smart contract. For an enterprise treasury, that's auditor-friendly because the token logic is at the protocol level. Hedera also exposes an EVM-compatible smart-contract layer (HSCS) that runs Solidity. The Hedera Consensus Service (HCS) provides timestamped immutable message ordering — used for supply-chain and audit-log applications, not financial transfers.
What's tracked on Hedera
HBAR transfers
Native asset movement with the per-transaction fee model.
HTS token transfers
Native fungible and NFT tokens decoded with metadata.
Smart contract calls (HSCS)
EVM-compatible smart-contract activity decoded.
HCS messages (audit trails)
Tracked for visibility but not classified as financial transactions.
Hedera accounting questions
How is HTS different from ERC-20?
HTS tokens are native — issuance, transfer, freeze, KYC controls are protocol-level features rather than smart-contract logic. From an accounting standpoint, the audit trail is cleaner because token logic isn't embedded in arbitrary contract code. The classification is the same as ERC-20 fungibles.
Other chain coverage and tax guides relevant to this network.
Book Hedera the right way
Free during Alpha. Connect a wallet, see every transaction reconciled to journal entries.