You don't have to believe.
You verify.
NW Energy does not ask for blind trust. The operation is designed to be observed by independent layers: public pool data, AriesEye Oracle validation, evidence recording on IPFS and the dashboard. No single layer is absolute proof — the strength is in the combination.
00Output available for lease — now
This panel shows the capacity open for immediate lease (not the operation's total output). When a lease is closed, the number drops automatically. When there is free capacity available, it appears here — mirroring the Oracle in real time.
01Operational proof, not a promise
The physical operation (real ASIC machines, energy, maintenance) generates signals that can be observed: connected workers, delivered hashrate, snapshots, history. The proof is born from operational data — and can be cross-checked.
02ViaBTC — the public, independent layer
When available, the public ViaBTC links act as an open layer for observing the operation. This lets any interested party observe operational signals directly at the pool source, without relying exclusively on our internal dashboard. ViaBTC does not replace the Oracle; it complements it as an open source.
kingminer202510 · Observer ViaBTC
Public observation link for the operational account (worker, hashrate, status).
kingminer20255 · Observer ViaBTC
Second official observation account, when applicable to the current operation.
Independence
Even if the Oracle is unstable or temporarily unavailable, the public pool layer remains observable in real time — straight from the source, outside our control.
03AriesEye Oracle — validation and organization
The Oracle is not magic. It is the layer that validates, organizes, records and cross-checks operational events: it collects data from the local agent, checks signatures (HMAC), associates time and origin, and presents everything in a readable way.
Valida
Checks whether the data package came from who claims to have sent it (signature) and whether it is intact (hash).
Organiza
Associates worker, time, origin, metric and status in a structured, queryable record.
Registra
Preserves the history and, when applicable, sends the evidence to an external registry (IPFS).
04Pinata / IPFS — evidence preservation
Operation snapshots, reports and JSONs can be recorded on IPFS via Pinata, generating a CID — a unique identifier of the content. If the file changes by a single comma, the CID changes. This makes the evidence tamper-evident.
What IPFS proves — and what it does not
Pinata/IPFS does not alone prove that a machine is on. It proves that a specific digital piece of evidence was preserved and can be audited.combination: operational data + signature + time + origin + Oracle + public ViaBTC layer + record.
The CIDs of published evidence are available on each operation's dashboard, verifiable directly on any IPFS gateway.
05How to read a proof
Each proof record carries fields you can check yourself. Anatomy of a record:
worker…… nw-s19p-007 — which machine/identity generated the data
pool……… ViaBTC — where the hashrate appears publicly
hashrate… 109.4 TH/s — capacity observed at the moment
status…… ATIVO — reported operational state
hash……… 0x8f3a…c21e — fingerprint of the package (integrity)
CID………… bafy…q4nd — address of the evidence preserved on IPFS
origin…… local-agent · HMAC ok — who collected it and whether the signature checks out
validating… Oracle · recorded — the layer that validated and organized
observation routine snapshot — context of the record
The values above are ilustrativos (anatomy of the format). Real records appear on the proof dashboard when the Oracle is connected, and can be checked field by field.
06What the proof confirms — and what it does not confirm
Transparency requires telling both sides. This is the honest boundary of operational proof:
✓ The proof confirms
- the existence of operational records;
- operation signals (worker, hashrate, status);
- snapshots and technical history;
- availability observed at recorded moments;
- that a specific piece of evidence was preserved (CID).
✗ The proof does NOT confirm
- guaranteed profit or fixed yield;
- future output;
- future BTC price;
- unlimited availability;
- absence of risk.
Mining has variable output — it depends on network difficulty, BTC price, uptime, energy, pool and maintenance. The proof demonstrates that the operation existed; decisions should take the risks into account.risks and go through KYC, contract and validation.
07Current state of NWM backing
The AriesEye Oracle is in operational validation mode for the NWM backing. We present the real state without dressing it up. · state as of 2026-07-09
The public ViaBTC output is being observed in real time. The Oracle generates a snapshot, daily hash and integrity signature.GROUPED_OPERATION, with backing eligible for NWM, physical pairing in progress (Agent NW-SP-002).Current status: observed pool active, physical proof received by the Oracle, NWM snapshot active, backing under final validation.
Verify. Ask. Decide calmly.
The evidence architecture exists so you don't have to rely on our word.