Partner verifier

Proprietary Technologies × No AI Training

Verify what we say. With your own keys.

The router at https://router.epochcoreqcs.com/ publishes signed sync ticks and proof bundles for self-powered biological monitoring nodes deployed in controlled-environment agriculture. The BioSwarm Attestor is a stateless Python sidecar that re-fetches live data, re-computes KPIs from raw node readings, walks the signature chain, and produces its own Ed25519 + ML-DSA-65 attestation envelope you can archive or forward. It does not require write access. It does not need our private keys. It produces verifiable environmental data on its own.

Three commands.

After cloning the router repo and installing dependencies. Replace bioechem and field-a with whatever tenant and zone you're auditing.

# Required + optional dependencies
cd epochcore-quantum-router/dispatcher
pip install cryptography           # required
pip install httpx oqs              # optional: faster HTTP, real ML-DSA-65

python3 bioswarm_attestor_cli.py run-once \
    --tenant  bioechem \
    --zone    field-a \
    --out-dir ./attestations

python3 bioswarm_pq_signer.py verify \
    --cosigned-file attestations/cosigned-*.json \
    --key-file      attestations/pq_keypair.json

python3 bioswarm_audit_bundle.py bundle \
    --tenant bioechem --zone field-a \
    --inputs attestations/ \
    --out    bundle.json

python3 bioswarm_audit_bundle.py prove \
    --bundle-file bundle.json \
    --inputs      attestations/ \
    --index       0 \
    --out         proof.json

python3 bioswarm_audit_bundle.py verify --proof-file proof.json
# {"ok": true, "merkle_root": "..."}

Worked example: Flood Sentinel.

A real trace from the working prototype. ALS-PT19 light sensor on A0 of an Arduino UNO R4 — when standing water bridges the sensor pad the photodiode signal jumps. Threshold: alarm fires above 0.6 V sustained for two consecutive samples.

Total elapsed from physical water → operator phone alert: under 20 minutes against a < 1 cm water depth. The proof bundle from this exact trace is what the three commands above verify — without giving the verifying party any tenant secrets, the chain of signatures and the consistency between router KPIs and raw readings can be re-derived on their own infrastructure.

What the attestor checks.

The attestor surfaces the gap between what the router reports and what the raw per-node readings imply. The KPI block in every envelope contains a kpi_match map with four entries:

Verdicts emitted per cycle:

A mismatch verdict fires whenever the router's claimed counts diverge from the recomputation. stale means the snapshot timestamp is older than five minutes — the recomputation is still delivered. no_data means the snapshot returned no nodes (useful for zone-empty vs zone-broken). The chain check walks prev_signature links in the sync-tick history and confirms timestamps move monotonically forward. Any break or reordering is flagged in the envelope's chain block.

Module map.

Five focused Python modules plus a CLI. Every module is fully unit-tested.