skip to content

day 277 of the operation / 05.10.2026

Proxfrito

← notes

notes03/10/2026

explain this: Proving the text is the same: that already exists

Stamping content on a blockchain is older than our hackathon. Three examples answer the question — and show where our piece fits.

  • blockchain
  • content
  • solana

Honest question: does this already exist? It does. Anyone who shows up at an event selling "put the content hash on the blockchain" as new will hear that people have been doing this for years — better to hear it now, for free.

The idea, in one sentence: you do not store the whole text on the blockchain. You store its fingerprint — the result of a calculation (SHA-256) that changes if a single comma changes. The text stays on your site; the fingerprint gets recorded. Later, anyone can recalculate and compare: if it matches, it is the same text.

Three that already do it:

  • OpenTimestamps — an open timestamping standard on Bitcoin. Public calendar servers, libraries in Python, JS, and Java, no sign-up. It is the rawest one: the file goes in, the proof of date comes out.
  • WordProof — a WordPress plugin that stamps posts and products on its own, every 15 minutes, on its own blockchain (EOS). It was born from the SEO problem: proving who published first and who owns the content.
  • ProofGate — runs on Solana devnet, takes a file or text, computes the SHA-256, and writes it to the network via the Memo Program. It is practically our MVP idea, already live. That is good: the technical path is short and known, not a bet.

So why do it again? Because the value is not in the stamp — it is in where it fits.

The three above are stamping tools: you take the content to them and leave the proof in a separate file. Our bet is the opposite: the site already publishes, already versions in markdown, already has a date. The record goes into the publishing flow, not as a separate service. The proof stops being a file you keep in a folder and becomes part of the page — the reader checks it right there, without installing anything.

A small, specific difference. It is not "blockchain solves everything"; it is "content that already exists starts carrying its own proof." Anyone who publishes on their own site gets what today only a CMS plugin owner has.

The event numbers and the deadline are in the previous note — and they are from the official source.