HMX Token Whitepaper · 2026

HumanX

An open collaboration network for humanoid robots.

Connecting real-world tasks, trusted payments, authorized data, and joint development under shared rules.

Download PDF
Max supply
1,000,000,000
Public allocation
35%
Participant roles
6
HMX protocol asset Task release Execution Verification Settlement Authorization Reuse

One loop. Six steps.
Value stays in the network.

01 — The protocol loop

A robot order is a service.
This makes it a record.

Every engagement follows the same path — from a written task to a reusable capability. Nothing moves forward until the previous step is proven.

  1. 01

    Task release

    Scope of work, price, timelines, acceptance criteria, AI intervention rules and dispute procedures are fixed in a versioned contract.

  2. 02

    Task execution

    Operators run the job on site and submit quantities, exceptions and attachments as evidence.

  3. 03

    Proof verification

    Independent reviewers check deliverables against the accepted scope. Partial acceptance and appeals are first-class outcomes.

  4. 04

    Commercial settlement

    Payment clears in fiat, stablecoin or enterprise finance — with fees, refunds and reconciliation on the record.

  5. 05

    Contribution authorization

    With explicit consent, data and tooling from the job can enter the public program under defined rights.

  6. 06

    Capability reuse

    Templates, adapters and standards from one delivery lower the cost and effort of the next.

Safety stays off the chain. Robots, real-time control and safety systems operate independently. A blockchain disruption must never cause an emergency stop or require on-site intervention.

02 — Why a token

Three jobs.
One shared asset.

A

Role commitment

Participants lock HMX to take on public responsibilities — and are held accountable for violations that are predefined and verifiable. Locking never replaces qualifications, independence or track record.

Lock · appeal · exit window

B

Contribution incentives

A capped supply and a results-based budget fund the things every operator needs: public data, adapters, evaluation frameworks and standards. Rewards follow verified results, not upload volume.

Budget · milestones · verification

C

Shared governance

Participants decide on public budgets, protocol standards and key network parameters — inside a clearly defined scope of delegated authority.

Propose · review · vote

A single robot order can cover equipment and on-site services. It rarely funds the adapters, datasets and standards that every operator depends on. HMX lets many independent entities co-own that shared layer — as payment, staking and security deposits, not as a claim on customer funds.

03 — Why HMX

Public goods need
a public balance sheet.

An adapter can serve several operators. One evaluation toolkit can support many customers. Good data can serve many development teams.

When the benefit is shared, the cost should not sit with one participant. HumanX turns public deliverables into a shared budget, a verification process and a contribution incentive.

  • 01
    Make public role commitments enforceable

    A verifier's obligations are defined in advance, and so are the consequences.

  • 02
    Reward verifiable public contributions

    Payment is tied to outcomes that are used, reused and maintained.

  • 03
    Run budgets and standards in the open

    Proposals, objections and final decisions are disclosed.

  • 04
    Transfer or exit under defined conditions

    Rights are not trapped. Exits have waiting periods and unresolved cases are handled.

04 — Architecture

Six modules.
One record.

Each module owns one question: what was agreed, who did it, what proves it, who accepts it, how it settles, and how the protocol records it.

M1

Task module

Scope of services, pricing, timelines, acceptance criteria, AI intervention rules and dispute procedures. Material changes require a new contract version.

Versioned contracts
M2

Identity & capability

Separates equipment, operators, authorizations and signing credentials. Supports switching, revocation and recovery.

Roles & keys
M3

Evidence

Links task versions, execution events, quantities, exceptions, AI intervention, customer acceptance and attachment integrity.

Tamper evidence
M4

Verification & dispute

Handles full and partial acceptance, additional evidence and disputes. Decisions and appeal channels are retained.

Acceptance records
M5

Settlement

Reconciles contracts, fees, refunds and actual payments across fiat, stablecoin and enterprise finance.

Fiat + on-chain
M6

Protocol module

HMX distribution, vesting and release, role binding, public budgets and governance processes — the layer that makes the network self-maintaining.

HMX lifecycle

Evidence proves integrity, not physics

An integrity proof can show a record was not altered. It cannot independently prove a physical event happened. HumanX says so, and keeps human verification in the loop.

Data stays where it belongs

Raw video, customer contracts, detailed logs and personal data stay off-chain in a trusted environment. Only necessary records are written on-chain, after a privacy assessment.

05 — The flywheel

Delivery
becomes capability.

A job that is done well produces more than a payment. It produces authorized experience, better tools, and a cheaper next job.

Data workflow

  1. Submit a need
  2. Confirm rights
  3. Launch collection
  4. Quality verification
  5. Licensing and payment
  6. Evaluation and use
Realdelivery Authorizeddata Bettertools Lower cost of the next integration

Commercial revenue from data licensing goes to the party holding the agreed rights. Joining a task does not grant consent to train models on its data.

06 — Tokenomics

One mint.
No surprises.

HMX has a fixed maximum supply. It is minted once, allocated to the treasury and a release contract, and never increased.

NameHMX
Maximum supply1,000,000,000
Supply mechanismOne-time mint
Future increasesNot planned

Cross-network bridging does not increase total supply and follows lock or burn mechanisms.

AllocationShareAmount
Public contribution & ecosystem
350,000,000

Data, tools, standards and infrastructure maintenance

Protocol treasury
200,000,000

Approved public network operations and reserves

Core team
180,000,000

Long-term development and ongoing services

Early investors
120,000,000

Capital injected against actual funding, with a clear vesting schedule

Community initiatives
80,000,000

Limited, real participation and community programs

Initial liquidity
50,000,000

Liquidity deployed at launch

Special research & partnerships
20,000,000

Dedicated projects executed on results

Total100%1,000,000,000

Commercial money and protocol money stay apart

Task payments are not automatically converted into token purchases. Public rewards are not counted as the customer's revenue. Equity returns and the protocol treasury are accounted for separately.

Fees are disclosed before they apply

Protocol service fees are specified by public rules, published in advance, and cannot be raised retroactively through governance.

07 — Use cases

What the token
is actually for.

01

Protocol role locking

For verifiers and public roles

HMX locking applies to specific roles in public verification and ledger maintenance. Admission still depends on professional qualifications, independence, real service capability and history — a lock does not replace any of them.

  • Responsibilities, permissions and scope of service
  • Locking amount and calculation method
  • Predefined violation types and evidentiary standards
  • Appeal procedures and unresolved cases
  • A recommended 30-day exit waiting period

Penalties apply only to predefined, verifiable violations. Ordinary failures and reasonable judgment calls are not misconduct. Customer loss protection comes from contracts, deposits and insurance — the token is not the sole source of compensation.

02

Public contribution rewards

For builders of shared capability

Public programs prioritize the things that compound: reusable adapters, task and evidence standards, authorized datasets with clear uses, independent testing tools, and maintenance of public infrastructure.

  • Each initiative publishes budget, verification standards and milestones up front
  • Rewards follow verified results — not upload volume or device registrations
  • Software budgets include a support period after release

Rewards are released in phases, with verification and monitoring in place. Disbursed cash, tokens and unvested amounts are tracked separately.

03

Protocol governance

For people who maintain the network

Governance covers public budgets, standard versions, partial role rules and authorized network parameters — and nothing else.

Tokens do not grant the right to:

  • Withdraw customer funds
  • Force disclosure of customer data
  • Unilaterally change existing commercial contracts
  • Control the physical operation of robots
  • Revoke legally acquired data rights

08 — Governance

Authority moves
on purpose.

Governance is handed over in three phases. Each phase is earned by operating results, not by announcing a roadmap.

Phase 1

Transparent operations

The core team leads under product and customer contracts. Allocations, permissions, budgets and major changes are disclosed publicly.

The network is not described as fully decentralized before it is.

Phase 2

Joint budgeting & standards

Clients, operators, developers and verification institutions set standards and validate public projects together. Conflicts of interest are disclosed.

No party may independently verify its own payments.

Phase 3

Limited protocol governance

Clearly defined items move on-chain: public budgets, standard versions and designated parameters.

Major changes carry a recommended execution delay of at least 7 days.

Decision path

  1. Proposal
  2. Public discussion
  3. Impact review
  4. Voting
  5. Implementation (with delay)
  6. Report

Supporting and opposing opinions are published alongside every final decision — to prevent opaque controllers forming quietly. Treasury spending supports approved public goods; it is not distributed equally among holders.

09 — Roadmap

Seven phases.
Seven gates.

No phase starts because the previous one launched. It starts because the previous one passed its acceptance criteria.

  1. 01

    Use case validation

    Contract templates, customer onboarding, pilot payment setup.

    GateVerified real demand and payment capability
  2. 02

    Initial product release

    Tasks, evidence, acceptance and settlement in one flow.

    GatePositive customer ROI and real-world usage
  3. 03

    Operator onboarding

    Adapters, standard versions and comparable operational records.

    GateMore operators, lower onboarding cost
  4. 04

    Public contribution program

    Dataset or tooling projects with independent verification.

    GateOutcomes adopted in practice
  5. 05

    Protocol role trial

    Locked templates, dispute resolution and an exit drill.

    GateFeasible cost, real enforcement, service continuity
  6. 06

    Token launch

    Issuance materials, contracts, release and governance setup.

    GateAuditable entitlements and permissions
  7. 07

    Governance expansion

    Public budget and transfer of standardized authority.

    GateIndependent participation and multi-stakeholder decisions

10 — Disclosure

Measured in public.
Or not claimed at all.

Device registrations, wallet balances and transaction volume alone do not prove a network works. These are the numbers HumanX commits to publishing.

Business

Paying clients, contract value, platform revenue, direct payment costs, client implementation costs.

Delivery

Task acceptance rate, dispute rate, settlement time, manual intervention rate, cost of repeated integration.

Contribution

Verified public outputs, independently adopted use cases, maintenance sustainability, real use of authorized data.

Protocol

Identified service providers, governance participation, treasury spending, reward distributions, future unlock plans.

Dependency

Revenue share of top clients, portion of related-party transactions, share of clients verified by leading institutions, balance retained after subsidies and exits.

Definitions, calculation methods, counting scope and sampling constraints are disclosed alongside the numbers.

11 — Risks

The honest list.

Every network has failure modes. Writing them down is the first mitigation.

RiskPotential impactMitigation principle
Insufficient robot capability or economics Clients stop buying Limited pilots in specific scenarios; compare viable alternatives
No real use case for the token No long-term holding or participation Validate with real entitlements and role-based demand
Price and liquidity volatility Uncertain participation costs and exit values Stabilize commercial payments in fiat; keep rules lockable and predictable
Reward abuse Budget leakage and invalid metrics Demand review, independent verification, delayed disbursement
Verification appeals Settlement errors and reputational damage Manage conflicts of interest; allow re-verification; enforce limited authority
Unclear data ownership Inability to use data or assume responsibility Define permissions first, then grant access with consent; keep rights records
Contract or permission flaws Asset losses and service disruption Independent review, phased rollout, transparent permission settings
Governance centralization A small group controls public rules Delegated authority, transparency, execution delays, an appeals process
Changes in legal classification Restrictions on issuance, transfer or service Local regulatory assessments and adjustments

12 — Participate

Seven ways in.
All of them real.

Participation opens progressively, based on product maturity and actual business needs — not on a countdown.

  • Enterprise customers

    Propose real-world tasks; help set payment pilots and acceptance standards.

  • Robot operators

    Onboard devices and services; validate cross-scenario payment workflows.

  • Device & software partners

    Build certified adapters; take part in compatibility and version maintenance.

  • Developers

    Contribute open tools, interfaces and sample projects.

  • Data rights holders

    Join clearly defined, properly authorized data projects for specific uses.

  • Verification institutions

    Take part in independent reviews, conflict management and dispute procedures.

  • Protocol participants

    Supervise and govern the public budget according to the rules.

13 — In one breath

Turn real work
into real revenue.

Let qualified contributions
compound into capability.

Enable collaboration
through shared rules.

HumanX — building the future of open collaboration for robot services.

Cover of the HumanX HMX Token whitepaper
28 pagesPDF

14 — The document

Read it in full.

The whitepaper covers the network model, six modules, token supply and allocation, three governance phases, the implementation roadmap and the risk register — in 28 pages, no marketing filler.

Download PDF

HMX Token Whitepaper · Release 2026 · English

HumanX — HMX Token Whitepaper

Loading the whitepaper…

3.6 MB document. On a slow connection this can take a moment.