Demo data. Not a real farm.

Verify a water record

A demo farm with made-up soil readings, sealed and signed the same way a real record is. Every check below runs in your browser, and nothing is sent anywhere.

Why this matters

Pumping reports, water credits, insurance claims and contracts all rest on farm records. Anyone who relies on one should be able to check it, not take it on trust.

Registry entry Demo data. Not a real farm.
Demo Ranch, Block 7 Pistachio · 14 days, Sep 1 to Sep 14, 2026 Not checked yet
Contents
1,008 soil readings at 1, 2 and 3 ft, with each day's checks and model results
Signatures
98. Every step and every day seal is signed.
Scheme
ECDSA P-256 with SHA-256 over canonical JSON (keys sorted)
Public key
SHA-256 …
The check recomputes every fingerprint and tests all 98 signatures against the public key.

The record

14 days, each sealed and linked to the day before

The check recomputes a fingerprint for every reading and every step, then tests each signature against the public key. Each day's seal also names the seal of the day before. Pick a day to see its steps.

This historical synthetic record is kept exactly as signed. The archived sensor-check step is displayed as Synthetic sensor rule. The current product uses WATCHDOG for crop stress and separate rules for sensor checks.

September 2026

Each column is one day: readings, quality checks, the three models and the daily report, then the day seal. Checks out Does not check out Not checked Seal names the day before

Day 5 of 14

How one day is sealed

Each step signs its own result and points to the step before it. Pick a day above to see its steps.

Showing Sat, Sep 5 Irrigated 8 h · 72 readings Not checked

Test the seal

Try to change the record

Change one reading and check again. A careless edit breaks the day's fingerprint. A careful forger can recompute the fingerprints, but cannot make the signatures match without AgWaterAI's private key.

Test 1 · A careless edit

Change the reading and nothing else.

Test 2 · A careful forger

Change the reading, then recompute every fingerprint so they match again.

Test 3 · A missing day

Take the whole day out of the record.

Who checks records like this

Anyone who has to rely on a farm's water records without taking anyone's word for them.

Groundwater agency

Confirm that reported pumping and soil records were not edited after the season.

Water-credit verifier

Trace a claimed figure back to the original readings and every step in between.

Corporate water buyer

Check that the records behind a water project are the originals before relying on them.

Insurer or lender

Confirm the records behind a claim or a loan are the ones captured on the day.

Lawyer

Show when each record was sealed and that nothing in it changed since.

Grower

Show anyone you choose that your records are unchanged, without handing over the rest of your farm data.

What the signature check can and cannot show

It shows
  • The readings have not changed since they were sealed.
  • Which day each reading belongs to, and that no day was removed or reordered.
  • Every step (quality checks, models, daily report) is accounted for and signed by the key holder.
It cannot show
  • That a sensor was installed or calibrated correctly. A field audit does that.
  • Any water-savings figure. That needs a baseline and a stated method.
  • Anything about data that was never collected.

Check it yourself

Download the demo record and the public key and run the same checks with any tool you trust.

  1. For each reading, take the SHA-256 of its JSON with keys sorted. Combine them in pairs into one root fingerprint per day; it must equal the root in the day's sensor step.
  2. For each step, take the SHA-256 of its id, its result and its parents' fingerprints (JSON, keys sorted). It must equal the step's fingerprint, and its ECDSA P-256 signature must check against the public key.
  3. Each day's seal must name that day's report and the previous day's seal, and its signature must check too.
Public key · PEM SHA-256 …