Proof-of-operation system · NW Aganah

You don't have to believe. You verify.

AriesEye exists for a single mission: prove that a physical, operational and economic reality existed, was recorded, was signed, was preserved and can be audited. — by anyone, at any time, without relying on our word.

In mining, the gap between what is promised and what is proven is where the risk lives. AriesEye closes that gap: it turns the real telemetry of the machines into understandable proof — hashrate on the public pool, integrity hash, CID on IPFS, timestamp and dashboard. Proof-of-operation does not guarantee returns — it demonstrates that the operation existed and can be examined.

The problem it solves

Proof is worth more than a promise

The "hashrate token" market carries a recurring flaw: claimed capacity that no one can verify independently. AriesEye was designed to be the opposite of that.

01

O problema

Projects promise infrastructure without providing a continuous, independent means to confirm that it exists, operates and produces the claimed hashrate.

02

A resposta

Collect operational evidence directly from the hardware, preserve it as cryptographic proof on IPFS and cross-check it with public pool data (ViaBTC).

03

The principle

Conservative by design: a false confirmation is worse than honest uncertainty. The system prefers the "pending" state to a verification it cannot prove.

From machine to record

The proof flow, in eight stages

Each stage is independent enough that a failure in one does not corrupt the others. If the oracle goes down, the proofs remain preserved on IPFS. If a pool source becomes unavailable, the physical readings stay recorded.

ESTÁGIO 01

Physical ASIC

The machine operates and generates real hashrate, under VNish firmware.

ESTÁGIO 02

Local Agent

An agent reads the telemetry on site: hashrate, temperature, workers.

ESTÁGIO 03

Pool / ViaBTC

The hashrate appears publicly on the pool — independent verification.

ESTÁGIO 04

Proof Packet

The data becomes an HMAC-signed package, tamper-proof.

ESTÁGIO 05

IPFS / CID

The package receives a unique, immutable content identifier.

ESTÁGIO 06

Oracle

The oracle validates the HMAC, breaks it down per machine and cross-checks with the pool.

ESTÁGIO 07

Dashboard

You track status, hashrate and metrics in clear language.

ESTÁGIO 08

Blockchain

When applicable, the hash is anchored on-chain (currently in conservative mode).

Conceitos

The vocabulary of proof

Proof-of-Operation

The evidence

Proof that a physical operation existed and was recorded — distinct from a contract audit and without being a promise of results.

Hash

Fingerprint

A mathematical signature of a piece of data. If the data changes, the hash changes — this is how integrity is ensured.

CID / IPFS

Content address

An identifier in distributed storage. Retrieving a CID returns exactly the original file, without ambiguity.

HMAC

Origin signature

It confirms that the proof package came from who claims to have sent it, and that it was not altered along the way.

Timestamp

Timestamp

Proves when the record was made, anchoring the proof in time.

Dashboard

Human-readable

Where all of this becomes readable information: status, hashrate, output and organized proofs.

Verifiable now

Six public contracts on the BNB Smart Chain

The ecosystem does not ask for trust — it publishes it. Each contract below is deployed and verifiable on BscScan. Click and check the code yourself.

Responsible transparency

What is public and what is private

Radical transparency does not mean exposing client data. AriesEye publishes integrity — hashes, timestamps and technical proofs — while rigorously protecting what is sensitive.

Public
  • Token contract verified (BscScan)
  • NWM contract address and on-chain supply
  • Public transactions and hashes
  • Non-sensitive CIDs on IPFS
  • Aggregate hashrate on the ViaBTC pool
  • Selected technical proofs
Private · protected by LGPD
  • Tax ID and documents
  • Full contract and supporting documents
  • Address, phone, email
  • KYC data and source of funds
  • Sensitive commercial data
  • Workers, IPs and specific pool accounts
Technical note. Personal data and sensitive documents are never recorded directly on a public blockchain. The blockchain records only hashes, CIDs and technical references.
Beyond mining

A proof layer that serves any sector

The AriesEye thesis — record, sign, preserve and audit a reality — is not exclusive to Bitcoin. It is a trust engine that may, in the future, be offered as a white-label product for other contexts that need to prove operation.

Energy

Prove generation, consumption and availability of a plant in an auditable, continuous way.

Data centers

Record uptime, load and real operation of computing infrastructure.

Production chain

Sign and preserve the steps of a physical process for later audit.

Documents

Anchor the integrity of a record in time, without exposing its content.

White-label applications are strategic vision — they depend on technical, regulatory and feasibility study. They do not constitute an offer or commitment.

Trust is not promised. Trust is recorded.

See how the proof works in practice — and how it underpins every plan in the NW Energy ecosystem.

Compliance and trust

Built under a regulatory framework

These are not decorative badges — they are verifiable commitments that underpin every interaction in the ecosystem.

⚖️

Lei 14.478/2022

Virtual Assets Legal Framework. Utility token under Brazilian law.

🔐

LGPD

Law 13,709/2018. Personal data protected and never recorded on a public blockchain.

🪪

KYC / AML

Mandatory identity verification for allocation. Active anti-money-laundering policy.

Verified contract

Public, auditable source code on BscScan — anyone can check.