Skip to main content

RANKIGI PROOF

RANKIGI Proof

We govern ourselves with the same infrastructure we sell. Our production hash chain is public. Verify it yourself.

PUBLIC KEY

FINGERPRINT

sha256:3ca5f8c2f41375be3b5e71212eb55ff42e9c428984e306602036e19381ee2031

LIVE CHAIN STATS

TOTAL SUBMITTED EVENTS

1249

LAST SUBMITTED EVENT (UTC)

2026-07-10T04:34:38.019Z

LAST SNAPSHOT

2026-07-10

REKOR LOG INDEX

2135710533

CHAIN STATUS

VERIFIED

RECENT EVENTS

Awaiting first sealed event.

VERIFY IT YOURSELF

Download verify.pyDownload RANKIGI proof bundle
python3 verify.py rankigi-proof-bundle.json

RANKIGI is the reference implementation of the KYA open specification. The spec is public. Read the standard.

WHAT RANKIGI DOES NOT CLAIM

  • The chain proves what was reported. RANKIGI cannot prove an agent reported every action it took. That requires agent-runtime cooperation shipping in v5. Pair RANKIGI with your existing observability tool to detect missing telemetry.
  • Data source identity is customer-asserted by default. When a customer registers a source named "Epic EHR", RANKIGI records and chains their submission. Vendor signature verification requires the vendor to participate. We show the attestation tier on every receipt.
  • Chain integrity means tamper-evident, not immutable. Append-only triggers block deletion. If a bad actor gained direct database access before the next Rekor anchor, events in the unanchored window could be rewritten. The top strip shows the current unanchored window age.