[ANN] HackMe Network — useful PoW pool · WASM · public coordinator · rc9

[kapa77]

HackMe — B2B fuzz audits with a CI gate you can wire tomorrow

Useful-PoW network (HMC) + customer fuzz product on the same hub.

What shipped for customers

• Flow: register → wizard (Scan / Audit / Deep) → status → HTML report + CI gate
• Crash-first triage: gate PASS/FAIL on crash / hang / ASan / memory only — detector noise is appendix
• Report card: verdict · assurance note ("not proven secure") · target fingerprint
• Escrow 20/80 transparent; unused bounty refunds; report-token auth hardened
• Pool: PoH miners auto-switch to orders; workerfuzz fleets dig distributed fuzz

Honest packages

• Scan — WASM smoke, local quick check
  
• Audit — WASM + native/ASAN repro path, pool + PoH attach
  
• Deep — byte corpus + hours-scale budget (signals beyond Audit, not just a bigger number)
  

Example campaign
HackMe Bootstrap Audit · cjson — runs progressing, crash-first gate, clean / no critical crash-class.
We do not invent critical vulns for marketing. CLEAN means no crash-class findings at the budgeted runs — not a security proof.

Links
Developers: https://hackme.tech/developers.html
CLI: https://hackme.tech/downloads.html#fuzzing-client
Tracker: https://hackme.tech/fuzzing-console.html
Campaigns: https://hackme.tech/fuzz-campaigns.html
Pool: https://hackme.tech/pool/coordinator
Downloads: https://hackme.tech/downloads.html

CLI

Code:

hackme-fuzzing register --save
hackme-fuzzing wizard --wasm ./guard.wasm --package audit --title "My guard"

[kapa77]

Re: HackMe Network — Useful PoW + Pool Fuzz · HMC

Update: 0.1.0-rc13 (2026-07-24) — 48h pool soak PASS, ISO aligned, rebuilt binaries.

TL;DR
• 48h mining soak PASS — continuous snapshots, gaps >10 min = 0
• Soak: ~69–197 GH/s (avg ~137) · workers 8–20 (avg ~13) · tip ~199444 → ~204005
• ACK ~0.13 ms · tiny signed rejects · fleet recovered after coordinator restarts
• Win/Linux + fuzz CLI + HackMe OS ISO all on rc13 (same SHA256 on GitHub + hackme.tech)
• Live pool now: ~12 workers · ~145 GH/s · tip ~204k

What is HackMe?
Open-source (AGPL-3.0) useful Proof-of-Work network:
• PoH mining — GPU workers on public HTTP SoloPool (not Stratum)
• Pool fuzz / orders — customers escrow HMC; miners dig WASM-gated work
• On-chain HMC — wallet + Activity on local node (127.0.0.1:8080)

Not a meme coin — we run our own pool, ship our own node, publish research ledgers.

Why rc13
rc12w = Wallet Activity + security hardening.
rc13 = ops proof: 48h soak held, then full rebuild including ISO (rc12w still had ISO on rc11s).

Honest note: confirms operator/private-pool readiness under this fleet. Not trustless L1. Not CEX-ready.

Downloads — verify SHA256
Channel: https://hackme.tech/downloads.html
GitHub: https://github.com/jokeez/hackme/releases/tag/0.1.0-rc13

| Artifact | SHA256 |
|----------|--------|
| hackme_0.1.0-rc13_windows_setup.zip | 846812f37b8113915388501a39be53e5ad19fb6165ca7b6f64d38be94dc97e92 |
| hackme_0.1.0-rc13_linux.tar.gz | c7d9fe2d0f901f1f973ced43d9af8828728cd9786b293b83b52f1a36ae7c8e90 |
| hackme-fuzzing-0.1.0-rc13-linux-amd64 | 94e4d222d280878378edd65debbc600cce945e4fed016af16e7aaf0ef7ba0ace |
| hackme-fuzzing-0.1.0-rc13-windows-amd64.exe | 1c93f976b81d29c7e244fb977ccbbdb01338ee10e61960651235ed96cd468e89 |
| HackMe-OS-0.1.0-rc13-amd64.iso | 1adf63cc8252c25ae040fc9362d78ac3209f0a5bf8babb05cd394f156ad5e60f |

Full list: https://hackme.tech/dist/release_0.1.0-rc13/SHA256SUMS.txt

Quick start — Linux

Code:

tar -xzf hackme_0.1.0-rc13_linux.tar.gz
cd linux
bash setup_hackme_miner.sh
bash start_hackme_miner.sh

Quick start — Windows
Download Setup .exe or windows_setup.zip → install → Start HackMe Miner.

Developers / B2B fuzz

Code:

hackme-fuzzing register --base http://127.0.0.1:8080 --save
hackme-fuzzing wizard --wasm guard.wasm --package audit

Links
• Site: https://hackme.tech/
• Pool: https://hackme.tech/pool/coordinator
• Explorer: https://hackme.tech/pool/explorer
• GitHub: https://github.com/jokeez/hackme/releases/tag/0.1.0-rc13
• Telegram: https://t.me/hackme_tech
• Discord: https://discord.gg/QMxSeaTSrQ

Pool is live. Verify downloads. Questions/setup in-thread welcome.

— HackMe team

[kapa77]

HackMe — research + pool pulse (2026-08-03)

OSS CVE Watch · libheif Day 10/14 — CLEAN
• ~198.6M libFuzzer exec · ~23.6h ASAN · ~2,338/s
• Corpus 2975 · 7255 edges · ASAN=0
• Days 1–10 cumulative ~1.61B exec on persistent HEIF/AVIF corpus
• Ledger: https://hackme.tech/reports/oss-cve-watch-libheif/day10.html
• Hub: https://hackme.tech/reports/oss-cve-watch-libheif/

We publish CLEAN days. CVE number only after ASAN repro + maintainer triage.
Days 11–14 continue on the same public cadence.

Live pool (same hour)
• ~21 workers online · ~140+ GH/s · tip ~234k
• Release channel: 0.1.0-rc13 (Win/Linux/ISO + fuzz CLI)
• Explorer: https://hackme.tech/pool/explorer
• Downloads + SHA256: https://hackme.tech/downloads.html

Honest note: no open B2B PoH orders right now — fleet on baseline PoH + pool fuzz research work.
When a customer order is open, scheduler flips to orders; until then miners earn fair-pool accrual as documented.

Telegram: https://t.me/hackme_tech
— HackMe ops

[kapa77]

HackMe research update — OSS CVE Watch · libheif series FINALE

We closed Day 14/14 on libheif (HEIF/AVIF). This is the end of the published series, not a routine mid-series day.

Day 14
• 316,619,059 libFuzzer executions
• ~39.5h ASAN depth · ~2,228 exec/s
• corpus 3,215 · 7,509 coverage edges
• ASAN=0 → CLEAN

Series Days 1–14
• ~2.57 billion libFuzzer executions (~2,568,698,936)
• ~325 hours ASAN time
• 14/14 published days CLEAN
• total ASAN heap crashes in budget: 0
• one persistent HEIF/AVIF corpus across the whole run

Public ledger (HTML, not a screenshot):
https://hackme.tech/reports/oss-cve-watch-libheif/day14.html

Series hub:
https://hackme.tech/reports/oss-cve-watch-libheif/

Pool (snapshot)
• 27 workers · ~681 GH/s
• https://hackme.tech/

CLEAN means no crash inside that day’s fuzz budget. It is not a CVE claim and not a proof of security.

Site / downloads / Telegram: https://hackme.tech/ · https://t.me/hackme_tech

[kapa77]

HackMe update — research close + honest exchange roadmap

libheif OSS CVE Watch: Day 14/14 CLEAN (~2.57B series exec, ASAN=0).
Ledger: https://hackme.tech/reports/oss-cve-watch-libheif/day14.html
(CLEAN = no crash in budget — not a CVE claim.)

Pool remains live (useful-PoW / HMC): https://hackme.tech/

Own market (not a third-party listing announcement):
- Now: paper / private-lab Spot + Convert UI
- Soft: static paper SPA ~mid-September (no public matching API)
- Live custody / foreign CEX: only after custody + security gates
No ROI promises. No fake “Tier-1 listing” claims.

Contacts: https://hackme.tech/contacts.html
GitHub: https://github.com/jokeez/hackme

[kapa77]

Re: HackMe Network — Useful PoW + Pool Fuzz

Update: 0.1.0-rc14 (2026-08-11) — customer-first pool fuzz scheduling + infra fixes for miners

TL;DR

In E2E order flows on Aug 11, rc14 reduced claim latency from seconds to milliseconds and increased pool completion throughput ~5–7×.
The pool now prioritizes **customer orders** (not bootstrap-only starvation), with hybrid dig on customer campaigns.

Before → After (E2E evidence)

Code:

Claim latency p50:   ~6000 ms  →  ~1–5 ms
Claim latency p95:   ~12–20 s  →  (stays low under customer-first priority)

Pool throughput:     ~4.6 done/min → ~25–32 done/min
Customer orders:     256/256 → 256/256 completed in ~26 min (~9.8/min)

Customer-first share:
  ~23% (before) → ~4× faster than bootstrap-tier in parallel A/B

Hybrid dig:
  idle path (concurrency=1, claim_gap 400ms, backpressure 35%) → fixed
  hybrid dig ON: 2/50/2000/10%, FINDINGs on customer campaigns

What rc14 actually ships

• **Customer-first priority:** scheduling tuned so pool fuzz progress tracks real customer order completions.
• **Hybrid dig is ON and effective:** FINDINGs happen on customer campaigns.
• **Identity + resync correctness:** `owner_ref` preserved; bootstrap resync fixed.
• **Escrow economics unchanged:** escrow remains 20/80.
  

For miners / operators

rc14 is designed for running the coordinator + fleet without the earlier slow/broken paths:

• pool workers: rc14 scales by order throughput (not “one GPU at a time”)
• operational fixes: less scheduling wall time; tuned claim gap/backpressure
• bootstrap starvation: removed via resync + customer-first priorities

Pool coordinator:
https://hackme.tech/pool/coordinator

For B2B fuzz teams (buying fuzz via orders)

If you’re integrating fuzz through customer orders, rc14 is the release you want because:

• orders complete faster in the same test envelope (256/256 in ~26 min)
• pool cycles are spent where customers actually need progress
• hybrid dig/fuzz runs together on the same customer workload

Fuzz guide:
https://hackme.tech/fuzz-guide.html

Downloads / GitHub release

Downloads:
https://hackme.tech/downloads.html

GitHub release:
https://github.com/jokeez/hackme/releases/tag/0.1.0-rc14

Scope note (honest)

This post reports E2E pool + scheduling behavior under real order flows.
It is not a claim of guaranteed future uptime, not a trustless L1 promise, and not exchange readiness.

Thanks

Pool ops, fuzz buyers, and miner operators make the measurements possible. Verify downloads before running.

[kapa77]

We’ve shipped **HackMe 0.1.0-rc14x** as a pre-exchange hotfix.

This is not a “new tokenomics” release or a money-path rewrite. It’s a product-truth release for the B2B fuzzing side of HackMe.

What changed:

- fuzz reports now make their **evidence scope explicit**
- raw findings and grouped display rows are clearly separated
- crash-first gate logic is easier to understand and audit
- repeated findings no longer look like fake “new bugs”
- Scan / Audit / Deep campaigns now show clearer depth evidence in reports

In short: the same hybrid useful-PoW + fuzzing flow is still there, but the output is now much more honest and useful for developers.

This matters because a security product dies when the report surface is noisy or misleading. We’d rather ship fewer claims and more truth.

rc14x is meant as a **pre-exchange stabilization line** before the Sept. 15 exchange push.

Downloads:
https://hackme.tech/downloads.html

GitHub release:
https://github.com/jokeez/hackme/releases/tag/0.1.0-rc14x

Please verify `SHA256SUMS.txt` before running any binaries.

Next focus is the exchange track. Bigger fuzz/product expansions come later.

[kapa77]

[ANN] HackMe 0.1.0-rc15 — B2B fuzz on a live PoH mining pool

HackMe is a hybrid chain: SHA-256d mining + WASM security work on the same pool.
rc15 is the production cut for customer fuzz campaigns on the public coordinator.

What's new in rc15:
• B2B fuzz Phase 2 wizard packs (secrets, script_bounds, filter_utf8, parser_expat)
• Scan/Audit/Deep tiers with honest byte ceilings (256 / 1K / 4K max)
• Pool anticheat: dynamic worker leases, exec cap 64 per unit, fail-closed replay checks
• Mining dashboard refresh — OSS libheif research archived CLEAN (~2.57B exec); live customer bootstrap orders visible on #mining

Live now:
• Hub: https://hackme.tech (node 0.1.0-rc15)
• Pool hashrate: ~800+ GH/s official HMC pool
• Downloads + SHA256: https://hackme.tech/downloads.html
• Release: https://github.com/jokeez/hackme/releases/tag/0.1.0-rc15
• Newsroom: https://hackme.tech/news.html

Miners: point your rig at the official pool — when B2B fuzz orders are active, scheduler switches to orders mode and pays HMC for WASM security work alongside PoH.

Not financial advice. Verify checksums. Research receipts ≠ CVE claims.

[kapa77]

HackMe Network — 0.1.0-rc16 (update channel + signed apt)

Status: LIVE
Site: https://hackme.tech
Downloads: https://hackme.tech/downloads.html
GitHub: https://github.com/jokeez/hackme/releases/tag/0.1.0-rc16

Summary
rc16 adds a production-style self-update path so miners/operators do not reinstall from scratch on every cut.

What changed

• Signed apt repository: package hackme-node (stable)
  
• One-shot bootstrap:

Code:

curl -fsSL https://hackme.tech/apt/install.sh | sudo bash

• Fast upgrade helper:
  Code:

  curl -fsSL https://hackme.tech/apt/upgrade.sh | sudo bash

  • L1 updaters: update_hackme_miner.sh / .bat (preserves .env, data, logs)
  • latest.json channel: https://hackme.tech/dist/latest.json
  • Windows dashboard update affordance + Setup updater
  • HackMe OS ISO rebuilt for rc16 (verify SHA256SUMS-iso.txt)
  
  Integrity
  Always verify published SHA256SUMS before run/flash:
  https://github.com/jokeez/hackme/releases/tag/0.1.0-rc16
  
  Notes
  Useful-PoW network / public pool / local B2B fuzz orders on 127.0.0.1 — unchanged model.
  This is software infrastructure progress, not a price call.
  
  Not financial advice.