xMeter: Smart Meter Data Privacy

The Problem

Smart meters collect 15-minute interval consumption data that reveals household occupancy patterns, appliance usage, and daily routines — a detailed profile of private life.

AMI 2.0 smart meters report granular energy consumption to utilities. Research has shown that this data can reveal when residents are home, what they’re doing, and even what they’re watching on TV.

Utilities need aggregate consumption data for grid management and demand response, but they don’t need individual household data to achieve this. Current systems collect everything.

The Old Way

The PRIVATE.ME Solution

xMeter enables utilities to compute grid-level analytics on XorIDA shares via xCompute. Aggregate demand, load forecasting, and outage detection work without accessing individual meter data.

Each smart meter XorIDA-splits its readings across independent aggregation nodes. Grid analytics (total demand, peak detection, outage identification) run on shares via xCompute’s Boolean circuit engine.

Individual meter data is reconstructable only with the homeowner’s authorization via xLock push-auth. Utilities see aggregate grid health — never individual consumption patterns.

The New Way

How It Works

xMeter combines xCompute aggregation with XorIDA split metering and xLock homeowner authorization for privacy-preserving AMI.

Use Cases

Integration

import { MeterPrivacy } from '@private.me/metersplit';

const meter = await MeterPrivacy.create({
  meterDid: meterDid,
  aggregators: [aggA, aggB, aggC],
  threshold: { k: 2, n: 3 }
});
await meter.reportReading(consumption);

Security Properties

Multi-Party Billing Authorization

Critical billing operations require K-of-N threshold approval to prevent unauthorized charges and meet regulatory requirements. The system integrates with the authorize package to enforce multi-party controls on billing workflows.

Billing approval workflows support three authorization patterns:

• 2-of-2 approval — Billing manager + finance controller must both approve charges before processing
• 2-of-3 approval — Any two of billing manager, finance controller, or compliance officer can authorize
• 3-of-5 approval — Enterprise deployments requiring broader authorization across departments

This architecture addresses regulatory requirements including NERC CIP strict access authorization processes for critical infrastructure, and FERC Order 2222 attestation requirements for distributed energy resource aggregators. All approval actions generate cryptographic audit trails via xProve.

Verifiable Data Protection

Every operation in this ACI produces a verifiable audit trail via xProve. HMAC-chained integrity proofs let auditors confirm that data was split, stored, and reconstructed correctly — without accessing the data itself.

Ready to deploy xMeter?

Talk to Ren, our AI sales engineer, or book a live demo with our team.

Ship Proofs, Not Source

xMeter generates cryptographic proofs of correct execution without exposing proprietary algorithms. Verify integrity using zero-knowledge proofs — no source code required.

Use Cases