Open · decentralized · verifiable

Your identity.
Your presence.
Your terms.

Publish a cryptographically verifiable declaration of where you can be found online—independent of any platform.

Read the specification Explore on GitHub

Signed JSON
documents

No central
owner

Built for the
open web

◇presence.json

✓ Verified

{
  "issued_at": "2026-07-16T04:00:00Z",
  "public_key": "gNhdiLJhE0NRL5BOnRV1Zi1wEGINqDLzR2329ikZk0c",
  "services": [
    {
      "type": "Website",
      "url": "https://jodydawkins.com"
    },
    {
      "type": "Tidal",
      "url": "https://tidal.com/artist/20195859"
    },
    {
      "type": "Spotify",
      "url": "https://open.spotify.com/artist/522ZyQMBe0xOfnJl9wWM4U"
    },
    {
      "type": "Apple Music",
      "url": "https://music.apple.com/us/artist/jody-dawkins/1520886678"
    },
    {
      "type": "YouTube",
      "url": "https://www.youtube.com/channel/UCsHFy8n7pQKf0feE0RxLNpQ/videos"
    },
    {
      "type": "GitHub",
      "url": "https://github.com/jodydawkins"
    },
    {
      "type": "Instagram",
      "url": "https://www.instagram.com/jody_dawkins/"
    },
    {
      "type": "TikTok",
      "url": "https://tiktok.com/@jody_dawkins"
    }
  ],
  "signature": {
    "algorithm": "ed25519",
    "value": "Grem07CoHHF-aHQrjzPON4pLE0PHZxjcvn7wGPGc4eDrzX0xyIlBNNFV64DooVb_fpRUkr-d-NvRjJ9jpPAVBQ"
  },
  "subject": "key:sha256:r04mk-KJfvTnlnVSTUpnT283CGbHSWJkFMevj-G72Ts",
  "type": "open-presence",
  "version": "0.1"
}

Live documentjodydawkins.com ↗

Document status Valid

01 / The idea

Your online presence should not belong to a platform.

OPP defines a small, signed JSON document that declares your public services. It does not define your identity or carry your content. You publish the declaration; any compatible application can verify it.

✦

Declare

List the HTTPS services that make up your public presence.

⌁

Sign

Canonicalize the document and sign it with an Ed25519 key.

◎

Verify

Any consumer can check the subject, signature, timestamps, and service URLs.

02 / Why OPP?

The relationship should belong to the people in it.

People are scattered across websites, feeds, social networks, and services. Today, platforms mediate those connections—and can reshape, restrict, or erase them.

OPP gives each person a portable, verifiable declaration of where they can be found. Applications can follow the person while platforms remain replaceable destinations.

Read why OPP exists

03 / The principles

Small by design.
Open by default.

PORTABLE

Platforms are destinations, not owners.

Your presence is a document you control, hosted at an HTTPS location you choose.

VERIFIABLE

Trust the declaration, not the directory.

A directory only resolves the document location. Consumers still fetch and verify the signed document themselves.

FOCUSED

Presence—and nothing else.

OPP does not define identity, content distribution, messaging, social networking, search, or ranking.

04 / Build with OPP

One protocol.
Three reference projects.

The core specification defines presence documents, signing, and verification. The Ruby implementation puts those rules into code. The directory server adds registration and resolution without becoming the source of truth.

Draft specification · Version 0.1 · Experimental

TRY ITVerify a live OPP document

curl -fsSLo presence.json \
  https://jodydawkins.com/.opp/presence.json

opp verify presence.json

Expected output: valid

CORE SPECIFICATION · DRAFT 0.1jodydawkins/opp RUBY REFERENCE IMPLEMENTATIONjodydawkins/opp-ruby REFERENCE DIRECTORY SERVERjodydawkins/opp-directory

Your identity.Your presence.Your terms.