VSE ANTI-FRAUD
WHITELIST PROTOCOL

VSE accepts only energy data originating from an identifiable physical energy asset and retrieved through an approved machine-authoritative source.

Approved sources include solar inverters, certified smart meters, approved hardware telemetry systems, official manufacturer infrastructure, and authenticated manufacturer cloud or OpenAPI connections representing data generated by the underlying hardware.

The following are not accepted as primary production evidence: manually entered values, user spreadsheets, user-generated CSV files, screenshots, human declarations, partner-generated production totals, manually edited payloads, or unverifiable third-party substitutes.

Every accepted source must have a stable technical identity. Depending on the manufacturer and hardware type, VSE may validate plant ID, inverter ID, logger ID, meter ID, serial number, organization ID, authenticated API account, source connection state and manufacturer response metadata.

A production interval received from one registered source cannot be silently attributed to another source.

VSE never creates an energy proof first and searches for evidence later. The original manufacturer response is captured before verification and preserved according to VSE evidence-retention rules.

No verified unit may exist without corresponding source evidence.

VSE independently fingerprints accepted source payloads. It does not trust a hash supplied by the provider. Where signatures, authenticated requests, HMAC validation or equivalent integrity mechanisms exist, they are independently verified.

The system checks consistency between source evidence, identifiers, timestamps, production intervals, calculated energy, audit hashes, previous audit state and the resulting VSE Unit.

VSE does not accept a partner's claimed energy total as proof. Energy values are calculated according to the active VSE methodology from authenticated source data for the verified interval.

The same valid source evidence processed under the same methodology must produce the same result. No employee, partner, buyer, administrator or auditor can manually change the calculation.

Time is part of the evidence. VSE validates source timestamps, collection timestamps, interval boundaries, ordering, duplicate intervals, missing samples, excessive gaps, future timestamps, invalid clock sequences and already processed intervals.

A production interval cannot be used twice.

One valid source interval may produce only one corresponding verified VSE energy state. Duplicate protection applies across evidence hash, source identity, production interval, audit identifier, VSE Unit identifier and blockchain state where applicable.

The same energy cannot be accepted again through another request, account, API key, organization or commercial transaction.

VSE proofs are not created by human approval. There is no administrator override capable of bypassing cryptographic validation, no commercial exception, no buyer privilege and no partner privilege.

Human review may exist outside this chain for compliance, investigation, support, security or enterprise assurance. It cannot alter raw evidence, rewrite accepted audit state or approve mathematically invalid proof.

Every verified VSE event is linked to an audit history. Accepted evidence is not silently rewritten. Historical verification state is not edited because someone later prefers a different result.

Corrections, exclusions, investigations and security actions create new auditable events. They do not erase history.

Once an interval has entered the verified VSE state, the underlying evidence cannot be replaced with a more convenient version. Attempts to alter evidence, timestamps, device identity, processed intervals, source attribution or cryptographic state are protocol violations.

A source has no inherent right to remain connected. Participation exists only while protocol requirements continue to be satisfied.

The system may suspend or reject a source on authentication failure, revoked manufacturer access, invalid identity, repeated duplicate submissions, impossible timestamps, cryptographic mismatch, manipulated payloads, inconsistent telemetry, prohibited source substitution or confirmed fraud indicators.

Administrative access does not create production authority. Administrators may manage users, organizations, configuration, system health, reviews, contracts, billing and access policies.

They may not fabricate verified production, manually mint unsupported energy, convert failed evidence into passed evidence or rewrite immutable audit history.

Money does not change the protocol. A larger customer receives no weaker validation. A strategic partner receives no hidden exception. A major corporation cannot purchase an override.

Commercial agreements may define price, volume, SLA, access rights, support, reporting and contractual obligations. They do not alter mathematical validity.

Once a VSE Unit is validly retired, it cannot return to available inventory, be sold again, be retired twice, or re-enter another active claim.

The resulting proof may reference the VSE Unit, energy amount, production interval, source evidence hash, audit hash, beneficiary, purpose, sale, mint transaction, retirement transaction, methodology, network and smart contract.

The final objective is not a human-readable certificate alone. A VSE proof is designed to be independently machine-verifiable.

A proof may include public VSE Unit ID, production interval, verified quantity, source fingerprint, audit fingerprint, previous audit state, blockchain references, beneficiary hash, purpose hash, sale hash, methodology hash, proof signature and protocol version.

When VSE cannot verify something, it does not pretend that it can. Unconfigured services remain unconfigured. Unavailable data remains unavailable. Pending evidence remains pending. Failed verification remains failed.

VSE must never fabricate live production, blockchain transactions, manufacturer confirmations, audit results, customer activity or energy inventory.