The sensor signs its own measurement.
Every measurement is hashed at the sensor, then anchored on Hedera HCS. A spoofer cannot fabricate false data without holding the physical sensor — and its key. This is the difference between declaring data and proving data.
The anti-spoofing chain
Proof pipeline: the sensor measures at the source, the measurement is hashed with SHA-256, the fingerprint is anchored on Hedera HCS, then publicly verified via the Mirror Node.
Technical evidence element · non-qualified. The hash is public; the raw data stays with the producer — 0DATA does not read it.
Declared or proven?
The server receives a value it cannot authenticate. Anyone can inject a false measurement — faked GPS, fictitious sensor, fabricated calculation. The network pays for nothing.
The measurement is hashed inside the sensor, then anchored on Hedera. Verifiable by any third party with a single Mirror Node call. Impossible to falsify without the physical hardware.
Frequently asked questions — DePIN anti-spoofing
How do you prevent spoofing in a DePIN network?
By signing the measurement at the source: the sensor computes the SHA-256 fingerprint of the reading itself, then anchors it on a public ledger (Hedera HCS). Without the physical sensor — and its key — no one can produce a valid fingerprint. The network verifies every data point instead of taking it on faith.
How do you prove an IoT measurement is real?
The measurement is hashed inside the sensor at acquisition time, not on a remote server. The fingerprint is then anchored on-chain. Any third party can recompute the hash and verify the anchoring via the Mirror Node: the data exists, timestamped and intact, regardless of who declares it.
How much does a proof of anchoring cost?
2 MAD per anchored seal. It is a pay-per-use toll, with no mandatory subscription: you pay for each proven measurement, not for a license. Larger integrations (sensors, volume) are quoted on request depending on your fleet and cadence.
How do you verify a proof on Hedera?
Each anchoring returns a public hash, a sequence number and the Hedera topic ID. You verify them with a single Mirror Node call or on Hashscan: the hash can be recomputed from the raw data, proving it was not altered after acquisition.
What is the difference between declared and proven data?
Declared data is a value received by a server, which it cannot authenticate: a spoofer injects a false reading (faked GPS, fictitious sensor) and the network pays. Proven data is signed at the sensor then anchored: it can only be falsified by holding the hardware.
Can a sensor-signed measurement be falsified?
Not without the physical sensor and its private key. The key lives in the sensor's secure element; the measurement is hashed before leaving the device. An attacker can neither replay an old value (timestamping) nor forge a valid fingerprint without the key.
Integrate proof into your network
A "measurement → hash → anchoring" chain ready to plug into a DePIN protocol (WeatherXM, PlanetWatch, Helium…).
Request a demoCompare with other DePIN networks (WeatherXM, Helium, DIMO, PlanetWatch) →
Technical evidence element · Hedera HCS timestamping. Data measured at the source, not declared. This does not constitute legal advice.