Verification & Trust Chain
Every gallon you save,cryptographically signed.
When a GSA auditor, a corporate water-credit buyer, or your bank asks "prove it," a screenshot of a dashboard isn’t enough. Our trust chain produces a tamper-evident, independently-checkable signed record of each water-use figure. Anyone with the public key can confirm the record hasn’t changed since it was issued, without trusting our server. The signature proves provenance and integrity; the meter, baseline, and methodology are still what a buyer or auditor evaluates.
Sensor reads ingested
Sentek soil-moisture probes write 15-minute readings to IrriMAX. Watermatics flow meters write pump runtime + cumulative volume to FDS. Both feeds land in AgWaterAI’s ingest pipeline with timestamp + source-of-truth metadata.
AI models compute claims
Six production models (PULSE / SENTRY / SENTRY-TRANSITION / WATCHDOG / SALT FLUSH / PRESCRIBE) transform raw sensor data into farmer-facing decisions and water-use claims (allocation usage, stress alerts, salt zone trend, irrigation prescriptions).
Cryptographic signing
Every entity certificate is signed with our Ed25519 private key (RFC 8032). The public key sits at /.well-known/agwaterai-signer.pub.jwk. Anyone can verify a cert without trusting our server.
What ships today vs the patent-pending roadmap
Live today
Ed25519 signed certs (RFC 8032)
- · Every entity cert signed with our private key
- · Public key at
/.well-known/agwaterai-signer.pub.jwk - · Per-site mini-hashes anchor under each entity cert
- · Anyone can verify without our server: fetch the JWK, run
compactVerify - · Visible on every customer dashboard Verification tab
Patent-pending roadmap
Patent-pending verification roadmap
- · Hybrid signature options after counsel review
- · Patent-pending chain structure licensed for AgWaterAI agriculture workflows
- · Selective-disclosure layer for grower-controlled privacy
- · Merkle anchoring across daily site snapshots
- · Built for buyer-grade audit trails
- · Gated on counsel review before public rollout
Same dashboard surface today and tomorrow. Swapping the signature primitive from today's Ed25519 signing to future hybrid signing keeps the UI, the verifier, and the workflow familiar. The patent-pending advances are invisible to growers, visible to auditors, and load-bearing for buyer + insurer counterparties down the road.
From soil sensor to verified output.
Sensor → aggregation → verification chain → Merkle attestation → verified output
Don’t trust us. Verify it yourself.
One click fetches a live signed record of our aggregate production stats, pulls the public key, and checks the Ed25519 signature right here in your browser. Our server plays no part in the check and never sees the result.
What you verify contains no private data: the signed record holds six company-level aggregate figures (total sensor readings, active site count, site-years, years of continuous data, and models in production) and nothing else. No farm names, no locations, no field-level readings, no customer information. The record even declares its own scope: aggregate-only; no per-customer data.
Verification happens in your browser with the public key. We never see the result.
Why this earns a buyer premium
Most ag-tech dashboards display numbers. Anyone could screenshot them. The trust chain turns those numbers into a verifiable artifact any counterparty can confirm with our public key.
That matters when the next buyer is a corporate water-replenishment program, a Verra VM0042 verifier, or a Gold Standard WBS registry. Those buyers want more than “the vendor says so”: a tamper-evident, independently-checkable record lowers audit friction and dispute risk. We are testing this workflow with corporate water buyers; pricing and registry acceptance are still subject to buyer diligence and methodology review.
Verify a cert yourself.
Fetch the public key, parse the JWS, verify the signature. No AgWaterAI API call required.
import { compactVerify, importJWK } from 'jose';
const jwk = await fetch('https://agwaterai.com/.well-known/agwaterai-signer.pub.jwk')
.then(r => r.json());
const publicKey = await importJWK(jwk, 'EdDSA');
const { payload, protectedHeader } = await compactVerify(jws, publicKey);
console.log('verified', JSON.parse(new TextDecoder().decode(payload)));jws is the compact-form signature shown in the Verification tab of any customer dashboard. The decoded payload includes entity id, acres, allocation AF, used AF, water year, and the issuance timestamp.
Why this matters beyond the dashboard
If water-credit markets develop, documented water savings can become a tradeable asset.
A signed water-use certificate is the difference between “our vendor says we saved water” and “here is the cryptographically attested record any buyer can confirm has not been altered since signing.” That distinction unlocks corporate water-replenishment programs, voluntary water credits, and ESG-grade water accounting. The trust chain above is what makes it possible.