Skip to main content
Explorer preview · example record

Trace the evidence, not the private data.

The planned Explorer will connect a PoCiSys receipt to its verification results and public Kaspa anchor while keeping prompts, responses, model weights, and proprietary evidence off-chain.

Illustrative preview only. The record below is fictional. Search, indexed audit data, public APIs, and Kaspa broadcasting are not live on this page.
Search coming later

Fictional example audit

demo-000042

Local checks passedKaspa not broadcast

Canonical event

schema_version
poci.receipt/0.1-demo
assurance_profile
observer_attested
event_type
runtime_integrity_observation
event_id
demo-000042
prev_event_id
demo-000041
observer_id
sha256:7d21…04be
runtime_class
Ollama-compatible local runtime
private content
Not collected; commitments only

Proof object

{
  "model_id": "sha256:8f34…b91c",
  "commit_hash": "9c4e18b2…7a31",
  "lineage_hash": "cb8dc069…fe44",
  "prev_commit_hash": "4a106f73…20d8",
  "signature": "MEYCIQDf…demo"
}
✓Canonical event bytes reproduce the displayed commitment hash.
✓The illustrative observer signature validates against its enrolled public key.
✓The previous commitment links continuously to this lineage hash.
○No transaction exists. Anchor acceptance, confirmation, and reorganization checks remain pending.
What this assurance level means: an observer_attested receipt can show that an enrolled PoCiSys observer signed a tamper-evident record. It does not prove that a neural network executed correctly or that every computation was recorded.

What can be public—and what stays private

Public verification surface

  • Receipt and schema identifiers
  • Assurance profile and signer identity
  • Commitment and lineage hashes
  • Kaspa transaction, acceptance, and confirmation status once live
  • Machine-readable verification outcome

Off-chain or never collected

  • Prompts, responses, embeddings, and private reasoning
  • Raw model paths, credentials, and private keys
  • Proprietary configuration and customer data
  • Full evidence bundles unless intentionally shared with an auditor
  • Anything outside the declared evidence policy

Planned verification path

01 · RECORD

Canonical event

A versioned, minimized event states exactly what the signer is claiming.

02 · PROVE

Hash, sign, and link

The event becomes a signed commitment connected to its previous receipt.

03 · ANCHOR

Kaspa acceptance

A batched commitment is submitted and tracked through acceptance and confirmation.

04 · VERIFY

Independent result

The Explorer displays each check without exposing the private event payload.

Read the current research