Verified Compute Cloud

The protocol
that turns a claim
into a transferable proof

Energy Web Verified Compute Cloud (VCC) is a decentralised compute and verification service that extends and enhances the Energy Web Digital Spine credential-governed data exchange orchestration, Energy Web Green Proofs registry operation and other services. A network of VCC operators execute independent, parallel computational checks, producing consensus-based and blockchain-anchored verifiable and tamper-evident results.

One protocol, many markets

Any verifiable claim. Any market.

Electricity
Prove that a kilowatt-hour of renewables matched a kilowatt-hour of consumption, hour by hour, locationally.
Renewable fuels
Various on-chain checks per retirement.
Carbon markets
Continuous project-level MRV instead of annual sampling.
Scope 3 / supply chain
Factory-level emissions proofs that travel with the shipment.
Product passports
Every material claim backed by a verifiable receipt.
AI compute provenance
Attest that a specific model ran a specific computation on specific inputs.
The protocol, step by step

One claim, four stages

Watch a single verification move from private data to a public, transferable proof.

Stage 01 · Encrypt & submit

The claimant encrypts inputs and submits

A company that needs a proof, say a carbon footprint, encrypts the inputs its chosen methodology asks for and submits them for verification. The raw data stays inside the claimant's environment. Only encrypted inputs and a cryptographic fingerprint cross the boundary.

actor
Claimant
private
Raw operational data
sent
Encrypted inputs + hash
PRIVATE VCC NETWORK CLAIMANT · ENVIRONMENT Company · scope 2 inputs 24/24 encrypted · raw data never leaves METHODOLOGY ghg-scope2-v1.4 signed · published awaiting inputs
Stage 02 · Run against the rule

A signed methodology defines the math

A versioned, signed methodology defines exactly what is calculated. Published once, upgraded transparently. Every operator on the network runs the same business logic against the same encrypted inputs. Same answer, every time.

actor
Methodology Builder
rule
ghg-scope2-v1.4 · signed
replays
Deterministic, every operator
SIGNED METHODOLOGY · ON-CHAIN method ghg-scope2-v1.4 author GHG Protocol WG input electricity_mwh, factor_kgco2 rule emissions = mwh × factor output kgco2_total · uint64 signed 0x9b3f…a210 · v1.4 OPERATORS RUNNING THIS METHODOLOGY OP-01 OP-02 OP-03 OP-04 OP-05 OP-06
Stage 03 · Run in parallel, find consensus

Independent operators agree on the answer

Independent compute providers run the methodology in parallel and submit their results to the chain. Consensus settles the answer. Anyone who returns a different number loses stake. The math gets a quorum, not a single point of trust.

actor
VCC Operators
quorum
5 of 6 agree · 1 slashed
settled
On-chain · seconds
CONSENSUS 5/6 agree OP-01 a3f9 OP-02 a3f9 OP-03 a3f9 OP-04 b7c1 OP-05 a3f9 OP-06 a3f9 agreed dissent · stake slashed
Stage 04 · Attest, publish, transfer

A public proof anyone can verify

The signed result is published on-chain as a transferable proof. Accredited auditors can inspect it under scoped access and sign their own attestation on top. The proof then travels downstream with the claim, to buyers, regulators, and the public.

actor
Auditors & Public
proof
company-ghg-84a3f9c2b1
who reads
Buyers · Regulators · Public
VCC EXPLORER · BEARER RECEIPT claim safc-2026-08a3f9c2b1 consensus a3f9…c2b1 · 5 of 6 attestation signed · VMI #001 private request via Launchpad block #18,422,931 · 0x9c41…7d2a AUDITOR Certified · ✓ TRANSFERS DOWNSTREAM Buyer Regulator Public
01 / 04
Five roles, one protocol

Who does what

Every verification involves five kinds of participant. Four of them produce the proof. The fifth is the reason it exists, the consumer at the end who needs to trust the claim without running anything themselves.

Prove a claim
Claimant
An enterprise, a registry, a fuel producer, SaaS platform, anyone making a claim that someone downstream needs to trust.
What they do
  • Picks a methodology
  • Encrypts and submits inputs
  • Owns access to raw data
Public proof, travels with claim
Author of the rule
Methodology Builder
A standards body, a sustainability team, or a developer who writes how a calculation must be done.
What they do
  • Writes calculation logic
  • Versions and signs the rule
  • Publishes on-chain
Signed, versioned methodology
Provide compute & stake
VCC Operator
An independent compute provider that subscribes to the network, stakes EWT, and runs methodologies for fees.
What they do
  • Stakes EWT
  • Runs methodology on inputs
  • Posts result for consensus
Service fee · slashed if wrong
Provide assurance
Auditor
An accredited verification firm that inspects receipts and signs an attestation on top of the network consensus.
What they do
  • Requests scoped access
  • Inspects record
  • Signs attestation on receipt
Counter-signed public proof
Rely on the proof
Proof Consumer
A buyer, regulator, NGO, journalist, or downstream counterparty who receives a claim.
What they do
  • Look up receipt ID in the explorer
  • Verify methodology, operator quorum, and timestamp
  • Check auditor counter-signature
Instant verification, no audit relationship required
What changes

The next generation
of verification

What a VCC proof gives you that an annual audit report doesn't.

Benefit 01
Continuous
Every submission, every time. Not an annual review window, verification runs whenever data lands.
Benefit 02
Complete
Every record is checked, not a sample. The proof covers the whole population of claims, not a sub-sample.
Benefit 03
Transferable
The proof travels with the claim. A buyer, a regulator, a partner can verify it without re-running the audit.
Benefit 04
Private by design
The data stays with the claimant. Only the calculation and its result become public; the inputs do not.
Built on the protocol

One in production, more being built

Energy Web Verified Compute Cloud is not a single product. It's the substrate that any registry, standards body, or enterprise can build their own verifier on. Here's what's live and what's coming.

Pilots in development

In flight across CBAM, CSRD & SAF compliance

Verified Compute Cloud is being piloted with registries, market operators, and assurance providers, each shaped around a specific regulatory framework. These programs sit on the protocol itself, not on any single registry.

Corporate disclosure · Pilot

Real-time ESG verification

Digital control environments and continuous data validation that reduce the cost of preparing and auditing sustainability data for CSRD reporting, working across the data supply chain.

Trade · Pilot

Green import verification (CBAM)

Continuously verified evidence packs that document an importer's lower-carbon inputs, packaged consistently for carbon border scheme verifiers and delivered on demand.

Aviation · Pilot

Verified SAF compliance

Machine-verifiable evidence bundles that document an operator's sustainable aviation fuel use and compliance position, packaged consistently for accredited aviation verifiers.

Many roles, one conversation

Whichever role you play, we want to hear from you

Bring us a claim, a methodology, a verification group, or just a question. We're early and working closely with the first builders on each role.

Get in touch →

This content is for informational purposes only and does not constitute investment, legal, or tax advice, nor an offer to buy or sell any financial instrument. Energy Web Token (EWT) is used to help secure the Energy Web Chain and, when restaked, to secure specific solutions and verified compute under defined service level agreements (SLAs). Participation in such solutions may require KYC/AML and carries risks, including slashing, technical or operational failures, and jurisdictional restrictions. Any payments referenced relate solely to service fees for verified work, not to financial yield or passive returns.