TAPP

For all creators

For all creators.

You made it first.

Put your one line next to what you made. TAPP finds it and fixes only that version's fingerprint in Sigstore Rekor, a public ledger. The text is never sent. Whatever anyone publishes later, the date is on your side.

Try itSee a real record

SEALED · SIGSTORE REKOR · TIME-FIXED · RECORD R · TAPP

What

Every time you publish, a date stamp goes on.

Make it. Publish it. 1

Make it. Publish it.

Write the way you always do, publish the way you always do. No new editor, no new blog. Just add your one line at the end.

The fingerprint gets a time. 2

The fingerprint gets a time.

TAPP finds it and places only that version's "fingerprint" (64 characters derived from the contents; change one character and it changes) in Sigstore Rekor, a public ledger. The same ledger Google and GitHub use to sign software. Nothing written there can be deleted. Not even by TAPP.

A badge next to your work. 3

A badge next to your work.

Your one line becomes the badge. Readers click it and see which version existed when, and can check it themselves.

Text, images, video, code. Any file works the same way.

The text is never sent anywhere. Only the fingerprint.

How it works, in plain words →

When

For the day someone says something. And for the day you want to say something.

A similar post appeared later.

A similar post appeared later.

"Mine was first" — shown not in your words but in a public ledger. Whoever they are, a date is a date.

"This was written by AI."

Drafts before publishing, edits after — every version you stamped lines up with its time. Readers get the material to judge.

A proposal, before you hand it over.

A proposal, before you hand it over.

Stamp once before you send it. Whatever happens after, "this existed before I sent it" doesn't go away.

What stays

What stays

Stays

  • the fingerprint of each version (64 chars)
  • the version number and the previous version's fingerprint
  • the fixed time
  • the ledger entry number

※ This is a third-party record that "this version existed on this date." If someone says something later, take it to a lawyer.

Doesn't stay

  • the text
  • the file name
  • your name
  • how you typed

※ The text never stays, so no one can read it. A fingerprint can't be turned back into text.

Start

Three minutes.

Three minutes.

  1. Sign up for ¥500 a month
  2. Add your note username or RSS feed on /me (once)
  3. Put your one line next to what you made (end of a post, video description, README, caption)

Finding and stamping is TAPP's job.

Try it See a real record

For developers (command line) → /en/writing#cli

Why I built this

I've made and shipped a lot of things on my own. I won't say who, but big companies copy them right away. Creators must not lose to capital. That's why I built this.

I hope it becomes a wedge for creators everywhere.

Mori / andQ Inc.

For teams that deliver apps or data

Facts, on the side of whoever made it first.

Anything that's made can be remade by whoever saw it. There's no stopping that. TAPP changes one point before it: the fact that someone "saw" or "received" it, kept in a form they can't deny later.

The record states facts only — from which network, which account, under which terms, when, and what was received. Judgement is left to whoever reads it.

If you don't write code → Hand it over (business plan)

Facts, on the side of whoever made it first.

How it works, in detail

Three steps. We never hold the text.

01 Receive 01 Receive

Your app tells TAPP the facts.

The delivering app sends "to whom, under which terms, what" to TAPP. Only the hash of the body is sent; the body stays with you.

POST /v1/seal { recipientId, termsVersion, bodyHash }
02 Seal 02 Seal

The record becomes one value.

Record R is canonicalized and hashed together with a secret random s. R and s stay with TAPP and never leave.

h = SHA-256( d ‖ s ‖ JCS(R) )
03 Fix 03 Fix

A time is stamped in a public log.

h is signed and registered in Sigstore Rekor (a public transparency log); only after the signed receipt is verified is the body sent. The order is never reversed.

hashedrekord → logIndex · integratedTime

Verify

Verify a record.

Enter a deliveryId to see the disclosure (record R, secret s, receipt) and a link to the entry in the public log. Recompute h yourself and compare.

Scope

What is public, what is not.

Goes to the public log

  • commitment h (32-byte hash)
  • TAPP's signing public key (same as /v1/keys)
  • registration time (integratedTime) and position (logIndex)

Does not

  • the body — TAPP never holds it
  • email, IP, network organization — only in the provider's authenticated admin view and the provider's own fact bundle
  • record R and secret s — as disclosure, only to whoever holds the deliveryId

Go ahead, copy it. The notice is already in the mail.

— Creators, everywhere

TAPP seal