Meeting attestation on Cubid

Prove the meeting happened. Prove what was said.

AI made it trivial to fabricate an interview. ProofOfMeetProtocol gives every interview, focus group, and source conversation a verification page: distinct real humans, a span of time, and the exact version of the record each of them endorsed.

Pre-launch. Version 0.2 is built and under test with design partners. Nothing on this page is a promise of a launch date.

Where we are, honestly

What exists today, and what does not.

We would rather you knew exactly what you are signing up for.

Built

Version 0.1, the core

Workspaces, Cubid sign-in, invitations, attendance and record attestations, Merkle commitments over records, disclosure profiles, verification pages, daily anchoring, REST API, SDK, and MCP server.

Built

Version 0.2, history and provenance

An append-only commit chain per workspace, provenance declarations for every document, witness statements from participants, and a computed human-involvement grade.

In progress

Deployment and design partners

Production sign-in with Cubid, the first hosted deployment, and the first university departments as design partners. Access is invite-only through an allowlist.

Designed, not built

VerifyMyResearch, institutions, Safe2Meet

The research application, institutional licensing, participant-held keys, and the Safe2Meet integration are specified in the whitepaper and PRDs but not yet built. Pricing is designed, not enforced; pre-launch versions take no money.

How it works

Three attestations. One page anyone can check.

  1. 01

    Open a workspace

    Create one for a meeting, attach the recording link, transcript, or notes, and declare where each document came from. Every change is a commit in a chain that cannot be rewritten.

  2. 02

    Invite the people who were there

    Each participant signs in with Cubid, which proves they are one distinct human. They attest attendance, approve the record, and choose how much of themselves to reveal.

  3. 03

    Share the verification page

    A reader sees what is proven and what is not: who attested, to which commit, with what statement, and when the whole thing was anchored.

Exact claims

What a verification page proves.

And what it never claims to. The page says both, in the same words, every time.

What the page proves

  • A workspace with this metadata existed by the times shown.
  • Each participant is a distinct human with the humanity score shown.
  • Each attestation was signed by that participant, for that span and that commit.
  • Anchored items existed by the time their batch root was published.

What it does not claim

  • That any transcript is accurate to what was said.
  • That a provenance declaration is true, only that it was committed.
  • That participants were not paid or coerced.
  • That a recording behind a hash can be retrieved.

Anchoring

Every attestation and commit lands in a daily batch anchored in Bitcoin.

Batch roots are signed with a published key, listed on the transparency page, and submitted to OpenTimestamps, which commits them into the Bitcoin blockchain. A receipt for any item proves it existed by the time its batch was published, and anyone can recompute the root with the open SDK.

  • Daily batches over attestation and commit hashes
  • Receipts by attestation id or commit hash
  • Transparency page lists every batch and its status
  • Roots timestamped into Bitcoin through OpenTimestamps

POAP reimagined

Loved POAP? This is where it went.

The Proof of Attendance Protocol taught people to collect proof that they were there. ProofOfMeetProtocol keeps the habits and fixes the proof.Read POAP Reimagined

  • A meeting in a minute, an emblem for every one, a collection on your handle
  • Kiosk QR at the door or three words said aloud; attest in under three minutes
  • Real humans, a span of time and an endorsed record, anchored to Bitcoin

Ask for early access.

Invitations go out in small batches to people with a real study, story, or course to verify. Tell us what you would use it for.

Your email and name are stored encrypted and used only to reply to you. No newsletters, no sharing.