THE PERMANENT INK PROTOCOL · PIP-1

Write once.
Verify forever.

An open standard that gives every piece of writing a name made from the writing itself. Change a single comma and the name changes. No account. No platform. Nothing to rent.

Change a comma Read the Yellow Paper SOON
RELEASE CANDIDATE 1 · OPEN FOR PUBLIC REVIEW

The name of the words above

pip1:t:pip1:t:8186c5e1db209ab3aa29f88d8073f264a30fa2c54120369503044183e19f96ba

Computed by the rules in the Yellow Paper. Change one comma and it becomes a different string. Try it →

01 — THE PROBLEM

Writing online has four ways to die.

A book on a shelf survives because it needs nothing. A page on the internet needs everything.

  1. I

    The host disappears.

    The site closes. The company is sold. The bill goes unpaid, and the words go with it.

    LEFT TO STORAGE NETWORKS
  2. II

    The text is quietly changed.

    A sentence is edited and no one is told. The old version is gone, and nobody can prove it ever existed.

    ADDRESSED BY PIP-1
  3. III

    The address stops working.

    A link points to a place, not to a thing. When the place changes, the link breaks, or worse, leads somewhere else.

    ADDRESSED BY PIP-1
  4. IV

    The proof belongs to someone else.

    Who wrote this? The answer lives in a database owned by a party that may not exist in fifty years.

    ADDRESSED BY PIP-1

Ink answers the last three with mathematics. For the first, it hands over to the storage networks built on top.

02 — THE IDEA

A name made of the writing itself.

Today, an address tells you where something lives. Ours tells you what it is.

We take your words and boil them down to a short fingerprint. That fingerprint becomes the name. The same words give the same name, on any computer, in any year. Different words give a different name.

A place example.com/essay Can move, close, or change.
A name pip1:t:8186c5e1…96ba Can’t change without changing itself.
1

Same words, same name.

2

One comma, a different name.

3

Anyone can check, offline.

We call it content addressing. You don’t need to remember that.

03 — SEE IT

Don’t take our word for it. Change a comma.

This runs in your browser. Nothing you type leaves this page.

Markdown or plain text. Up to 64 KiB.
Presets:
Same words, different file?

Editors disagree about invisible things. Pretend your file came from somewhere else.

The name we compute
pip1:t:8186c5e1db209ab3aa29f88d8073f264a30fa2c54120369503044183e19f96ba

0 of 64 digits changed · 48 bytes · 1 chunk

This is a working copy of the Yellow Paper’s text-naming rules (sections 4 and 5). It skips one check, the Unicode 18.0.0 list of assigned characters, which the reference implementation performs.

04 — HOW IT WORKS

Four steps. No trust required.

  1. 1

    Tidy the bytes, never the words.

    Editors disagree about line endings, invisible marks and how accents are stored. We settle those arguments, and only those. What you wrote is never touched.

    ef bb bf 43 61 66 65 cc 81 0d 0a → 43 61 66 c3 a9 0a

    Café, saved three different ways, becomes one set of bytes.

  2. 2

    Give it a name.

    The text is cut into small pieces and folded into a tree of fingerprints. The top of the tree is its name, so even a single paragraph can be proven to belong.

    pip1:t:8186c5e1…96ba — 48 bytes · 1 chunk
  3. 3

    Bind it together.

    A small plain-text record lists the title, licence, sources you cite, earlier versions and who the authors are. It gets its own name. Change one line and that name changes too.

    pip-manifest 1
    profile pip-1
    title Test Manuscript
    text pip1:t:8186c5e1…96ba 48
    author pip1:k:2b27c5d4…130b

    From the Yellow Paper’s test manifest. Identifiers shortened.

  4. 4

    Sign it for the long run.

    Authors sign the record with the post-quantum standards NIST published in 2024. A signature says one key approved this exact record, in a stated role.

    role 01 · ml-dsa-87 · signature 4,627 bytes

Then anyone, anywhere, can check all of it with nothing but the files.

05 — SIGNATURES

Signed for computers that don’t exist yet.

Today’s signatures are expected to fall to a large enough quantum computer. A signature on a manuscript should mean something for centuries. So we use only the new post-quantum standards.

ML-DSA

Built on lattices.

Standard
FIPS 204
Profile
ML-DSA-87 · Category 5
Size
4,627-byte signature

SLH-DSA

Built on hashes alone.

Standard
FIPS 205
Profile
SHAKE-256s · Category 5
Size
29,792-byte signature

Different mathematics. If one family ever weakens, the other still stands. Sign with both, and a forger would have to break both.

Honestly: both families lean on the same hash permutation, Keccak. The Yellow Paper says so, and describes how a work is renewed if that ever weakens.

Not used: RSA · ECDSA · EdDSA · ML-DSA-44

06 — CITATIONS

A citation that can’t be quietly redirected.

When you cite a work, you cite its name. If anyone serves different words under that name, the check fails.

cite:pip1:t:9e13e0cc…f413#b=0-5
Bytes 0 to 5 of one specific text. Anyone can check them.

You can point at an exact passage, and prove it is there.

A citation can still point to something nobody has kept. That is a problem of finding, not of truth. Ink can tell you what is missing. It can’t summon it.

07 — LIMITS

What Ink does not do.

  • It can’t prove who a person is. A signature proves a key signed. Anyone can copy a text and sign it first.
  • It can’t prove who had an idea first. Time evidence bounds when exact words existed, not when they were imagined.
  • It can’t keep a copy alive. A name can’t be forged, but it can’t summon bytes either.
  • It can’t stop deletion. It makes tampering visible. Keeping copies is the job of storage.
  • It can’t protect you from look-alikes. A new text can use letters that only look familiar. Readers must stay alert.
  • It can’t judge a text. Ink names bytes. It says nothing about legality or merit.
  • Not yet: secrecy, anonymity, revocation. None of these is in version 1.

We’d rather tell you now.

08 — BEYOND THE INK

The ink is the foundation.

Everything above this line is specified. Everything below is a proposal. We mark the difference every time.

SPECIFIED IN PIP-1 ↑
PROPOSED ↓

Storage

PROPOSED

Long-term copies, paid for once through an endowment, kept by many independent nodes.

Curation

PROPOSED

If everything is permanent, so is spam. Guilds of readers decide what enters the Canon.

Reading

PLANNED

A quiet reader with no ads, no popups and no hidden ranking.

Mirrors

PLANNED

Small archive boxes anyone can run. Text is tiny.

09 — THE CONSTITUTION

The Constitution of the Sovereign Word.

DRAFT PRINCIPLES · TO BE RATIFIED BY A FOUNDING COHORT

  1. The right of un-erasability.

    What enters the Canon is never silently changed or removed. Revisions are added beside the original, never over it.

  2. The right of attribution.

    A writer’s signed claim of authorship travels with the work, wherever it is copied.

  3. The right of exit.

    No reading app owns the library. If one turns bad, anyone can build another over the same books.

  4. The right of estate.

    Writers decide in advance who inherits their work, or whether it passes to the public domain.

  5. Freedom from black boxes.

    Discovery runs on open, explainable rules, never on a hidden engagement algorithm.

Proposed. To be ratified by a founding cohort of writers, scientists and essayists.

10 — ROADMAP

Four phases. One honest status for each.

PHASE 1

The specification

  • Yellow Paper PIP-1 IN PUBLIC REVIEW
  • Reference implementation (Python) INCLUDED
  • Publishing tool for writers PLANNED
  • The Constitution, version 1.0 DRAFTING
PHASE 2

The bridge

  • Storage endowment and registry PROPOSED
  • Citation graph PLANNED
  • Anonymous pen names EXPLORING
PHASE 3

The reading room

  • The Sanctuary reader PLANNED
  • Curator guilds PROPOSED
  • Estates and shared royalties PROPOSED
PHASE 4

The mirrors

  • Cold-storage archive boxes PLANNED

No dates. We will not promise what we have not built.

11 — HELP US BREAK IT

Help us break it.

Version 1.0 is not final. Before it is, three things have to happen, and each needs people who are not us.

Build it again.

Write an independent version in another language. See whether you get our numbers.

Review it.

Cryptographers: attack the domain separation, the tree, the signed message and the renewal design.

Check the numbers.

Compare the ML-DSA test vectors with a second implementation and with NIST’s validation data.

There are three more open items in section 14.3 of the Yellow Paper.

Read the Yellow Paper SOON Get the test vectors SOON Join the Working Group SOON

Permanent ink. Open to everyone.