[01]
Executive Summary
VSE Protocol is an enterprise-grade Decentralized Physical Infrastructure Network (DePIN) transforming distributed residential solar energy into verified, institutional-grade Energy Attribute Certificates (EACs).
[02]
System Architecture & Data Flow
Physical Inverter → Aggregator Backend → Oracle Engine → Blockchain State
Ingestion:
Secure API connection (e.g., Solarman/Deye) running daily batched cron jobs at 23:50 local time to prevent timezone/rollover data loss.
Hash Chain:
Every telemetry packet is cryptographically hashed (SHA-256) before on-chain submission, ensuring an immutable audit trail.
Redundancy:
Dual-node oracle setup with automated failover.
Fallback:
In case of API outage, the backend retains a local encrypted queue. Historical endpoints backfill missing data.
[03]
Data Verification & Anti-Spoofing
Trustless verification of off-chain energy production.
Spoofing Prevention:
Cross-referencing reported yield with regional weather APIs and theoretical max capacity of hardware. Outliers are quarantined.
Duplication Handling:
Idempotent processing. Each daily batch generates a unique cryptographic nonce. The smart contract rejects duplicates.
Outage Handling:
Zero-data days result in zero minting. Interpolation is strictly forbidden to maintain 1:1 token-to-kWh integrity.
[04]
Tokenization & Retirement Logic
1 VSE Token = 1 kWh of verified green energy.
No Deflation:
VSE employs a zero-speculation model. Token supply is strictly bound to historical energy production.
Minting:
Tokens are minted in aggregate to the Aggregator's audited Treasury Wallet based on the daily Oracle payload.
Retirement Burn:
Enterprise ESG purchases are sent to a Null Address. Transaction metadata includes the Enterprise Corporate ID and offset period.
[05]
The Aggregator Entity (Legal)
The protocol is operated commercially by VSE Aggregator s.r.o., a registered European corporate entity.
B2B Sales:
Issuing official fiat-based (EUR) invoices to enterprise clients for EAC purchases.
GDPR Compliance:
On-chain data contains zero PII. Wallet mapping and user KYC are stored on secure off-chain servers.
Standards:
Built to align with ISO 14064 (GHG Accounting) and ISO 17029 (Validation and Verification).
[06]
Revenue Distribution
Strict 70/30 Institutional Revenue Share Model.
Accounting:
Internal off-chain ledger tracks each user's proportional energy contribution.
Distribution:
70% of fiat is distributed to hardware owners via SEPA bank transfers ('Data Provision Fees').
Treasury:
30% is retained by the s.r.o. for API overhead, server infrastructure, and EWF audit fees.
[07]
Risk Management
Contingency protocols for systemic resilience.
API Outage:
Buffered in database; retried using historical endpoints up to 72 hours.
Chain Outage:
State is preserved off-chain. Transactions queue until RPCs stabilize.
Inverter Failure:
Hardware risk is borne by the user. 0 kWh = 0 tokens. System remains economically whole.
Regulatory:
s.r.o. structure isolates protocol from MiCA crypto-asset regulations (B2B data brokerage).
[08]
Governance & Access Control
Strict Separation of Duties using OpenZeppelin's AccessControl.
Smart Contract:
MINTER_ROLE is exclusively held by the Backend Oracle address.
Treasury Security:
Corporate Multi-Sig wallet requires 2-of-3 board member approvals.
Future State:
Transition toward a decentralized Foundation model post-enterprise adoption.
[09]
Compliance & ESG Alignment
Built for the next generation of corporate reporting.
EU CSRD:
Corporate Sustainability Reporting Directive compliant data structures.
GHG Protocol:
Token retirements directly offset Scope 2 (purchased electricity) emissions.
EAC Standards:
Mirrors Renewable Energy Guarantees of Origin (REGO/GO) with timestamped proof.