KAI Oracle and KAI-Pay
KAI Oracle provides evidence and Bitcoin network data you can use. KAI-Pay provides the payment path: you check the invoice and approve the payment yourself.
Oracle beta: invitation only. The public wallet can be used independently. KAI Oracle participation and help (German)
What you can use Oracle for
- Evidence of a file version: Submit a locally calculated SHA-256 hash for anchoring through OpenTimestamps without sending the file to Oracle. After Bitcoin confirmation, the timestamp can be verified independently.
- Analyse Bitcoin network data: Retrieve on-chain facts and fee time series from KAI’s own Bitcoin node for your own analysis.
- Share evidence: Retrieve available integrity and anchoring evidence bundles for independent verification.
A timestamp proves that a hash existed no later than a particular time. It does not establish the truth of a file’s contents or a person’s identity or authorship. A submitted anchoring request is not yet a confirmed Bitcoin proof.
How Oracle and the wallet work together
- Arrange beta participation under the Oracle terms (German) and receive an invitation code.
- Request the service you need from Oracle. The service quotes a price in sat and issues an L402 challenge when the service is ready.
- Paste that challenge into “Send” in KAI-Pay and check its origin, amount and fee. Payment requires your approval.
- After paying, copy the access credential and use it with Oracle. The wallet does not fetch the service automatically. Keep any delivered files and proofs yourself.
This workflow currently targets technically experienced beta participants. For the known KAI Oracle node, the wallet currently allows at most 10 sat per L402 payment plus fees. The check shown in the wallet is authoritative. Access and validity depend on the specific Oracle offer; Bitcoin confirmation of a timestamp may follow later.
L402 in the wallet explained · Beta participation and delivery help (German) · Oracle privacy (German)
What is being developed next
Oracle is being expanded with measurable evaluations of the Bitcoin network. An internal fee forecasting pilot has been implemented but is currently disabled and has not completed evaluation; it is not a public product and does not currently provide fee recommendations to the wallet. New forecasts should outperform simple benchmarks before publication.