Reads the selected account and active network only after the user chooses to connect.
Protocol paper · Version 1.0
Prompt.
Proof.
Portable.
Kernave turns an AI run into a deterministic, inspectable receipt. The first release works locally in the browser and keeps network actions separate, explicit, and optional.
01 · Product
A receipt layer for AI work.
Kernave is not an AI model and does not generate an answer. It packages the context of a completed inference—model identity, revision, prompt, output, seed, notes, and creation time—into a portable receipt that another person can inspect and verify.
01
Capture
Enter the minimum facts needed to describe a run. Required fields are validated before a receipt can be created.
02
Seal
Kernave normalizes the record, serializes it deterministically, and computes a SHA-256 digest in the browser.
03
Verify
Anyone can import the JSON receipt. Kernave recomputes its digest and reports whether the body still matches.
04
Carry
The receipt is a plain, exportable artifact. It does not depend on an account, a hosted database, or a proprietary reader.
02 · Local-first receipt
Verifiable structure, not a truth claim.
The current receipt format is kernave.inference-receipt, version 1.0. Kernave sorts object keys during canonical serialization, preserves array order, normalizes line endings, and hashes the resulting UTF-8 bytes with SHA-256.
A matching digest proves that the exported receipt has not changed since it was sealed. It does not prove that a named model ran, that the prompt was complete, that the output is correct, or that the author owns the underlying content.
Verification sequence
- Check the receipt kind and version.
- Remove the stored digest from the body used for verification.
- Serialize the remaining object with the same deterministic key ordering.
- Compute the SHA-256 digest and compare it with the stored value.
- Return a clear match or mismatch result without rewriting the imported record.
03 · Web3 role
Identity and anchoring stay optional.
The local receipt is useful without a wallet. A wallet can add portable authorship and support future public anchoring, but connecting never signs a message, sends a transaction, activates points, or triggers payment.
The full prompt and output remain off-chain unless the user independently publishes them.
A future signing flow must preview the exact payload and request its own confirmation.
A configured contract may record a digest, never the private receipt body, after an explicit transaction.
04 · Ecosystem contribution
Reusable evidence for an open network.
Kernave contributes a compact receipt schema, deterministic hashing rules, a browser verifier, an example payload, and a minimal anchoring contract interface. Builders can use these assets to add interoperable AI-run provenance without adopting Kernave’s interface.
- A versioned JSON receipt that is readable by people and machines.
- A canonical serialization routine with a reproducible SHA-256 digest.
- An import-and-verify path that works before any wallet connection.
- A digest-only anchoring pattern that avoids publishing prompts and outputs.
- Clear lifecycle states for local, signed, submitted, confirmed, and failed actions.
05 · Access
Three actions. Three decisions.
01
Connect wallet
Establishes an address context only. No points, signature, transaction, or payment occurs.
02
Activate 100 points
A separate, no-payment action records a local participation state. Points have no cash value and do not represent a token.
03
Optional 0.42 BOT
A voluntary upgrade path. The exact recipient, amount, active network, and estimated wallet effects must be shown before confirmation. If verified configuration is absent, payment remains unavailable.
Points, payment, and product use do not guarantee an airdrop, token allocation, financial return, priority access, or future benefit.
06 · Boundaries
Current now. Guarded next.
Available in the current release
- Create, download, import, and cryptographically verify local inference receipts.
- Connect a compatible browser wallet without an automatic signature or transaction.
- Inspect network state and prepare an exportable digest envelope.
- Activate a clearly labeled local points state through a separate action.
Future or configuration-dependent
- Wallet-signed authorship claims and public digest anchoring.
- Contract-backed credentials, revocation references, and cross-app receipt discovery.
- Optional payment, available only when a verified recipient and supported network configuration are present.
- Independent attestations from model providers, auditors, or trusted execution environments.
07 · Risks
Know what the proof cannot do.
- Input authenticity: a user can enter inaccurate model, prompt, or output details before sealing a receipt.
- Content exposure: exported files contain the text entered by the user and should be handled as sensitive material.
- Wallet risk: browser extensions, phishing, malicious approvals, and compromised devices can cause loss.
- Network risk: fees, congestion, reorgs, contract defects, and third-party outages can delay or invalidate an action.
- Immutability: confirmed public records may be permanent even when the associated local file is deleted.
- Version drift: future receipt versions may require migration or additional verification rules.