Trust Model

ElizaPay is explicitly engineered around a minimal trust model.

What the User Must Trust

Users must trust only a small set of assumptions:

A) Cryptography

• signature correctness

• ZK proof soundness

• secure hashing commitments

B) TEE Security Model

• enclave isolation guarantees

• memory encryption effectiveness

• sealed storage correctness

C) Attestation

• that the enclave is running the correct code build

• that it has not been substituted by malicious code

D) Blockchain Settlement

• transaction finality correctness

• smart contract execution rules

What the User Does NOT Have to Trust

ElizaPay aims to remove trust in:

• ElizaPay developers not logging data

• infrastructure provider not snooping

• node operators not copying traffic

• cloud hosting not compromised

• customer support and internal staff

Principle: trust should not be required where architecture can remove it.

Trust Boundaries (Simple Definition)

Trusted Zone: enclave + user-defined policy Untrusted Zone: everything else (servers, routers, relayers, developers)

This is how ElizaPay preserves privacy even in adversarial environments.