You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+12Lines changed: 12 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -25,6 +25,16 @@
25
25
26
26
---
27
27
28
+
## What is siqlah?
29
+
30
+
siqlah is a **Go + Rust server and CLI toolkit** that creates tamper-evident, cryptographically signed audit receipts for AI API usage. It is a **software transparency and accountability tool** — not a cryptocurrency project, blockchain application, or financial product.
31
+
32
+
It uses standard **Ed25519 digital signatures** (the same algorithm used by SSH, TLS, and Git) to sign usage receipts, and builds an **append-only Merkle log** (the same data structure used by Certificate Transparency) so that any party can independently verify token counts without trusting the provider or the operator.
33
+
34
+
The word "private key" appears throughout the codebase and documentation in its standard cryptographic sense: an Ed25519 signing key for receipts and checkpoints, identical in nature to an SSH host key or a TLS client certificate key. It has no connection to cryptocurrency wallets, seed phrases, or blockchain accounts.
35
+
36
+
---
37
+
28
38
## The Problem
29
39
30
40
Every major AI provider — OpenAI, Anthropic, Google — prints a token count in their API response. That number directly determines your invoice. Yet **no independent party verifies it**. You trust a JSON field.
@@ -211,6 +221,8 @@ siqlah supports two signing backends, selectable with `--signing-backend`:
> **Note on terminology:** The "private key" used here is an **Ed25519 digital signature key** for signing usage receipts and Merkle checkpoints — a standard cryptographic primitive equivalent to an SSH or TLS signing key. It has no relation to cryptocurrency wallet keys, seed phrases, or blockchain accounts.
225
+
214
226
Fulcio-signed receipts include a `certificate_pem` field and optionally a `rekor_log_index` for the Rekor transparency log entry.
0 commit comments