Sovereign Signing Identities — Detached Signatures, Sovereign Identity, and Continuum

Continuum is increasingly evolving into a local-first workspace for sovereign signing identities. This article explores the philosophical and architectural implications of unifying PGP, Bitcoin, Nostr, and eventually SSH identities under a shared challenge → sign → verify model.
Sovereign Signing Identities — Detached Signatures, Sovereign Identity, and Continuum

Andrew G. Stanton - Thursday, May 7, 2026


The deeper I go into Continuum, the more convinced I become that the real idea underneath all of this is not actually “social publishing.”

It is sovereignty.

Not sovereignty in the vague political sense.

Not branding. Not slogans. Not performance.

But actual cryptographic authority that remains under local control.

Tonight’s work on:

  • PGP identities
  • Bitcoin signing identities
  • Nostr signing identities

made that increasingly obvious.

What Continuum is slowly becoming is not merely:

  • a Nostr client
  • a publishing tool
  • a signing utility
  • a cryptography experiment

It is increasingly becoming:

A workspace for sovereign signing identities.

That phrase matters.

Because identity on the modern web is mostly fake sovereignty.

People think they “have accounts.”

But in reality:

  • platforms own the infrastructure
  • platforms control verification
  • platforms control access
  • platforms can revoke identity
  • platforms mediate trust

OAuth logins feel decentralized.

They are not.

Most identity today is still fundamentally:

permissioned identity.

Cryptographic identity changes that relationship.

A private key represents authority that exists independently of the platform.

And what became fascinating tonight is that multiple ecosystems all suddenly started converging into the same conceptual framework.

PGP. Bitcoin. Nostr. Soon SSH.

At first glance these appear to be completely separate worlds.

Different communities. Different tooling. Different purposes. Different cultures.

But underneath the surface, they all revolve around the same primitive:

private key → sign → public verification

That is the deeper pattern.

And once Continuum began supporting:

  • detached signatures
  • external artifact attestations
  • local proof bundles

the similarities became impossible to ignore.

A detached PGP signature proves:

The holder of this private key attested to these exact bytes.

A Bitcoin artifact proof says:

The holder of this secp256k1 private key attested to this exact artifact hash.

A Nostr artifact proof says:

The holder of this Schnorr signing authority attested to this exact external artifact.

These are not fundamentally different concepts.

They are variations of the same deeper idea.

That realization has philosophical implications far beyond software tooling.

Because identity itself begins shifting away from:

platform-mediated identity

and toward:

self-controlled cryptographic authority.

That does not automatically solve trust.

Trust is still human.

Reputation is still human.

But verification changes dramatically.

You no longer need:

  • centralized authentication providers
  • centralized trust brokers
  • platform-controlled publishing
  • hosted verification services

You only need:

  • public verification material
  • the proof
  • the artifact

That is an entirely different trust architecture.

And perhaps the most interesting part is that the proofs themselves are public.

Tonight’s generated proof bundle included:

  • detached PGP signature
  • Bitcoin proof JSON
  • Nostr proof JSON
  • signers.json
  • manifest.json
  • bundled PGP public key

All public.

No private signing authority exposed.

That inversion is profound.

Public proof. Private authority.

That may actually be the best short summary of the entire architecture.

The signer retains control. The verifier gains confidence. The platform becomes optional.

That is why I increasingly think the core abstraction inside Continuum is not:

social publishing

but rather:

local-first cryptographic authority.

And once you begin thinking this way, many other possibilities emerge naturally.

Challenge-response authentication. Portable attestations. Offline verification. Self-sovereign login flows. Public proof bundles. Cross-protocol identity systems.

Even SSH suddenly fits naturally into the same framework.

An SSH key is also:

  • challenge-response
  • signing authority
  • public verification
  • local identity

Again:

Different protocol. Same primitive.

I do not know how broadly useful this will ultimately become.

Most people may never care.

But I increasingly suspect that a smaller group of people:

  • developers
  • researchers
  • open-source maintainers
  • Bitcoin builders
  • sovereign computing advocates
  • security-conscious users

will immediately understand why this matters.

Because at some point you realize:

identity does not actually require a platform.

It only requires:

  • authority
  • proof
  • verification

And that changes how you think about the internet itself.


Write a comment
No comments yet.