EWP Architecture

The protocol model is organized as concepts, flows, and transport interfaces. This chapter documents the canonical structure of epress world protocol for interoperable node behavior.

Protocol Concepts

Identity

Node identity is rooted in Ethereum address ownership and signature verification.

Routes: GET /ewp/profile

Node

A node exposes profile, avatar, settings, and APIs as an autonomous social endpoint.

Routes: GET /ewp/profile, GET /ewp/avatar, PATCH /ewp/nodes/:address

Connection

Follow relationships are created and removed through signed handshakes.

Routes: POST /ewp/connections, DELETE /ewp/connections

Publication

Publications bind author identity to content hash and optional signature.

Routes: GET /ewp/publications, GET /ewp/contents/:content_hash

Replication

Follower nodes replicate signed content from followed publishers.

Routes: POST /ewp/replications

Proof/Signature

Typed-data signatures and timestamp validation enforce authenticity and replay resistance.

Routes: POST /ewp/connections, DELETE /ewp/connections, PATCH /ewp/nodes/:address, POST /ewp/replications

Trust and Verification Boundaries

Identity is anchored on Ethereum address verification.
Cross-node writes require typed-data signature validation and freshness checks.
Replication is gated by relationship state, not by anonymous push.
Profile and publication updates are accepted only when signatures and timestamps are valid.

Open EIP-712 Signing Spec