Skip to main content

Hemera Trading (Hemera)

Hemera Trading (Hemera) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Hemera Trading (Hemera) — an AI/Analytics | DeFi project (a platform with trading operation automation, AI bots and analytics; claimed on the official website), token (symbol: HEM) on the Ethereum network.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a web platform whose website claims AI bots/“smart bots”, analytics and tools for executing trading operations; a Telegram interface is also mentioned.
  • Who it’s for: users who need automation tools and an interface for operations (claimed).
  • Why onchain/token: the ERC‑20 token HEM on the Ethereum network is confirmed; the website claims that the token is used for access to features (staking/AI tools) and related mechanics (claimed).
  • What you can actually touch (Tier‑1): the web dashboard (/dashboard) and pages describing services (links in links_* / Evidence).

How it works (very briefly)

  1. The user does: uses the platform interface and (claimed) connects an exchange account via API.
  2. The system does: provides tools/bots/analytics and executes operations via integrations (claimed).
  3. The user gets: automation/analytics/a management interface (claimed).
  4. Where the blockchain is: the HEM token (ERC‑20) on Ethereum is confirmed; the rest of the platform logic is offchain.
  5. Token role (if any): the website claims that HEM gives access to features (staking/AI tools; claimed).

Quick links: AI thesis fit

Project passport

Field Value
Project name Hemera Trading (Hemera)
Also known as (aliases) $HEM
Logo (logo) —
Token symbol (ticker) HEM
Category AI/Analytics | DeFi
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xd0054b65b683dbdd324b51f5f1f16aadeb99a74b
Token model (token_type) utility (access + staking)
Max supply 1,000,000,000 HEM
Issuance fixed (max total supply)
Tokenomics (tokenomics, brief) The website claims: the token is used for access to staking/farming and the platform’s AI tools (as claimed).
Governance —
Admins/keys —
Audit yes (a link to the audit report is on the website; see Evidence)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI bots + trading analytics
Use‑case (use_case) trading operations automation
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 1 / evidence_score 2
Last verified 2026-02-11

General project overview

Per the Tier‑1 website, Hemera Trading is positioned as a platform with a set of tools, including “AI Bots”, “Smart Bots”, analytics and management interfaces, as well as a mention of a Telegram interface. The source also states that the platform integrates with exchanges via API (Binance and Bybit are mentioned).

The onchain fact confirmed via the explorer is the HEM token (ERC‑20) on the Ethereum network. The website claims that HEM is linked to access to features (staking/farming/AI tools), but the details of the mechanics and proof of the onchain necessity of the token for services require separate analysis.

Features/modules

  • Copy trading / manual trading / smart trading (claimed): platform modes.
  • AI Bots / Smart Bots (claimed): automation based on AI/indicators.
  • Advanced analysis (claimed): analytical tools.
  • Telegram interface (claimed): management via Telegram.

Typical scenarios

  • Scenario 1: a user enters the dashboard → configures a tool/bot → observes the state (claimed).
  • Scenario 2: a user connects an exchange via API → uses automation (claimed).

Getting started (wallet/network)

  • What you need: access to the web dashboard; an EVM wallet — if interacting with the HEM token.
  • Network/chain: Ethereum.
  • Fees: Ethereum network fees apply to operations with the token; platform/exchange fees are not confirmed by Tier‑1 sources.

Architecture/tech (non‑AI)

  • Components: a web platform (offchain) + integrations with exchanges via API (claimed) + the ERC‑20 token HEM (onchain).
  • Participant roles: platform users and token holders.
  • Where logic runs: platform operations and AI analysis — offchain; the token — onchain (Ethereum).
  • Dependencies: external exchange APIs (claimed) and the Ethereum network (for the token).

Token/economics (expanded, no forecasts)

  • Token utility (claimed): the website claims that HEM is used for access to features (staking/farming/AI tools).
  • Issuance/supply: max total supply 1,000,000,000 HEM (Etherscan).

Governance

  • Who makes decisions: —.

Security and incidents

  • Audits: an audit report is claimed on the website (see Evidence).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: risks of web platforms and external API integrations; onchain risks of the token require separate verification.

Project status and timeline

  • Current status: active (website).
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: exchange APIs (Binance/Bybit; claimed).
  • Partners: —.
  • Where it’s actually used: the web dashboard and Telegram (claimed).

AI component of the project

  • What is real AI here? the website claims AI bots and AI analytics as part of the platform.
  • What is truly onchain? the HEM token (ERC‑20) on Ethereum is confirmed.
  • Why is a token needed? the website claims: access to staking/farming and AI features (claimed); the onchain necessity of the token for services requires clarification of details.
  • Red flags (based on the information found): absence of strict Tier‑1 quality metrics for the AI part; uncertainty about which features require the token and exactly how.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity low 1
Token necessity low 1
Evidence Tier‑1 present 2
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): AI is described as part of the product (AI_1), so we do not use the intent‑only flag.
  • Evidence: Tier‑1 — https://hemeratrading.net/
  • Why sufficient / why not (one line): There is a Tier‑1 description of a service with AI bots/AI tools.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The website claims AI bots/AI analytics as part of the platform.
  • Evidence: Tier‑1 — https://hemeratrading.net/
  • Why sufficient / why not (one line): The Tier‑1 source lists services, including AI Bots and AI analysis.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The website has a link to the web dashboard (as a product surface).
  • Evidence: Tier‑1 — https://hemeratrading.net/ ; https://hemeratrading.net/dashboard
  • Why sufficient / why not (one line): The presence of a web surface is sufficient for the demo flag.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No Tier‑1 reproducible quality metrics for the AI part were found.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of the AI models was not found per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The source contains product claims, but no technical details of the models.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: the HEM token: 0xd0054b65b683dbdd324b51f5f1f16aadeb99a74b
  • Evidence: Tier‑1 — https://etherscan.io/token/0xD0054b65B683Dbdd324B51F5F1F16AadEB99a74B
  • Why sufficient / why not (one line): The token contract is confirmed by the onchain explorer.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: the existence of onchain logic of the product other than the token is not established (per Tier‑1).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xD0054b65B683Dbdd324B51F5F1F16AadEB99a74B
  • Why sufficient / why not (one line): There are no Tier‑1 onchain artifacts of product logic.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 argument for onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an ERC‑20 token, HEM.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xD0054b65B683Dbdd324B51F5F1F16AadEB99a74B
  • Why sufficient / why not (one line): The token contract is confirmed by the onchain explorer.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): The website claims that the token is used for access to platform features (staking/AI tools).
  • Evidence: Tier‑1 — https://hemeratrading.net/
  • Why sufficient / why not (one line): The source describes HEM as a utility token of the ecosystem and mentions access to features.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 0
  • Claim (one line): Protocol incentives/collateral/penalties are not established per Tier‑1.
  • Evidence: Tier‑1 — https://hemeratrading.net/
  • Why sufficient / why not (one line): Staking/farming are mentioned, but without a strict protocol specification.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance use of the token is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): Replaceability is not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): A Tier‑1 specification is needed as to why it “does not work” without the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://hemeratrading.net/ Tier‑1 description of services (AI bots/analysis, integrations) and the role of the HEM token.
Tier‑1 https://hemeratrading.net/dashboard Web surface of the product (demo surface).
Tier‑1 https://etherscan.io/token/0xD0054b65B683Dbdd324B51F5F1F16AadEB99a74B The ERC‑20 token contract of HEM (onchain fact).
Tier‑1 — No Tier‑1 source for quality metrics of the AI part (AI_3) was found.
Tier‑1 https://contractwolf.io/projects/hemera Audit report referenced by the official website (without assessing the audit conclusions).

No comments to display

Back to top