1. Abstract of Collection
Energy records can contain or be linked to identifiable information. The proposed framework distinguishes source measurements, verifier records, and ledger references. These are technical data, not an automatic guarantee of anonymity.
- Website operation is distinct from measurement sequences.
- Application access is distinct from measurement batch IDs.
- Participant identity is distinct from energy record identifiers.
Cryptographic hashes and signatures do not by themselves establish privacy compliance. Actual processing, access, retention, and user rights must be assessed for each service.
2. Data Emissions and Persistence
Storage Layer
A proposed source integration supplies StorageProofs with measurement references and device evidence. Such records can be linkable to a participant or location even when raw measurements are not published.
Consensus Layer
Verifier services assess evidence and produce votes. A certificate can include signer references that identify participating verifiers. Their membership and access require explicit controls.
Ledger Layer (XRPL)
A proposed ledger reference can expose:
- transaction and account metadata,
- record identifiers,
- evidence digests.
Validated public-ledger records are independently observable and cannot be treated as private storage. Sensitive source evidence should not be placed in public transaction fields.
3. Application Data Boundaries
Enerdex development materials describe data minimization goals:
seen[ES]-> identifies repeated records; it does not guarantee anonymity.policy_hash-> references a policy version; it is not encryption.RecordLock-> marks an application record; it does not conceal participants.
The design calls for separate access controls for source evidence, participant information, and public references. Each integration requires a documented data-processing assessment.
4. Telemetry & Analytics
Illustrative Enerdex views can display:
- Validator latency distributions,
- QC build times,
- Submission status examples.
The main-site energy-flow values are synthetic examples. They are not evidence that production telemetry is collected or that every connected application follows the same processing model.
5. Third-Party Exposure
Data made public or sent to external services can be processed by:
- XRPL Ledger Nodes (operators of public ledger infrastructure),
- Connected Applications (services with their own access and processing boundaries),
- Infrastructure Providers (where used to deliver a service).
Public account and record references can be correlated with other information. Technical pseudonyms are not a guarantee of anonymity.
6. User Control & Retention
A public-ledger record is different from data held by an application. Validated transactions form a persistent public history. Off-ledger retention and requests must be handled according to actual processing and applicable requirements.
7. Interpretive Clause
This framework description does not establish that all data is anonymous or unidentifiable. Terms such as nonce continuity, signer references, or record checks describe technical mechanisms, not a complete privacy guarantee.