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:3ca5f8c2f41375be3b5e71212eb55ff42e9c428984e306602036e19381ee2031FORMAT
Ed25519
ISSUED
2026-03-26
PASSPORT KEY
CLOSURE KEY
WITNESS KEY
LIVE CHAIN STATS
TOTAL SUBMITTED EVENTS
1182
LAST SUBMITTED EVENT (UTC)
2026-06-18T05:19:55.920Z
LAST SNAPSHOT
2026-06-18
REKOR LOG INDEX
1857886596
CHAIN STATUS
VERIFIED
RECENT EVENTS
| CHAIN INDEX | ACTION | TIMESTAMP (UTC) | HASH | VERSION |
|---|---|---|---|---|
| 1096 | tool_call | 2026-04-06T02:07:47.642Z | 54884c0f784006f8 | v1 |
| 1095 | tool_call | 2026-04-06T02:07:47.145Z | 52201c7e52194c35 | v1 |
| 1094 | tool_call | 2026-04-06T02:07:45.699Z | 802ce367f300e820 | v1 |
| 1093 | tool_call | 2026-04-06T02:07:45.230Z | 10045bd35f68361b | v1 |
| 1092 | tool_call | 2026-04-06T02:07:45.321Z | 50957094d76137c4 | v1 |
| 1091 | tool_call | 2026-04-06T02:07:45.054Z | 504ac579a69ae146 | v1 |
| 1090 | tool_call | 2026-04-06T02:07:44.731Z | 69c3d7ea7c731847 | v1 |
| 1089 | tool_call | 2026-04-06T02:07:44.686Z | 8d8ebf37e5afd989 | v1 |
| 1088 | tool_call | 2026-04-06T02:07:44.697Z | 98f390bb94c3276b | v1 |
| 1087 | tool_call | 2026-04-06T02:07:44.363Z | 5b91e54f5a5a5e44 | v1 |
VERIFY IT YOURSELF
python3 verify.py rankigi-proof-bundle.jsonRANKIGI 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.