A deterministic commitment
The same specified sample material produces the same verification input. A receipt has a reproducible object for the verifier to inspect.
A defined inference receipt check
Give the inference receipt something to stand on.
Lumen verifies provider-signed commitments over sampled inference values, giving supported workflows a specific receipt-verification path.
LumenIllustrated study
Source / fingerprint / attribution
An anchor identifies a record. It does not prove every claim.
01 / Built for a purpose
Start with exactly what can be checked.
An inference result needs a verification claim more precise than “AI verified.” Lumen binds sampled top-k hidden-state material into a deterministic commitment and checks the provider’s signature against the expected receipt context.
Provider attribution
Ed25519 authorship binds the committed material to the provider key. The verifier checks the signature rather than relying on an unsigned result label.
Expected-work binding
Receipt verification uses the expected context. Matching a signature is useful only when it belongs to the work the application intended to accept.
A place in work acceptance
Supported bounty workflows can choose Lumen-attested acceptance when that verification statement is suitable for the task.
The details matterGood questions.
Good questions.
Clear answers.
Does Lumen prove every model operation was performed correctly?
No. Its current scope is sampled commitment and provider-signature verification. Applications must not promote that into a claim of complete execution correctness.
How is it different from a TEE receipt?
Lumen checks specified committed sample material and authorship. TEE verification evaluates a hardware-attestation statement under vendor trust assumptions. They answer different questions.
Keep exploringOne capability.