Elch on Nostr: ...

quoting
naddr1qq…vdfa

Andrew G. Stanton - Friday, March 13, 2026

---

Continuum is designed to give users sovereign custody of identity, writing, and archives while still publishing to the Nostr network.
The questions below address common concerns people have when first installing or running the system.

---

What exactly is Continuum?

Continuum is a local-first publishing node for authors.

It manages:

• sovereign identity (npubs)
• signed content (articles and notes)
• relay publishing on the Nostr network
• durable local archives of your work

Continuum runs entirely on your machine.

There are no cloud dependencies and no external platform required to operate it.

You control your keys, your writing, and your archive.

---

Is Continuum a notary or proof-of-authorship service?

No.

Continuum is not a notarization or timestamping service.

Some systems focus on taking content, hashing it, and anchoring a proof to a blockchain to demonstrate authorship.

Continuum operates at a different layer.

Instead of proving authorship through a service, Continuum enables sovereign publishing by allowing authors to:

• maintain custody of their identities
• sign their content directly
• publish to distributed relays
• maintain a durable local archive

In other words:

Continuum = author node

rather than

notary service

Because all content is signed, Continuum could be extended to support notarization workflows if desired, but that is not its primary purpose.

The primary goal is local custody and durable publishing, not proof services.

---

Local-first? What if I lose my data?

Local-first does not mean fragile. It means you control the primary copy.

Continuum protects your work through multiple durability layers:

• Local database – fast access to your notes and articles
• Nostr relays – published content is distributed across the network
• Archive export – your signed history can be reconstructed
• Backups – you can copy the archive directory anywhere

Even if your machine fails, your content can usually be recovered from relays or archives.

Local-first gives you control, not risk.

---

Multiple keys? What if I get hacked?

Continuum reduces risk compared to centralized platforms.

You can:

• use separate identities (npubs) for different roles
• rotate identities if necessary
• isolate publishing identities

If a key is compromised, you can stop using it and create a new one.

There is no centralized account that can be taken over.

---

What if I lose my keys?

Private keys should be backed up, but you have options:

• Continuum stores keys locally in identity files
• those files can be copied or encrypted for backup
• multiple identities can be created and used

Even if a key is lost, published content remains verifiable on the Nostr network.

For experimentation you can also create throwaway keys.

---

Docker? Isn’t that complicated?

Docker simply runs Continuum in a self-contained environment.

Benefits include:

• no dependency conflicts
• predictable environment
• easier upgrades
• isolation from the rest of your system

Typical setup:

1. Install Docker (one time)
2. Run the provided script
3. Open the local dashboard

After that Continuum behaves like a normal local application.

---

ZIP download — what about viruses or tampering?

Each Continuum release includes a SHA-256 checksum so you can verify the download.

After downloading the archive run:

shasum -a 256 continuum.zip

This produces a hash value.

Compare it with the official hash provided in the release .txt file.

If the values match:

• the file downloaded correctly
• the contents have not been modified or corrupted

If the values do not match, discard the file and download again.

You can also:

• inspect the ZIP contents
• scan with antivirus tools
• run the software inside Docker isolation

---

Local custody — what about discovery?

Local custody does not isolate your content.

Continuum publishes to the Nostr network, which provides:

• distributed relays
• global discovery
• multiple compatible clients (Primal, Coracle, etc.)

Your archive stays under your control while your content can still be discovered across the ecosystem.

---

Can I test Continuum without commitment?

Yes.

You can experiment safely by:

• creating a new test identity
• publishing a few notes
• exploring the dashboard

If you decide not to continue, simply delete the folder.

Nothing persists outside your machine unless you choose to publish to relays.

---

The Principle Behind Continuum

Continuum follows a simple idea:

Your identity, your keys, your content.

Instead of trusting a platform to preserve your work, you maintain sovereign custody while still benefiting from a distributed network.

Continuum prioritizes:

• durability
• portability
• independence
• verifiable authorship

Running Continuum is closer to operating a personal publishing node than signing up for another cloud account.

---

Why not just use a folder of Markdown files and Git?

Using Markdown files with Git is a good practice and many developers already work this way.

Continuum does not replace that idea — it builds on it and extends it into a sovereign publishing system.

A simple Markdown + Git workflow gives you:

• local files
• version history
• backups if you push to a remote repository

Continuum adds several capabilities that Markdown + Git alone does not provide:

Sovereign identity

Continuum is built around cryptographic identity (npub).

Every piece of content is signed by the author's key, creating verifiable authorship across the Nostr network.

Git commits can be signed, but those signatures usually remain within the repository context.

Continuum signatures travel with the content itself.

---

Distributed publishing

Git manages repositories.

Continuum publishes directly to Nostr relays, allowing content to be discovered across the network without relying on a central hosting platform.

Your work becomes part of a distributed publishing ecosystem rather than a single repository.

---

Durable archives

Continuum maintains structured archives of signed content that can be rebuilt if needed.

This creates a durable record of authorship and publication history that can be recovered independently of any single platform.

Git preserves file history, but it is not designed as a long-term publishing and authorship archive.

---

Multi-identity workflows

Continuum allows you to manage multiple identities (npubs) in a single environment.

This makes it possible to publish under different identities while keeping each identity's keys and content organized.

Git repositories typically assume a single identity per repository.

---

Local-first publishing

Continuum acts more like a personal author node than a repository.

It manages:

• identity
• signing
• publishing
• relay distribution
• archives

while still keeping everything locally under your control.

---

The difference in perspective

A Markdown + Git workflow looks like this:

Markdown files
↓
Git repository
↓
Hosting platform

Continuum looks more like this:

Identity (npub)
↓
Signed content
↓
Local archive
↓
Distributed publishing (Nostr relays)

Both approaches value local files, but Continuum integrates identity, publishing, and durability into one coherent system.

If Markdown + Git already meets all of your needs, you may not need Continuum.

But many writers and builders want something that provides sovereign identity and distributed publishing, not just version control.

---

Why not just use a Nostr client like Primal, Damus, or Coracle?

Nostr clients are excellent tools for reading and interacting with the network.

They focus on:

• browsing content
• social interactions
• short-form posting
• following other users

Continuum serves a different purpose.

It is designed to function as a local-first author node that manages identity, publishing, and archives.

Nostr clients

Typical Nostr clients provide:

• timeline browsing
• replies and social interaction
• reposts and likes
• ephemeral posting

Most clients treat content primarily as social feed activity.

---

Continuum

Continuum focuses on durable authorship and publishing.

It manages:

• sovereign identity (npubs)
• signed articles and notes
• local archives of all published content
• structured publishing workflows
• relay distribution
• recoverable publishing history

Instead of treating posts as ephemeral feed items, Continuum treats them as signed artifacts of authorship.

---

The architectural difference

A typical client workflow looks like this:

User
↓
Client app
↓
Relays
↓
Timeline feeds

Continuum operates more like this:

Identity (npub)
↓
Signed content
↓
Local archive
↓
Distributed relays
↓
Nostr ecosystem

In this model the author node is primary, and the network is a distribution layer.

---

Complementary tools

Continuum does not replace Nostr clients.

In fact, many users will:

• publish using Continuum
• read and interact using their favorite Nostr client

Continuum focuses on creating durable, signed work, while clients focus on consuming and interacting with content.

---

Why this distinction matters

Most social platforms prioritize engagement and feeds.

Continuum prioritizes:

• authorship
• custody
• durability
• verifiable history

It treats writing more like published work than social activity.

---

Why should I care about owning my publishing infrastructure?

Most people today publish their work using tools or platforms they do not control.

Examples include:

• social networks
• blogging platforms
• cloud-based writing tools
• newsletter services
• most Nostr clients

These tools are convenient, but they come with tradeoffs.

Your work becomes dependent on:

• the platform’s policies
• the platform’s availability
• the platform’s business model
• the platform’s long-term survival

Even in decentralized systems like Nostr, most users still rely on third-party clients.

Those clients typically require your private key or delegated signing authority, meaning you still trust a third-party tool to perform signing operations.

Continuum takes a different approach.

Instead of publishing through a platform or client, Continuum allows authors to run their own local publishing node.

This means:

• your identity belongs to you
• your private keys remain under your control
• signing happens locally
• your content is stored locally
• your archive is portable
• publishing happens through a distributed network

In this model, clients and platforms become interfaces, not gatekeepers.

Your work remains yours regardless of which clients or services exist in the future.

---

The traditional model

Most online publishing looks like this:

Author
↓
Platform account
↓
Platform database
↓
Readers

If the platform disappears, the connection between author and reader disappears as well.

---

The Continuum model

Continuum treats authorship differently:

Author identity
↓
Signed content
↓
Local archive
↓
Distributed relays
↓
Multiple clients and readers

Your writing is not tied to a single platform.

It exists as a set of signed artifacts that can be distributed and verified across the network.

---

A shift in perspective

Continuum is based on a simple idea:

Writers should own their publishing infrastructure.

Instead of relying on centralized services, authors can maintain custody of their identity and work while still participating in a global network.

This approach emphasizes:

• independence
• durability
• portability
• verifiable authorship
• long-term preservation

It may look different from typical cloud platforms, but it restores something that existed in earlier eras of computing:

the author runs the node.