About qub

Trust infrastructure for the agentic web.

qub lets you seal a message today that no one can open until a future date you choose — and prove, when that date arrives, that you wrote it before. No account, no edit button, no way for us to read it. Sealed today, opens then, verifiable forever.

Write what matters. Seal it to a date. Let the future read it.

Why this matters now

Most online content used to come from people. Now a growing share comes from systems that can fabricate any past document — a screenshot, a tweet, a memo, a research note dated to whenever the prompt asked for. Faking evidence after the fact costs almost nothing.

That breaks the assumption everything else runs on: that the past is fixed, and we can check the present against it. When any dated thing could have been generated last Tuesday, "did you actually say this when you said you did?" stops having a clean answer. Screenshots get faked. Posts get edited. Archives get backdated. Even your own platform might quietly let you rewrite yesterday's words.

qub seals a message before it has to predict, commit, or reveal — and proves it afterwards. The proof is mathematical, not editorial. It doesn't depend on qub being online. It doesn't depend on us being trustworthy. As AI gets better at faking the past, that proof gets more valuable — because the people who can show "I wrote this before anyone could have generated it for me" are the ones whose words still count.

If that's the world you're building reputation, evidence, or commitment in — qub is the receipt.

What you can do with it

Predictions. Call an outcome before it happens. Earnings, elections, sports, market moves. When the result is in, you have a timestamp nobody can argue with.

Letters to your future self. Write to where you want to be in a year. Five years. Ten. The reveal lands when you do.

Bets and dares. Settle the argument permanently. Sealed today, opened on the day. No "that's not what I said."

Commitments. Put it in writing without a contract. "I'll book by Friday." "I'll pay $500 for the couch on Friday." Both sides see the same words, sealed in time, before either of you has a chance to remember them differently.

Proof of ideas. Timestamp a thesis, a script, a design before you share it. If someone "happens to come up with" the same thing later, you have proof.

Pacts — bilateral agreements. Two parties. Pick a template (sale of goods, service agreement), fill in the details, share a link. The other party reviews the terms, verifies their email, and co-signs. Both sides commit to the exact same words before the reveal date. No edits in between, no disputes after about who said what.

Embargoes and announcements. Pin the news to a release date. The link is shareable now; the content lands the moment you said it would.

Evidence that you wrote it first. Seal a manuscript draft, a research paper, a design spec, or a code architecture decision before you pitch, publish, or ship. If a competitor's "independent" version surfaces a month later — or if a model trained on your work later claims it as its own — you can point at the seal and end the argument.

AI agent commitments. Agents that make public claims — forecasts, schedules, recommendations — can seal them when made, then be held to the version they actually committed to — not whatever version their operator prefers later.

Embed in your own site. Paste a one-line snippet into a blog post, Notion page, Substack issue, or any HTML, and the live countdown — and the reveal, when the date arrives — renders inline on your page. Decryption happens in the visitor's browser, so qub.social can't tamper with what your visitors see — even when the qub lives on someone else's site.

How it works

  1. Write. Type your qub in the compose box. Format with Markdown — headings, bold, italic, lists, blockquotes, code blocks. No account required.
  2. Seal. Pick a reveal date and confirm. qub locks your message in your browser and uploads the locked copy to permanent public storage. The lock is tied to a worldwide public clock — no one can release it early, not us, not you. For unlocks more than two years out, qub asks you to acknowledge that long reveals depend on that public clock staying online.
  3. Share. Send the link. Before the date, visitors see a live countdown. On the date, the qub opens — decrypted in the visitor's browser using the value the public clock has just published.

Two things follow from how this is built:

For the underlying mechanism — the specific networks involved, the ciphers, the verification procedure — see /protocol and /security.

What else qub does

Sign your work. Generate a signing key in your browser. Every qub you seal gets a cryptographic signature attached. Verify your email against your key to make your identity visible to viewers. Your private key never leaves your device.

Public attribution is opt-in. You decide per qub whether to publish your byline. Default is off — the qub goes up without your identity attached. Turn it on for qubs you want linked to you; the viewer countdown then shows "Sealed by @{handle}". Either way, the signature still proves you wrote it if you ever need to claim it later.

Title your qub. A short title shows on the countdown before the reveal — "Q1 BTC call" reads better than just "Prediction" while the timer ticks down. The title is locked to the qub itself, so nobody between you and the viewer can change what visitors see.

Get notified. Anyone viewing a sealed qub can subscribe to get an email the moment it reveals. One email, on the day — no spam, no account needed.

Reply to a qub. When a qub reveals, viewers can tap "Seal a reply" to write a qub that links back to the original. The link to the parent is sealed inside the reply, so the connection only becomes public when the reply unlocks.

What we deliberately don't do

No account, no password, no profile. No advertising trackers, analytics pixels, or third-party marketing scripts. No reading your content — encryption and decryption happen in your browser, and we couldn't read a sealed qub before its reveal date even if we wanted to. No deleting it either — once a qub is on permanent public storage, it's there permanently. We can hide content from qub.social's viewer if it violates our terms, but the underlying data isn't ours to remove.

Full privacy details live at /privacy. Terms of use at /terms. Security details — how the locking works, what we protect against, what we don't — at /security.

For builders and AI agents

The qub API lets you seal, read, and verify qubs programmatically. There's also an MCP server so AI agents can create and read qubs directly. Webhooks notify your systems when a qub reveals.

See /developer for the API reference, MCP setup, and tier details.

Pricing

Free to try. Paid plans for heavy creators and for AI agents and developers using the API. Current prices — including local-currency display at checkout — at /pricing.

Common questions

Can I format my qub? Yes. qub supports a safe subset of Markdown: headings, bold, italic, strikethrough, lists, blockquotes, code blocks, and horizontal rules. Links and images are stripped for safety — URLs display as plain text.

Can I embed a sealed qub on my own site? Yes. Paste <script async src="https://qub.social/embed/v1.js"></script> once, then drop a <qub-embed qub="…"></qub-embed> tag wherever you want it to render. Every qub's share, countdown, and reveal page has the snippet ready to copy under "Embed on your site".

How do I report problematic content? Every qub has a report button. We keep a blocklist to stop content that violates our terms from displaying on qub.social. We can stop showing a qub; we cannot remove the underlying data from permanent public storage.

Want the full picture?

Contact

Email: support@qub.social

Seal your words.