EIP-712 Signing Spec

EIP-712 typed data and Ethereum signatures are the trust backbone of epress world protocol. For state-changing or provenance-critical interactions, nodes depend on typed-data signatures to verify signer identity, payload integrity, and intent timestamp.

What Is Signed vs What Is Read

Read-only discovery endpoints such as GET /ewp/profile and GET /ewp/publications are not signed requests.
Cross-node state transitions and content provenance rely on EIP-712 signatures.
Verification includes signer recovery, identity binding, and timestamp freshness checks.

Cross-node Types

Protocol-level typed data shared between peer nodes.

CreateConnection
DeleteConnection
NodeProfileUpdate
StatementOfSource

Node-local Types

Application-level typed data used by node runtime workflows.

CommentSignature
DATA
DeleteComment

Typed Data Catalog

Structured field-level definitions for every current primaryType.

Verification Rules

Server-side acceptance checks and error mapping per type.

Security Model

Replay resistance, signer binding, and trust boundaries with flow diagrams.