Page Navigation

epress node Developer Docs

Open

Collapsed while browsing epress world protocol docs.

EIP-712 Security Model

In epress world protocol, signatures are not only identity proofs. They are state-transition permissions for node-to-node actions. This model defines where trust is accepted, where payloads are rejected, and how replay and tampering risks are constrained.

Security Guarantees

Signer Binding

Recovered signer address must match protocol identity fields inside the message.

Replay Resistance

Timestamp windows reject expired payloads and stale update attempts.

State Isolation

Even valid signatures cannot bypass relationship checks, resource checks, or ownership checks.

Connection Handshake Security Boundary

Follower NodeFollowee NodeConnection StorePOST /ewp/connections + typedDatarecover signer + check timestamppersist relationship if validWrite accepted only after signer binding and freshness checks

Replication Security Boundary

Publisher NodeFollower NodeTimeline StorePOST /ewp/replications + statementOfSourceverify signature + follow statefetch content + commit publicationContent enters timeline only when proof and relationship are both valid

Node Profile Update Security Boundary

Publisher NodePeer NodeNode CachePATCH /ewp/nodes/:address + typedDataaddress match + signer recoveryapply only if timestamp is newerMonotonic timestamp rule prevents stale profile overwrite