Species Suite · Onli private market technology

Onli introduces

Witness

A consensus of one.

Private truth. Public proof.
Owner-controlled access.

Witness makes private sources of truth publicly provable — without making them publicly readable.

  • 01 Witness
  • 02 Translate
  • 03 Prove
Scroll

0.1 — The thesis

Publicly provable does not mean publicly readable.

01 · The institution

Imagine a regulated institution that uses an independent compliance firm.

02 · The verifier

The compliance firm needs to verify that something happened. It does not need unrestricted access to the underlying private record.

03 · The principle

Witness separates the two. The fact becomes provable to anyone. The record stays with its owner.

Independence does not imply privileged access.

Oracle record

Stays private.

Proof

Is public.

Access

Belongs to the owner.

Owners control who, when, where, and for how long someone can see proof.

Who
A named recipient, sealed to their key — or an open audience the owner chooses.
When
Disclosure happens only when the owner runs Prove. Nothing is disclosed by default.
Where
Bound to a stated purpose and an optional challenge, so proof cannot be replayed elsewhere.
How long
Every named grant carries an expiry. The owner can revoke future access before then.

0.2 — The model

Private truth. Public proof.

Witness gives a private Oracle record a publicly verifiable proof without publishing the record. Witness itself never learns what the record means.

01

Private truth

Oracle

The underlying record remains private, inside the appliance that produced it.

02

Public proof

Witness

A public proof establishes that the private record exists and has not been altered.

03

External anchoring

OpenTimestamps · Bitcoin

Witness Nodes anchor each checkpoint outside the system — to Bitcoin through OpenTimestamps by default, or through another anchor provider.

04

Human meaning

Translate

Connects a public Witness proof to the meaning held in the appliance's private Oracle — for its owner only.

05

Owner-controlled disclosure

Prove

The owner decides what to prove, to whom, and under what conditions.

The public node gives you the proof.

The appliance Oracle tells you what that proof means.

0.3 — How it works

Witness → Translate → Prove.

One privacy boundary. Above it, everything is public and content-agnostic. Below it, everything belongs to the owner. Only a commitment crosses — unless the owner proves.

Step 01 · Create the public proof

Witness

The Oracle Adapter turns a private record into a commitment and registers it with the Headless Witness. The server appends it to an append-only transparency log and returns a signed receipt.

Independent Witness Nodes follow the log, verify its checkpoints and cosign them. Checkpoints are anchored through a pluggable anchor provider — Bitcoin through OpenTimestamps by default.

  • Crosses boundarycommitment only
  • Public learnsa record exists, unaltered, at a time
  • Public never learnswhat the record says
Witness architecture Public side: Headless Witness transparency log, three Witness Nodes and an anchor provider (OpenTimestamps to Bitcoin by default). Private side: Onli ID, Oracle, the private record and the Oracle Adapter, which sends Witness to the log, Translate to the owner's app and Prove to a recipient. PUBLIC PRIVATE · OWNER OWNER PRIVACY BOUNDARY Headless Witness log · receipts · checkpoints Witness Node Witness Node Witness Node Anchor providerOTS → Bitcoin · default follow · verify · cosign · mirror · serve Onli ID Oracle Private record Oracle Adapter owns Translate + Prove Owner's appweb · mobile · custom Recipiente.g. compliance firm commitment witness_id → meaning sealed claims verify against log
ORACLE RECORD (private)
     │  witness
     ▼
PUBLIC PROOF (commitment in a transparency log)
     │
     ├── no disclosure by default
     │
     └── owner Prove ──► selected claims, independently verifiable

0.4 — Components

A protocol, not an application.

Witness is an Onli protocol with reference implementations. Every piece can be run, replaced or verified independently.

  1. 01

    Witness Protocol

    OWP/3

    Shared contracts, cryptographic construction and verification rules.

  2. 02

    Headless Witness Server

    public

    Public registration, append-only transparency log, receipts, checkpoints and proof retrieval. Content-agnostic.

  3. 03

    Witness Node

    public

    Independently operated node: follow, verify, mirror, cosign, anchor, serve, audit.

  4. 04

    Oracle Adapter

    private

    Appliance-side bridge between Oracle records and public proofs. Owns Translate and Prove.

  5. 05

    Client SDK

    developer

    Reusable developer interface — TypeScript, Rust, Swift, Kotlin.

  6. 06

    Reference front ends

    owner

    Web — a visual relationship surface. Mobile — table-first.

Running a Headless Witness Server or a Witness Node grants no access to private Oracle records.

Witness is not

  • document storage
  • a public transaction database
  • a cloud repository for Oracle records
  • a global index of an owner's activity
  • an authorization authority for Oracle contents
  • dependent on the reference clients
  • a system that writes every event to Bitcoin

0.5 — Witness Nodes

A consensus of one.

No global network of strangers has to agree. You choose who verifies — one node you trust, or a quorum of several. Every operator verifies public history without seeing a private record.

Option 01

Run it yourself.

Operate your own Witness Node beside your appliance. You follow, verify and cosign the log directly.

Option 02

Your auditor runs it.

You don't need to run a node at all. An independent financial audit firm operates it, cosigns what it verified, and still never sees your records.

FOLLOW

Track checkpoints and log growth.

VERIFY

Check signatures, log identity, protocol version and append-only consistency.

MIRROR

Retain enough public history to serve or rebuild verification evidence.

COSIGN

Countersign verified checkpoints with C2SP transparency-log cosignatures.

ANCHOR

Anchor checkpoints through a pluggable provider — OpenTimestamps to Bitcoin by default — and keep the proofs.

SERVE

Serve retained public proof material.

AUDIT

Apply an organization's own policy to public history.

A node never cosigns a checkpoint it cannot verify, and never cosigns two histories that disagree.

Attestation quorum · anchor providersNode operation is in the developer docs Witness Nodes →

Anchor providers

Anchored beyond the system.

Witness Nodes anchor each checkpoint through a pluggable anchor provider. OpenTimestamps to Bitcoin is the built-in provider and the production default; other anchoring systems plug in through the owp3-anchor-plugin/1 protocol, and every system must define a proof that third parties verify independently. An Ethereum L1 calldata provider is a reference add-on example of the plugin architecture; production anchors to Bitcoin through OpenTimestamps.

0.6 — Developers

Four checks. Two more when you pin keys.

Headless and protocol-first. The TypeScript SDK runs the reference owp3-core compiled to WebAssembly, so a result in your app is byte-for-byte what the reference verifier reports.

import { WitnessdClient, verifyWitness } from "@onli/witness-sdk";

// Anyone can check a proof. No account, no private access.
const log = new WitnessdClient("https://onli-witnessd.onrender.com");

const check = await verifyWitness(log, witnessId, {
  tsPks: [TRANSPARENCY_SERVICE_PK],   // pinned out of band
  checkpointPks: [CHECKPOINT_PK],     // adds note-signed
  nodeKeys: { "node-a": NODE_A_PK },   // adds cosigned
});

check.ok;     // true only when every check passes
check.checks; // published · receipt · stable-id · on-log · note-signed · cosigned
  1. 01

    published

    The bundle is served with state PUBLISHED.

  2. 02

    receipt

    The receipt verifies under the Transparency Service key.

  3. 03

    stable-id

    The statement hashes to the witness_id you asked for.

  4. 04

    on-log

    The statement's index sits inside a checkpoint of the log.

  5. 05

    note-signed checkpointPks

    That checkpoint is signed by the log under a key you pinned.

  6. 06

    cosigned nodeKeys

    At least one Witness Node you pinned cosigned it, and every pinned node's line verifies.

SDK · Claude skill · MCP serverAvailable to approved partners on request Developer docs →

TypeScript

@onli/witness-sdk

Rust

owp3-core · owp3 CLI

Swift

planned

Kotlin

planned

A consensus of one

The record stays private.
The proof is public.
Access belongs to the owner.