Skip to content

LibraryData and agents2014Design paperCorpus record

TLSNotary: notarising a TLS session

TLSNotary. TLSNotary contributors.

TLSNotary publishes a way to split a TLS session so a notary can attest that a server sent some bytes, without the notary seeing every byte and without trusted hardware.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

TLSNotary publishes a way to split a TLS session so a notary can attest that a server sent some bytes, without the notary seeing every byte and without trusted hardware.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
1

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    A notarised webpage is evidence about a session. It is not evidence the page was true, and the notary is still a party.

  2. Claim 02 · Paper model

    The proposal

    TLSNotary publishes a way to split a TLS session so a notary can attest that a server sent some bytes, without the notary seeing every byte and without trusted hardware.

  3. Claim 03 · Paper model

    The mechanism

    The prover and the notary jointly handle the session keys so the notary can sign a commitment to part of the transcript.

  4. Claim 04 · Paper model

    The bound

    This note does not say a court accepts the artefact.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    A notarised webpage is evidence about a session. It is not evidence the page was true, and the notary is still a party.

    Model

    What has to hold

    You are reading TLSNotary's site. DECO is the neighbouring paper.

    Falsifier

    What would retire it

    What can the notary still see?

  2. 02 The proposal

    Observation

    What the study says

    TLSNotary publishes a way to split a TLS session so a notary can attest that a server sent some bytes, without the notary seeing every byte and without trusted hardware.

    Model

    What has to hold

    You are reading TLSNotary's site. DECO is the neighbouring paper.

    Falsifier

    What would retire it

    What does the notary sign?

  3. 03 The mechanism

    Observation

    What the study says

    The prover and the notary jointly handle the session keys so the notary can sign a commitment to part of the transcript.

    Model

    What has to hold

    No price, supply, yield, or adoption figure is added by this desk.

    Falsifier

    What would retire it

    What does the notary sign?

  4. 04 The bound

    Observation

    What the study says

    This note does not say a court accepts the artefact.

    Model

    What has to hold

    You are reading TLSNotary's site. DECO is the neighbouring paper.

    Falsifier

    What would retire it

    How does a verifier check the artefact?

03 Sequence

One action, as an operating tape

  1. 01The prover and the notary jointly handle the session keys so the notary can sign a commitment to part of the transcript.
  2. 02Selective disclosure is the point: the verifier sees a slice. The slice can omit the part that mattered.
  3. 03DECO is a later cryptographic design in the same problem area. It is not this protocol.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    TLSNotary publishes a way to split a TLS session so a notary can attest that a server sent some bytes, without the notary seeing every byte and without trusted hardware.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A malicious notary can break the intended guarantee. The docs' assumption on the notary has to be stated.

  2. What actually moves

    The cut

    Selective disclosure is the point: the verifier sees a slice. The slice can omit the part that mattered.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

  3. What a later deployment may change

    The cut

    DECO is a later cryptographic design in the same problem area. It is not this protocol.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading TLSNotary's site. DECO is the neighbouring paper.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

No performance claim is made.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  1. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

A notarised webpage is evidence about a session. It is not evidence the page was true, and the notary is still a party.

What the design proposes

  • The prover and the notary jointly handle the session keys so the notary can sign a commitment to part of the transcript.
  • Selective disclosure is the point: the verifier sees a slice. The slice can omit the part that mattered.
  • DECO is a later cryptographic design in the same problem area. It is not this protocol.

How the mechanism is specified

  • The prover and the notary jointly handle the session keys so the notary can sign a commitment to part of the transcript.
  • Selective disclosure is the point: the verifier sees a slice. The slice can omit the part that mattered.
  • DECO is a later cryptographic design in the same problem area. It is not this protocol.

What this page does not treat as proven

  • This note does not say a court accepts the artefact.
  • A malicious notary can break the intended guarantee. The docs' assumption on the notary has to be stated.
  • No performance claim is made.

Why the desk still reads it

TLSNotary publishes a way to split a TLS session so a notary can attest that a server sent some bytes, without the notary seeing every byte and without trusted hardware.

09 Lexicon

Terms, opened into the record

Notary
A party who attests the session. Trust does not disappear. It moves.
Selective disclosure
Showing a slice of a transcript. Omission is possible.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.