EAS · IPFS · Base Mainnet
Verify any
data point independently
Every response from the MineFlowTrack API includes an EAS attestation UID and an IPFS CID. No trust required — verify the source data directly on easscan.org and IPFS.
How provenance works
From field to API in four steps
Field collection
Each run is recorded in the field using the MineFlowTrack PWA. Data is captured against the locked v1 schema: run ID, date, site coordinates (rounded to ±0.1°), feed type, tray geometry, ultrasound parameters, flow rate, feed mass, and recovery rate. Stored in Firebase Firestore.
IPFS pinning via Pinata
The completed run JSON is pinned to IPFS via Pinata. The resulting CID is a content-addressed, permanent identifier for the exact data object. If the data changes, the CID changes — making tampering detectable without a database.
EAS attestation on Base
An EAS attestation is created on Base mainnet, encoding the run data fields and IPFS CID against the registered schema. The resulting UID is a permanent, on-chain record. The attesting wallet is the single source of truth for the operator's identity.
API delivery
When you call /runs via the x402-gated API, each run in the response includes its eas_uid and ipfs_cid. You can verify either independently, any time, without MineFlowTrack's involvement.
EAS Schemas on Base mainnet
Two registered schemas
Both schemas are registered on Base mainnet in the EAS Schema Registry. The UIDs are permanent — the schema definition is locked and publicly viewable on EASScan.
Benchmark schema
Used for USGS commodity summaries (gold, silver, copper).
Schema name: mineral-intel-benchmark-v1
0xde9e029944dd16f3dad09458ec50b1823e4fbeaa35e6779509aeb84059bb8531
Run log schema
Used for each field season run log attestation.
Schema name: mineral-intel-ultrasound-run-v1
0x7fe15e2b15e89e5e16348683b62c90c9139fdbf1b24d424d7931b4572334d73d
Independent verification
Three ways to verify
Verify on EASScan
Take the eas_uid from any run log response. Go to easscan.org (Base network), search the UID. The full attestation — schema, data fields, attester wallet, timestamp — is on-chain.
Verify on IPFS
Take the ipfs_cid from any response. Fetch it via any IPFS gateway: https://ipfs.io/ipfs/<cid>. The returned JSON should match the data in the API response exactly — content-addressed, immutable.
Query EAS directly
Use the EAS SDK or GraphQL API to query all attestations against the run log schema UID on Base mainnet. You can reconstruct the full run log history without using the MineFlowTrack API at all.
Infrastructure
What runs where
| Component | Service | Details |
|---|---|---|
| On-chain attestations | Ethereum Attestation Service | Base mainnet. Two registered schemas (v1, locked). |
| IPFS pinning | Pinata | Each run JSON pinned before attestation. CID committed to EAS record. |
| Payment protocol | x402 + CDP Facilitator | $0.10 USDC per call on Base mainnet. EIP-3009 authorization. |
| API server | Google Cloud Functions (Gen 1) | us-central1, nodejs20, Express. Deployed as api function. |
| Static site | Firebase Hosting | CDN-hosted. Project: fourmonth-73efe. |
| Field data capture | Firebase Firestore + Hosting (PWA) | mineflowtrack PWA — offline-capable field data entry. Exports v1 bundles. |