Decentralized Identity

Your identity on epress is your Ethereum address — a cryptographic key pair you generate yourself. No platform issued it. No platform can revoke it. It is mathematically yours.

Platform Account

The fragile identity

Issued by the platform
Can be revoked at any time
Lost if platform shuts down
Cannot be transferred

Your username, followers, reputation — all borrowed, never owned.

Self-Sovereign Identity

The robust identity

Generated by you, owned by you
Impossible to revoke
Works across all platforms
Fully portable & transferable

Your identity exists independently. No platform can take it away.

Cryptographic Ownership

Your private key never leaves your device. You sign, you prove, you control.

Universal Portability

Take your identity to any EWP-compatible platform. Your reputation travels with you.

Censorship Resistant

No central authority can suspend or delete your account. Your voice cannot be silenced.

Proof of Source

Every piece of content is cryptographically signed by your Ethereum identity. Simple to use, mathematically impossible to forge.

1

Write

New Post
Draft saved
2

Sign

Sign Message

epress.world

Message to sign:

Publish content: 0x7a3f...9e2b

3

Broadcast

Published!

Your content is now signed and ready to be distributed to your followers.

Transaction Hash

0x1a9f...8e3d

Notify-Pull: Efficiency Meets Decentralization

Publishing doesn't crash your server. You broadcast a lightweight cryptographic proof. Followers independently pull the full content. Cost scales naturally with influence.

AlicePublisherBobFollowerCarolFollowerDaveFollowerPoS Notification (~200 bytes)Content Pull (full data)
1

Publisher Broadcasts Proof

Alice creates content, generates a cryptographic hash, and signs it with her private key. She broadcasts only the Proof of Source (PoS)—about 200 bytes—to all her followers.

2

Followers Verify & Request

Each follower node receives the PoS, verifies the signature against Alice's Ethereum address, and then initiates a pull request for the full content.

3

Content Distributes On-Demand

Alice serves the content directly to each requesting node. The cost is distributed: popular publishers invest more in bandwidth, but retain full control and monetization.

Why this matters: In centralized platforms, viral content can bankrupt you with bandwidth costs. In epress, viral content creates economic opportunity. You control the infrastructure, you capture the value, and your reach is limited only by your willingness to serve your audience.

Nodes & Protocol

epress nodes communicate via the epress world protocol (EWP) — an open protocol for content distribution. Each node stores content, manages follows, and syncs with peers.

EWPEWPEWPEWPEWPYour Node· Content· Connections· Profileself-hostedNode B· Content· Connections· ProfileNode C· Content· Connections· ProfileNode D· Content· Connections· Profile

No Central Server

Nodes communicate directly with each other. No company owns the network infrastructure.

Open Protocol

EWP is public. Anyone can implement a compatible node in any language.

Equal Peers

Every node has identical capabilities. No privileged nodes, no gatekeepers.

Content Flow

When you publish, content doesn't just reach your followers — it becomes permanently distributed across the network, each copy carrying its own cryptographic proof of origin.

Alice's NodeSigns contentGenerates PoS{ hash · addresstimestamp · sig }PoS only · ~200 bytesPoS only · ~200 bytesPoS only · ~200 bytesBob's Nodeverify → pull → storeCarol's Nodeverify → pull → storeDave's Nodeverify → pull → storeLocal ReplicaContent + PoS ✓Local ReplicaContent + PoS ✓Local ReplicaContent + PoS ✓Local Timeline ↓Content lives here. Timeline builds from this.

PoS Travels With Content

Every replica carries the original cryptographic proof. Authenticity is verifiable anywhere in the network, without contacting Alice's node.

Local Storage Enables Local Timeline

Because each follower node stores content replicas locally, your timeline is generated entirely on your own node — no central server involved.

Local Timeline

Your timeline is generated locally by your node, aggregating content from everyone you follow. No algorithmic manipulation — just a simple, timestamp-ordered feed you control.

Platform Algorithmic Feed

🔥 TRENDING · SPONSORED

You won't believe what happened...

⚠ Paid promotion

💰 AD · PROMOTED

Buy this product — limited offer

⚠ Advertiser content

👁 VISIBILITY THROTTLED

My honest opinion about...

⚠ Reach limited by algorithm

🔁 SUGGESTED · NOT FOLLOWED

We think you'll like this...

⚠ Platform chose this for you

Platform decides what you see.

VS

epress Timestamp Timeline

14:32Bob

Just deployed my epress node, feels great

✓ Content + PoS verified

13:15Carol

Signed my first post on epress network

✓ Content + PoS verified

12:08You

Welcome to my node — this is home

✓ Content + PoS verified

11:45Bob

Reading the epress whitepaper, chapter 12 is wild

✓ Content + PoS verified

You choose sources. Timestamp order. Nothing hidden.

Ready to Run Your Own Node?

Everything you just learned runs on your own server. One command to install.

Terminal
$ # Install epress on your server

$ curl -fsSL https://epress.world/install.sh | bash