On-chain proof of development
We don't just claim we built DORA OS. We prove it — cryptographically, on Polygon Mainnet. Two trust anchors, two timestamps, one development timeline that anyone can verify.
Trust anchor #2 — DORA OS full stack
21 Oracles · 317 Tools · 9 Workflows
31 March 2026 · Block 84,921,488
SHA-256 content hash
3334e7bbdedc6401ce66f2a3768c9c4a572a42bd41304d6be36b1ba441a0e753
Chain
Polygon PoS (Mainnet)
Event rules
12 routing rules
Verify on Polygonscan →
Trust anchor #1 — Pre-DORA baseline
One day before DORA enforcement
16 January 2026 · Block 81,721,330
SHA-256 data hash
6f2957bac3a775ea5deed8ee0b068d19d29c0101760b0a556b690cb45c89bbb2
Chain
Polygon PoS (Mainnet)
Context
DORA enforcement: 17 Jan 2026
Contract
0xeDdDFD981A806E0A96A8d1C37d0997F04630DDda
Verify on Polygonscan →
Development timeline (on-chain verified)
16 Jan 2026
Trust Anchor #1 — Pre-DORA baseline anchored on Polygon (Block 81,721,330)
17 Jan 2026
DORA (EU 2022/2554) enters into force across the EU
25 Jan 2026
Dual Polygon + XRPL anchor — compliance evidence infrastructure live
Feb 2026
AmpelOracle, DORAOracle, AMLOracle, LawOracle foundations
Mar 2026
8 new oracles + 3 upgrades built (TestOracle, ReportingOracle, CloudOracle, Conductor, DriftOracle, EventFabric, PredictOracle, ZKEvidenceOracle)
31 Mar 2026
Trust Anchor #2 — Full DORA OS: 21 Oracles, 317 Tools (Block 84,921,488)
How to verify
Each trust anchor is a Polygon transaction where the input data field contains a SHA-256 hash. This hash is the fingerprint of a JSON manifest listing every oracle, tool, workflow, and capability at that point in time.
To verify: open the Polygonscan link, click "Input Data", decode as UTF-8 — the hex string matches the SHA-256 hash shown above. The block timestamp is immutable. The manifest content that produces this hash is published below.
This is not a claim. It's a cryptographic proof that this system existed, with these exact capabilities, at this exact time. Anyone can verify it. No trust required.