Skip to main content

Havy

Havy — 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).

Havy — a project with an ERC‑20 token on the Ethereum network; the website URL returns irrelevant content as of the verification date, so the product description and the role of the token are considered not established.

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: an ERC‑20 token/project; its purpose is not established per Tier‑1 as of the verification date.
  • Who it’s for: not established per Tier‑1 as of the verification date.
  • Why onchain/token: the ERC‑20 token contract is confirmed; the role of the token and onchain logic (other than the token) are not established per Tier‑1 as of the verification date.

How it works (very briefly)

  1. The user does: performs operations with the token (ERC‑20 transfers/interactions).
  2. The system does: records operations on the Ethereum network.
  3. The user gets: onchain confirmation of operations.
  4. Where the blockchain is: the ERC‑20 contract on Ethereum.
  5. Token role (if any): not established per Tier‑1 as of the verification date.

Quick links: AI thesis fit

Project passport

Field Value
Project name Havy
Also known as (aliases) HAVY
Logo (logo) ../assets/699_havy_logo.webp
Token symbol (ticker) HAVY
Category Consumer
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2018-08-30 (deployment of the HAVY ERC‑20 contract; per the Etherscan creation tx)
Project status (status) active
Token (standard) ERC-20
Token contract 0x7c2e5b7ec572199d3841f6a38f7d4868bd0798f1
Token model (token_type) —
Max supply 8 200 000 000 HAVY (max total supply per Etherscan)
Issuance —
Tokenomics (tokenomics, brief) Per Etherscan, max total supply = 8.2B HAVY (8 decimals). Per the smart contract code (GitHub), sales (tokensPerEth), admin airdrop, owner‑burn and withdraw are described; in the onchain creation tx, 2B HAVY was minted to 0x2E483151... (per Etherscan).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) —
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

As of the verification date, the ERC‑20 token contract on the Ethereum network and the existence of a smart contract repository on GitHub are confirmed. The website URL returns irrelevant content (not about the crypto project), so the product description and the role of the token are considered not established until explicit Tier‑1 artifacts appear.

Features/modules

  • Not established per Tier‑1 as of the verification date.

Typical scenarios

  • Scenario 1: transfer of the ERC‑20 token → recording of the transaction on Ethereum.

Getting started (wallet/network)

  • What you need: a wallet for the Ethereum network.
  • Network/chain: Ethereum.
  • Fees: Ethereum fees for ERC‑20 operations.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract; the smart contract repository.
  • Participant roles: token holders.
  • Where logic runs: onchain on Ethereum.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 as of the verification date.
  • Protocol necessity drivers: not established per Tier‑1 as of the verification date (other than issuance/distribution mechanics in the contract code).
  • Who pays fees: token users for ERC‑20 operations.
  • Where fees go: to Ethereum validators (network fees).
  • Max supply: 8 200 000 000 HAVY (max total supply per Etherscan).
  • Issuance/burn: the code includes burn() (onlyOwner), which reduces totalSupply (per GitHub).
  • Security/incentive mechanisms: per the code, there is an admin airdrop and initial distribution/sale; protocol incentives for the product are not established.
  • Distribution and token issuance schedule: per the code, 2B HAVY was distributed to the owner at deployment; further distribution — via getTokens() (purchase) and admin airdrop (per GitHub).
  • Treasury: —.

Governance

  • Who makes decisions: not established per Tier‑1 as of the verification date.
  • How protocol parameters change: not established per Tier‑1 as of the verification date.

Security and incidents

  • Audits: —.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: the code contains owner rights (airdrop/changing the sale rate/burn/withdraw), which increases trust‑assumptions.

Project status and timeline

  • Current status: active (based on the presence of the token/contract).
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1 as of the verification date.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component was found.
  • What is truly onchain? The ERC‑20 token contract on Ethereum.
  • Why is a token needed? Not established per Tier‑1 as of the verification date.
  • Red flags (based on the information found): irrelevant/unexpected content at the website URL; absence of a Tier‑1 description of the product and the role of the token.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present (OC+TK, partially) 3
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 mention of AI as intent/applicability was found.
  • Evidence: Tier‑1 — https://havy.io
  • Why sufficient / why not (one line): Per Tier‑1 sources, an AI component is not confirmed; the website URL looks irrelevant.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): An AI component is not established per Tier‑1.
  • Evidence: Tier‑1 — https://havy.io
  • Why sufficient / why not (one line): There is no Tier‑1 description of AI tasks/models.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): An AI demo is not applicable: an AI component is not established.
  • Evidence: Tier‑1 — https://havy.io
  • Why sufficient / why not (one line): —.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

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

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

  • AI_4 (decision): 0
  • Claim (one line): A tech description of an AI component is not applicable: an AI component is not established.
  • Evidence: Tier‑1 — https://havy.io
  • Why sufficient / why not (one line): —.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x7c2e5b7ec572199d3841f6a38f7d4868bd0798f1 (ERC‑20 contract); creation tx 0xacb03f939d601fcadc8590eae7139376cfd45b25b415ebd822e3c407fcb7e17f; ContractCreator 0x2E483151a9649DDC35D6eeeDa31CfE2d2dD32a29 (per Etherscan).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x7c2e5b7ec572199d3841f6a38f7d4868bd0798f1 ; https://etherscan.io/tx/0xacb03f939d601fcadc8590eae7139376cfd45b25b415ebd822e3c407fcb7e17f
  • Why sufficient / why not (one line): Etherscan records the ERC‑20 contract and its creation tx on Ethereum mainnet.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 as of the verification date (other than the token/contract).
  • Evidence: Tier‑1 — https://github.com/havytoken/smartcontract
  • Why sufficient / why not (one line): The smart contract repository does not prove product onchain logic other than the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://github.com/havytoken/smartcontract
  • Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): An ERC‑20 contract is recorded in links_*, so the token exists.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x7c2e5b7ec572199d3841f6a38f7d4868bd0798f1
  • Why sufficient / why not (one line): The onchain contract page confirms the existence of the token.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): Payment for the service with the token is not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://github.com/havytoken/smartcontract
  • Why sufficient / why not (one line): There is no Tier‑1 description of the token utility.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Mechanics of token‑based incentives/collateral/penalties are not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://github.com/havytoken/smartcontract
  • Why sufficient / why not (one line): There are no incentive parameters as of the verification date.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://github.com/havytoken/smartcontract
  • Why sufficient / why not (one line): There is no description of governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not established per Tier‑1 as of the verification date.
  • Evidence: Tier‑1 — https://github.com/havytoken/smartcontract
  • Why sufficient / why not (one line): Without a confirmed role of the token, no conclusion can be drawn.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://havy.io The website URL currently looks irrelevant to the claimed crypto project (a domain/content conflict is possible).
Tier‑1 https://github.com/havytoken/smartcontract Smart contract repository (context).
Tier‑1 https://raw.githubusercontent.com/havytoken/smartcontract/master/havy.sol Token parameters in the code (name/symbol/decimals/totalSupply), initial distribution to the owner, airdrop/sale and owner functions (burn/withdraw).
Tier‑1 https://etherscan.io/token/0x7c2e5b7ec572199d3841f6a38f7d4868bd0798f1 The existence of the ERC‑20 token/contract on Ethereum.
Tier‑1 https://etherscan.io/token/0x7c2e5b7ec572199d3841f6a38f7d4868bd0798f1 Max total supply = 8 200 000 000 HAVY (8 decimals).
Tier‑1 https://etherscan.io/tx/0xacb03f939d601fcadc8590eae7139376cfd45b25b415ebd822e3c407fcb7e17f Creation tx of the HAVY contract (ERC‑20) and mint of 2 000 000 000 HAVY to 0x2E483151... (ContractCreator).
Tier‑2 https://coinmarketcap.com/currencies/havy/ Reference profile; not Tier‑1 proof.

No comments to display

Back to top