Hatom (HTM): project purpose, mechanism and token context
The review below maps the available evidence for Hatom across project scope, mechanism, token role and operational status. Fast-changing market, supply and contract details are kept outside the factual record unless a dated source supports them. This structure is designed to keep entity-specific evidence, dated limitations and practical verification needs visible rather than hiding them behind generic market language.
Purpose in the reviewed sources
The reviewed record describes Hatom in these terms: Official docs call HTM the utility and governance token of Hatom. This establishes a documented purpose, but it does not establish current adoption, reserves, market value or future results. This boundary keeps the stated project purpose separate from observations that need market, legal or onchain evidence.
A second source-bound point concerns the operating model: The official allocation table totals 100M HTM and lists lock/vesting periods. The statement should be checked against the current interface and deployment because product rules and integrations can change. A current interface check is still necessary because documentation can outlive the implementation it originally described.
Mechanism described by the project
The sources describe an additional part of the design: Hatom docs describe lending, liquid staking, USH and a TAO bridge. The point is informative about mechanism, not a promise of financial outcome or uninterrupted availability. This protects the distinction between how a system is described and what a user can enforce or execute today.
For present-day identification, the evidence records: Hatom is a MultiversX DeFi liquidity hub offering lending, liquid staking, a native stablecoin and bridge infrastructure. That description does not remove the need to verify the exact network, contract and supported interface. Contract verification should include the full address, network and official destination rather than a shortened ticker comparison.
Supply and token context
For token structure, the record provides the following: Hatom supplies non-custodial lending/borrowing, liquid staking and over-collateralized USH stablecoin products. HTM governs protocol decisions; staking HTM in the Booster can direct protocol revenue and incentives to stakers. Absent or qualified economic parameters remain open questions and should not be converted into current facts. The current chain record and latest official terms should resolve any difference between historical and present economic parameters.
For understanding dependencies, the following fact is relevant: Documented token utility: govern upgrades, listings and feature integrations; stake in the Booster; receive a portion of protocol-generated revenue; participate in the Hatom ecosystem incentive model. Current permissions, custody arrangements and transaction paths remain separate verification tasks. Each dependency can change the practical risk even when the high-level project description remains the same.
Contracts, versions and interfaces
The evidence set contains one additional project-specific point: Official docs call HTM the utility and governance token of Hatom. It is presented as documented context, not as a recommendation or prediction. The same rule applies to scale, user, partnership, licensing and performance statements found in project-controlled material.
The dated evidence supports this narrow conclusion: The official allocation table totals 100M HTM and lists lock/vesting periods. Because deployments evolve, it should be compared with the latest official record before use. Historical documentation remains useful context, but it is not automatically evidence of the current operating state.
What the sources do not establish
The evidence establishes the following while leaving other fields open: Hatom docs describe lending, liquid staking, USH and a TAO bridge. Current activity and market conditions should not be inferred from that statement. Leaving a field unresolved is preferable to publishing a plausible but unsupported completion.
The record closes with this supported point: Hatom is a MultiversX DeFi liquidity hub offering lending, liquid staking, a native stablecoin and bridge infrastructure. Before acting, users should reconcile it with current identity, contract, access and risk information. The exact checks depend on the asset, but a current primary source and full contract comparison are the minimum identity controls.
Key takeaways
- Official docs call HTM the utility and governance token of Hatom.
- The official allocation table totals 100M HTM and lists lock/vesting periods.
- Hatom docs describe lending, liquid staking, USH and a TAO bridge.
- Hatom is a MultiversX DeFi liquidity hub offering lending, liquid staking, a native stablecoin and bridge infrastructure.
- Hatom supplies non-custodial lending/borrowing, liquid staking and over-collateralized USH stablecoin products. HTM governs protocol decisions; staking HTM in the Booster can direct protocol revenue and incentives to stakers.
YearBull Rank overview
Current YearBull Rank for hatom: #7845.
Rank change (reference points).
Reading rule: a smaller rank number indicates stronger placement.
- 7d window (2026-10-20): #6507 → #7845 (down by 1338).
- 30d window (2026-09-27): #7608 → #7845 (down by 237).
Risk framing: short bursts do not always translate into durable placement. If it moves only on certain days, it can be update cadence.
Cycle framing: sideways periods still reshuffle relative placement. If both are flat, the coin may be tracking its peer basket.
Liquidity posture: deep markets usually produce smoother rank paths. If the line reacts in bursts, watch for calendar-driven liquidity.
Market structure: fragmentation can make rank more reactive. If rank improves slowly, it often reflects broader access or steadier participation.
YearBull Rank is an internal ordering on YearBull that positions a coin relative to the rest of the tracked universe. A smaller rank number indicates a stronger position at that moment. Use it as positioning context over time, not as a promise.
