Humans.ai

Humans.ai — 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).

Humans.ai — an AI/Agents | Infra “AI & Blockchain” ecosystem that includes its own L1 blockchain (Humans Blockchain) and an AI direction (EVA / AI agents). The ecosystem’s native token: HEART (also represented by an ERC‑20 contract on Ethereum).

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: its own blockchain + a product layer positioned as a platform for creating/using AI agents (EVA) and “AI on blockchain”.
Who it’s for: developers and teams who want to build dApps/agents on the Humans.ai network (Cosmos + EVM compatibility) and ecosystem users.
Why onchain/token: the blockchain is a PoS network with validators and EVM contracts; the HEART token is the native asset for fees, staking/rewards and governance (per Tier‑1 sources).
What you can actually touch (Tier‑1): Humans.ai Docs (EVM contracts, validators, explorers) — https://docs.humans.ai/; public explorers — https://docs.humans.ai/developer/block-explorers

How it works (very briefly)

The user does: deploys a node/validator or uses the network via a wallet (MetaMask/Keplr) and dApps; a developer deploys EVM contracts.
The system does: validators (CometBFT) produce blocks; the network provides an EVM environment and (per the docs) extensions/precompiles for operations such as staking/governance.
The user gets: onchain transactions/contracts and the ability to participate in staking/governance; the product layer is positioned as “AI agents / EVA”.
Where the blockchain is: Humans.ai is a sovereign PoS L1; data is available via Cosmos/EVM explorers (Mintscan and others).
Token role (if any): HEART is used for fees, staking (validators/delegators), rewards and governance; fees are paid in HEART even if the payment is initiated in fiat/another crypto (per the Tier‑1 $Heart page).

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Humans.ai
Also known as (aliases)	Humans Blockchain; EVA; $HEART
Logo (logo)	../assets/131_humans-ai_logo.svg
Token symbol (ticker)	HEART
Category	AI/Agents \| Infra
Primary chain (chain)	Humans.ai
Type	Appchain
Network status	mainnet
Consensus (consensus)	PoS (CometBFT)
Launch date (launch_date)	2023-05-29 (mainnet launch per the Humans Blockchain page)
Project status (status)	active
Token (standard)	native
Token contract	— (for the ERC‑20 representation see links_*/Evidence)
Token model (token_type)	utility (gas + staking + governance)
Max supply	7,800,000,000 `HEART` (per Humans Blockchain / $Heart)
Issuance	—
Tokenomics (tokenomics, brief)	fees in `HEART`; staking/rewards for validators and delegators; governance token
Governance	governance via `HEART` (mentioned on the token page and in the validator documentation)
Admins/keys	—
Audit	yes (an audit is mentioned on the Etherscan token page)
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	EVA / AI agents
Use‑case (use_case)	L1 + EVM for an AI ecosystem
DecAI Fit — AI thesis fit	3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary	1 / 3 / 3 / 3
Last verified	2026-02-05

Links (links_*)

Type	Link
Website	https://humans.ai
Docs	https://docs.humans.ai/
GitHub	https://github.com/humansdotai
Releases / Changelog	https://github.com/humansdotai/humans/releases
Whitepaper	https://humans.ai/whitepaper
Roadmap	https://app.humandesign.ai/roadmap (access via membership)
Security advisories	https://github.com/humansdotai/humans/security/advisories
Explorer	https://www.mintscan.io/humans
Token Explorer (ERC‑20)	https://etherscan.io/token/0x8FAc8031e079F409135766C7d5De29cf22EF897C
Block explorers list	https://docs.humans.ai/developer/block-explorers
X	https://twitter.com/humansdotai
Discord	—
Telegram	https://t.me/humansdotai
Medium	https://medium.com/humansdotai
Audit report(s)	https://github.com/humansdotai/audit-reports
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/humans-ai
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/humans-ai/

General project overview

Humans.ai describes itself as an “AI & Blockchain ecosystem”: its own blockchain (Humans Blockchain) and a product layer around AI agents/tools, where the blockchain is used for governance/verification and the economy (fees/staking/governance). The Tier‑1 Humans.ai documentation emphasizes that the network simultaneously supports the Cosmos stack and EVM compatibility (JSON‑RPC and smart contracts), and that validators are selected based on their stake of the HEART token and receive rewards/fees.

Per the Tier‑1 pages of the website, the project also claims an AI component (EVA: “AI that creates AIs”, a conversational tool) and a set of applied scenarios, “AI agents for community/company/government”. At the same time, no detailed technical description of models/metrics was found at Tier‑1 levels within this card.

Features/modules

Humans Blockchain (L1): a sovereign PoS network, the “blockchain of AIs”, mainnet since 2023‑05‑29 (per the website).
EVM compatibility: deployment of Solidity contracts, Ethereum JSON‑RPC, EVM tooling.
Validators/staking: validators and delegation of HEART, rewards and slashing (per the docs).
AI layer (positioning): EVA / AI agents (per the website), AIverse materials (partially available).

Typical scenarios

Scenario 1 (user): connects a wallet (MetaMask/Keplr) → makes transactions/interacts with dApps → pays fees in HEART.
Scenario 2 (validator/delegator): a validator runs a node → receives rewards/fees; a delegator stakes HEART → shares in the validator’s income; slashing is possible for violations.
Scenario 3 (developer): deploys an EVM contract on Humans.ai → uses Cosmos interoperability and EVM tooling.

Getting started (wallet/network)

What you need: a wallet (MetaMask for EVM, Keplr for the Cosmos part) and HEART tokens for fees/staking.
Network/chain: Humans.ai mainnet; the available explorers are listed in the documentation.
Fees: network fees and part of the validator rewards are paid in HEART (per the validator docs and the $Heart page).

Architecture/tech (non‑AI)

Components: a PoS L1 network (CometBFT), an EVM environment, a set of explorers/indexers, SDK/CLI, validator infrastructure.
Participant roles: validators, delegators, EVM contract developers, dApp users.
Where logic runs: onchain — consensus, staking, governance and smart contracts; offchain — frontends/wallets and possible AI services (the details of AI computation are not disclosed in Tier‑1 sources).
Dependencies: JSON‑RPC, wallets (MetaMask/Keplr), explorers/indexers.

Token/economics (expanded, no forecasts)

Token utility: network and platform fees are paid in HEART; the token is used for governance; validators/delegators receive rewards and fees in HEART.
Protocol necessity drivers: HEART is described as the “native token” and “fuel” of the ecosystem, and validators are selected by stake; without the token, PoS security and the fee mechanics are impossible.
Who pays fees: users who make transactions/interact with contracts.
Where fees/rewards go: to validators and their delegators (taking the validator commission into account).
Security/incentive mechanisms: staking and slashing (double sign/offline/non‑participation in governance).
Issuance/burn/distribution: detailed tokenomics/vesting are not established from the Tier‑1 pages available for this card → —.

Governance

Who makes decisions: governance via stake/votes (mentioned in the docs and on the $Heart page).
How protocol parameters change: via onchain governance (details are not disclosed within this card).
Where decisions are discussed/made: GitHub/social media + onchain governance (link not established).
Keys/multisig: —.

Security and incidents

Audits: the Etherscan token page lists a security audit (Hacken, Dec 6th, 2021) for the ERC‑20 contract; there is also an audit-reports repository.
Bug bounty: no Tier‑1 found → —.
Incidents: not established per Tier‑1 → —.
Threat model: validator risks (slashing/downtime), risks of EVM contracts and bridges, risks of the “AI layer” (promises without technical details/metrics).

Project status and timeline

Current status: mainnet (the Humans Blockchain page says “fully operational”; a “mainnet-alpha stage” is also mentioned).
Key releases/milestones: mainnet launch 2023‑05‑29 (per the website); public releases of humansdotai/humans (GitHub Releases).
Roadmap: the roadmap page requires membership/login; public Tier‑1 content is unavailable.

Ecosystem/integrations

Integrations: wallets (MetaMask/Keplr/WalletConnect), public explorers (Mintscan/BigDipper and others), EVM tooling (Solidity/Remix/JSON‑RPC).
Partners: — (in this card we do not record them without separate Tier‑1 confirmation of specific integrations).
Where it’s actually used: public explorers and the documentation on deploying EVM contracts and validation.

AI component of the project

What is real AI here? Per the Tier‑1 website, AI agents/EVA are claimed (“AI that creates AIs”, a conversational tool). However, the Tier‑1 sources available for this card contain no detailed technical description of models/versions/metrics.
What is truly onchain? Humans.ai is a PoS L1 network (CometBFT) with validators, EVM contracts and public explorers.
Why is a token needed? HEART is the native token for fees, staking/rewards and governance; the docs describe staking/slashing mechanics.
Red flags (based on the information found): a lot of marketing about “AI” without technical artifacts; conflicting supply data between the website and the Ethereum explorer; the security page in the docs is still “Coming soon”.

DecAI Fit component summary

DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	low	1
Onchain necessity	high	3
Token necessity	high	3
Evidence	Tier‑1 present	3

Details

AI reality

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

AI_0 (decision): 0
Claim (one line): not applicable: the Tier‑1 website describes an AI product/agents (see AI_1), not only intent.
Evidence: Tier‑1 — https://humans.ai
Why sufficient / why not (one line): the presence of an AI product description → AI_0 is not needed as “intent”.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 1
Claim (one line): the EVA/AI layer is positioned as a conversational tool and as a system for (auto)creating AI agents for the needs of people/communities/companies.
Evidence: Tier‑1 — https://humans.ai
Why sufficient / why not (one line): the Tier‑1 website explicitly describes the functions of the AI agent and “AI that creates AIs” → AI_1 = 1.
Conflict note (if any): the technical details of models/architecture are not disclosed (see AI_4=0).

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): within the available Tier‑1 pages, no reproducible demo/tutorial was found where the operation of EVA/an AI agent can be “touched”.
Evidence: Tier‑1 — https://humans.ai
Why sufficient / why not (one line): there are links to AI sections, but an interactive demo is not confirmed → AI_2 = 0.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — https://humans.ai
Why sufficient / why not (one line): the Tier‑1 pages contain no quantitative quality metrics for AI models/agents → AI_3 = 0.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): the available Tier‑1 sources contain no technical description of EVA models/architecture/versions; mostly product wording is available.
Evidence: Tier‑1 — https://humans.ai; https://aiverse.humans.ai/ai
Why sufficient / why not (one line): the absence of a tech spec/versions → AI_4 = 0.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Humans.ai mainnet (Cosmos + EVM).
Addresses/identifiers: chain‑id humans_9000-1 (per the repository README); public explorers (Mintscan and others); the HEART ERC‑20 contract (Ethereum): 0x8FAc8031e079F409135766C7d5De29cf22EF897C.
Evidence: Tier‑1 — https://github.com/humansdotai/humans; https://docs.humans.ai/developer/block-explorers; https://etherscan.io/token/0x8FAc8031e079F409135766C7d5De29cf22EF897C
Why sufficient / why not (one line): there is Tier‑1 confirmation of the network/chain-id and public explorers + the onchain address of the ERC‑20 representation.
Conflict note (if any): —

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

OC_2 (decision): 1
What useful logic is onchain: PoS validators/staking/slashing; EVM smart contracts and stateful precompiles (for example, staking/governance operations) per the docs.
Evidence: Tier‑1 — https://docs.humans.ai/validator; https://docs.humans.ai/developer/smart-contracts
Why sufficient / why not (one line): onchain includes consensus/staking and EVM logic, not just a token → OC_2 = 1.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 1
“Replace the blockchain” test: without the blockchain, the basic properties of a PoS network are lost: public verifiability of state, trustless execution of rules and the economy of staking/rewards/slashing.
Evidence: Tier‑1 — https://docs.humans.ai/validator; https://humans.ai/blockchain
Why sufficient / why not (one line): the project is an L1 platform where onchain is the basic entity → OC_3 = 1.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): the project has a native token, HEART.
Evidence: Tier‑1 — https://docs.humans.ai/validator; https://humans.ai/heart
Why sufficient / why not (one line): Tier‑1 sources directly describe HEART as the native token of the network/ecosystem → TK_0 = 0.
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): platform/network fees are paid in HEART (even if the payment is initiated in fiat/another crypto).
Evidence: Tier‑1 — https://humans.ai/heart
Why sufficient / why not (one line): the Tier‑1 $Heart page directly states that fees are paid in HEART → TK_1 = 1.
Conflict note (if any): —

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

TK_2 (decision): 1
Claim (one line): validators/delegators stake HEART and can be slashed for double sign/offline/non‑participation in governance.
Evidence: Tier‑1 — https://docs.humans.ai/validator
Why sufficient / why not (one line): the Tier‑1 validator documentation describes staking and slashing → TK_2 = 1.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 1
Claim (one line): HEART is used for governance (participation in votes/network parameters).
Evidence: Tier‑1 — https://humans.ai/heart; https://docs.humans.ai/validator
Why sufficient / why not (one line): Tier‑1 sources directly link the token to governance → TK_3 = 1.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): as the native token of a PoS network, HEART is not replaceable without changing the basic economics of staking/fees/governance.
Evidence: Tier‑1 — https://docs.humans.ai/validator; https://humans.ai/heart
Why sufficient / why not (one line): the token is built into the security and fees of the network → TK_4 = 0.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://humans.ai	Tier‑1 positioning of the AI agent/EVA and the “AI & Blockchain ecosystem” (AI claim).
Tier‑1	https://humans.ai/blockchain	Mainnet launch date (May 29, 2023), network parameters and positioning as an L1 “blockchain of AIs”.
Tier‑1	https://docs.humans.ai/validator	CometBFT/PoS validators, staking/rewards/fees and slashing; `HEART` as the native token of the network.
Tier‑1	https://docs.humans.ai/developer/smart-contracts	EVM compatibility of Humans.ai and the context of EVM tooling/JSON‑RPC.
Tier‑1	https://docs.humans.ai/developer/block-explorers	List of public explorers (Cosmos/EVM) for Humans.ai mainnet/testnet.
Tier‑1	https://humans.ai/heart	`HEART` as a utility token for fees and governance; fixed supply of 7.8B (per the website).
Tier‑1	https://etherscan.io/token/0x8FAc8031e079F409135766C7d5De29cf22EF897C	Onchain fact: the ERC‑20 representation of `HEART` and max total supply on Ethereum; an audit is indicated on the token page.
Tier‑1	https://aiverse.humans.ai/ai	An additional Tier‑1 AIverse page (marketing description of the AI direction).