VSEPROTOCOL
SIGN IN DEMO ACCESS
VSE // STANDARD

Evidence rules before
commercial claims.

The VSE methodology defines how source data becomes a verified unit, how duplicate claims are prevented and what a public proof must contain.

VSE-STP / SOURCE TRUST PROTOCOL

Required source controls

  • Official manufacturer cloud response
  • Complete plant and device identifiers
  • UTC-normalized finalized time interval
  • Stored raw response before processing
  • SHA-256 evidence fingerprint
  • Documented energy calculation method
VSE-AUDIT / CHAINED EVENTS

Required audit controls

  • Canonical JSON event payload
  • Previous event hash
  • Unique event hash
  • Unit and business references
  • Immutable timestamps
  • Administrative action log
VSE-UNIT / REGISTRY INVARIANTS

Required contract controls

  • Authorized minter and retirer only
  • Unique audit hash
  • Unique source hash
  • Unique source interval
  • One-time retirement
  • No transfer, approval or reactivation
VSE-PROOF / FINAL ENVELOPE

Required proof fields

  • Production interval and energy
  • Source and audit hashes
  • Mint and retirement transactions
  • Beneficiary, purpose and sale hashes
  • Methodology and contract identifiers
  • Ed25519 signature when configured
VSE commercial scope: VSE verified units are independent private, machine-verifiable energy proof sold by direct contract. The VSE source controls, audit chain and retirement proof are the product. No third-party audit is required by VSE itself; any extra buyer review is contractual. VSE does not claim to be an official Guarantee of Origin, EECS certificate, carbon credit, transferable token or automatic Scope 2 evidence.