Climate risk you can prove.
ClimateChain BD turns open ECMWF/ERA5 rainfall data for the Surma–Kushiyara basin into a transparent risk index — then commits each assessment to a tamper-evident registry, so a single altered byte becomes visible to anyone.
04
Monitoring stations
Surma–Kushiyara basin
1d · 3d · 7d
Rainfall windows
Strictly past-only
05
Verification states
Including graceful RPC failure
SHA-256
Dataset integrity
Manifested & re-checked
Basin pulse
Surma–Kushiyara aggregate
Connecting to stations…
mean station SRRI
station spread
Severe stations
0 / 4
Registry
Checking…
Mode
Connecting
Research prototype · not an official warning system
Sylhet Division scopeSRRI is an empirical meteorological rainfall-risk indicator calibrated to BMD thresholds — not a validated hydrological flood probability. Machine-readable flood ground truth was unavailable, so no flood labels were fabricated.
Risk intelligence
Station risk assessment
A transparent 24h / 3-day / 7-day rainfall index with weighted contribution attribution.
Station network
Four sentinels on the Surma–Kushiyara
Every card is computed from the same past-only feature pipeline and re-ranked on each scenario change.
Surma–Kushiyara basin
Geospatial station network
Real coordinates, river corridors, and live SRRI color coding. Click a marker to reassess a station.
SRRI legend
Observations
Precipitation record · Sylhet Sadar
No observation records are available for this station yet.
No observation records available.
Try the live scenario or a historical monsoon date.
7-day outlook
Forecast rainfall · Sylhet Sadar
Numerical weather prediction is kept explicitly separate from observed risk and is never registered as historical provenance.
Trust layer
Blockchain provenance & tamper evidence
Canonical JSON → domain-separated SHA-256 → EVM-ready commitment. Change one byte and the verdict flips.
01Canonicalize
Sorted keys · normalized floats
02Hash
Domain-separated SHA-256
03Commit
bytes32 commitment
04Verify
Recompute & compare every byte
Report commitment
Deterministic identifiers for station · —
Derived at registration
Not registered in this session
Computed at registration
Model version
—
Canonical schema
climatechain-provenance-v1
Registry
Local simulator
Contract
Simulated commitment
Integrity console
Register the commitment, then verify the exact payload.
Registration target: labelled local simulator — no transaction or gas is claimed.
Run verification to compare the local canonical hash against the registry.
Registry audit trail
Commitments registered through this API instance (local simulator or RPC).
Why it matters
From open rainfall data to trusted climate action
The same verifiable primitive can support insurance, relief accountability, and long-horizon adaptation planning.
Parametric climate insurance
A rainfall threshold can trigger a payout while the canonical event report remains independently auditable — reducing dispute friction after a disaster.
Relief & grant accountability
Donors and auditors can verify that the rainfall snapshot behind a needs assessment was not quietly rewritten before funds were released.
Civic planning & research
Planners get a transparent, reproducible rainfall-risk baseline for the haor belt, with limitations and data lineage exposed instead of hidden.
Built to be judged — and re-run
Surma–Kushiyara flash-flood corridor
Station-level risk for Sylhet Sadar, Sunamganj, Kanaighat and Zakiganj.
Real ECMWF / ERA5 rainfall
Open-Meteo ingestion with committed SHA-256 manifests and integrity re-checks.
Verifiable provenance layer
Canonical JSON + domain-separated hashing + EVM commitment + five-state verification.
One-click tamper simulation
Judges can see a report flip from VERIFIED to MISMATCH in seconds.
Designed for non-experts
Plain-language summaries, explicit limitations, and no black-box claims. A journalist, relief coordinator, or judge can follow the evidence chain without reading Solidity.
Scalable next steps
Scientific methodology
Transparent by construction
The data lineage, formula, assumptions, and ethical boundaries behind every SRRI score.
Open, reproducible rainfall data
Committed dataset manifests
Manifest metadata unavailable. The API will surface these when reachable.
Pipeline guarantees
- Chronological sorting + duplicate-date removal
- Range checks: negative and >500 mm flagged
- Trailing 3d/7d windows reference past records only
- Seed ingest writes a sample + SHA-256 manifest; API reads never rewrite it
- Nullable river levels and flood labels — never fabricated
What this is not
null and the limitation is disclosed at the API and UI layers.