HackMe Network
HMC economics — full guide
Chain emission · coordinator pool · settlement · audit orders
TL;DR for miners| You are NOT on Stratum | HTTP coordinator + [mono]workerpoh[/mono] leases — no :3333 share accounting |
| Your paycheck story | Coordinator accrual for accepted work → operator settlement → your [mono]HMC-…[/mono] wallet |
| PoH block subsidy | Goes to the block-producing node’s primary wallet — not auto-split to every remote GPU |
| More miners ≠ more coins | ~120 blocks/hour network-wide (30s target) — fleet size splits competition, not inflation |
Read once before scaling hashrate. Numbers below match open-source constants in [mono]internal/chain/economics.go[/mono] and the live economics page.
The #1 misconception (please read)“If I mine on the HackMe pool, every new block pays my GPU like a classic BTC pool.”
No. HackMe separates consensus emission (PoH blocks on the chain) from pool accounting (coordinator + settlement). Remote workers earn through accepted lease work credited off-chain, then settled on-chain — unless you yourself operate the node that appends blocks.
Three layers — one picture YOUR RIG (CPU / OpenCL / CUDA)
|
| claim lease + submit batch (hybrid-signed)
v
+---------------------------+
| COORDINATOR (pool) | <-- off-chain ledger: payout_hmc, stats
+---------------------------+
|
| settlement timer / operator batch
v
YOUR HMC- ADDRESS (on-chain balance after credit)
(parallel, network-wide)
+---------------------------+
| PoH CHAIN (consensus) | ~30s blocks, halving schedule
+---------------------------+
|
| block reward -> primary wallet of PRODUCING NODE only
v
operator / leader node wallet (not auto per GPU)
Layer 1 — Chain (PoH emission)What it isUseful Proof-of-Work: WASM-gated nonce search, dynamic difficulty [mono]target_mod[/mono], tip grows on valid blocks.
Supply cap| Max supply | 100,000,000 HMC |
| Genesis policy | Locked in code ([mono]policy_hash[/mono] in metrics) — no hidden mint switch |
Base block reward (empty mining — no open paid order on block)Halving every
2,102,400 blocks (~
2 years at 30s/block target), then a
tail floor:
| Epoch (blocks after genesis) | Base reward / block | Notes |
| 0 — blocks 1 … 2,102,400 | 0.010000 HMC | Initial schedule |
| 1 — … 4,204,800 | 0.005000 HMC | First halving (verified under coordinator stress load) |
| 2 — … 6,307,200 | 0.002500 HMC | |
| 3+ (floor reached) | 0.002000 HMC | Tail floor [mono]RewardTailFloorHMC[/mono] — long-term incentive |
Network-wide emission (empty mining only)Roughly
120 blocks/hour × current base reward —
independent of how many pool workers exist.
| At 0.01 HMC/block | ~1.2 HMC/hour total base emission (whole network) |
| At 0.005 HMC/block | ~0.6 HMC/hour (post first halving) |
Who receives the block subsidy on-chain?The implementation credits the node’s
primary wallet row (so [mono]GET /api/wallet[/mono] matches ledger state). The block may still record a [mono]minerAddress[/mono] for transparency — credits follow
primary wallet, not a blind header split.
Layer 2 — Coordinator (how your rig earns on the public pool)Official fair pool mode ([mono]payout_found_only=0[/mono], [mono]reward_auto=1[/mono], hybrid signer strict):
You earn for
accepted attempts inside each lease (capped by batch size), plus a
found bonus when you submit a valid hit.
Formula (matches coordinator code +
site docs):
payout_per_submit = (paid_attempts / 1_000_000) × reward_per_m + found_bonus (if valid found)
reward_per_m ≈ base_reward_hmc × 1_000_000 / target_mod
(auto-synced from canonical chain metrics when reward_auto=1)
(illustrative — live [mono]target_mod[/mono] moves with pool load):
| base_reward_hmc | 0.01 |
| target_mod | 1,000,000 |
| reward_per_m | 0.01 × 1,000,000 / 1,000,000 = 0.01 HMC per million attempts |
| Your batch (lease cap) | 4,000,000 attempts accepted |
| Attempt payout | (4M / 1M) × 0.01 = 0.04 HMC |
| Valid found hit | + found_bonus (pool default often ~0.01 HMC — see [mono]/api/pool/stats[/mono]) |
Higher pool difficulty ([mono]target_mod[/mono]↑) lowers [mono]reward_per_m[/mono] so coordinator payouts stay tied to chain economics — not arbitrary inflation.Fairness guards on the public pool- Hybrid Ed25519 on submits when strict mode is on — reduces fake-attempt payout games.
- Per-worker lease cap — official pool configures a max concurrent leases per worker id so one rig cannot monopolize the fleet.
- 429 backpressure under abuse — coordinator rejects overload instead of corrupting leases.
- Replay / stale work protection — bad submits do not accrue.
What you see locally- Dashboard → Unpaid worker accrual (pool paycheck meter).
- Pool API → [mono]total_payout_hmc[/mono], worker stats.
- This is off-chain until settlement — not the same as wallet balance yet.
Layer 3 — Settlement (off-chain → on-chain)Flow[list=1]
- You map [mono]worker-id=HMC-youraddress[/mono] via [mono]WORKER_PAYOUT_MAP[/mono] (must match operator map on settlement host).
- Coordinator accumulates [mono]payout_hmc[/mono] per worker id.
- Operator runs [mono]settle_worker_payouts[/mono] automation (official pool: timer on the order of minutes, not “once a week”).
- Explorer / wallet shows on-chain credit to your [mono]HMC-…[/mono] address.
Rule of thumbAccrual ≠ wallet until settlement completes. Always verify on
pool/explorer before scaling hardware spend.
Layer 4 (product) — Paid audit ordersHackMe is also a
useful-work marketplace: clients escrow HMC for WASM-gated audit tasks; PoH blocks tied to an open order must match task reward or the chain rejects the append.
When a customer opens a prepaid order| Escrow (prepaid) | [mono]reward_hmc × target_solves[/mono] — held for miners solving the task |
| Platform fee | 5% of prepaid → [mono]DevFeeAddress[/mono] ([mono]OrderPlatformFeeRate = 0.05[/mono]) |
| Burn accounting | 10% of prepaid tallied as burned supply metadata ([mono]OrderBurnRate = 0.10[/mono]) — separate from transfer fees |
On-chain transfer fees (different split — do not mix with order open):
| Burn share | 30% of [mono]fee_units[/mono] |
| Dev/platform share | 70% of [mono]fee_units[/mono] |
Orders are the long-term demand layer for useful compute; the public pool’s steady accrual path is coordinator-based even when you are not solving a commercial order yourself.
HackMe vs classic Stratum pool | Classic Stratum (BTC-style) | HackMe official pool |
| Protocol | TCP :3333 shares | HTTP [mono]/pool/coordinator[/mono] leases |
| Share → block | Pro-rata block reward split | Coordinator [mono]payout_hmc[/mono] policy + settlement |
| Block finder | Pool wallet often central | Producer node primary wallet + separate pool ledger |
| Work unit | Hash on block header | WASM PoH nonce ranges + hybrid signatures |
Miner checklist (official pool)[list=1]
- Download only from hackme.tech/downloads.html — verify SHA256.
- Set [mono]HACKME_PUBLIC_AUTHORITY_BASE=https://hackme.tech[/mono].
- Configure [mono]WORKER_PAYOUT_MAP[/mono] → your real [mono]HMC-…[/mono] payout address.
- Start [mono]hackme-node[/mono] + [mono]workerpoh[/mono] (Windows installer or Linux bundle).
- Watch Unpaid worker accrual on 127.0.0.1:8080.
- Confirm settlement on explorer before buying more rigs.
Live numbers & transparency
FAQQ: I found a block — why didn’t my GPU wallet jump instantly?A: Block subsidy credited the
producing node’s primary wallet path. Your rig’s income is still coordinator accrual → settlement unless you run the producer yourself.
Q: Does adding 1,000 miners mint more HMC per hour?A:
No for base schedule — only ~120 blocks/hour. More miners compete for coordinator accrual and block-finding probability.
Q: Is this an ICO or pre-mine sale?A:
No ICO · no token sale. Experimental RC network — verify everything on explorer before trusting payouts.
Q: Can policy change?A: Pool coordinator knobs and settlement timing are
operator policy (announced on
News). Chain constants require a
coordinated upgrade — not a silent remote toggle.
DisclaimerHackMe Network is experimental release-candidate software (0.1.0-rc11g at time of writing). Mining and cryptocurrency involve risk. This post is technical documentation, not investment advice. Pool parameters and settlement timing may change with notice on the official website. English is authoritative; translate at your own risk.
