Our Key Components

ElizaPay is built from modular components that interact deterministically.

Eliza Agent (Private Banking Operator)

The Eliza Agent is an AI system with a banking function set, including:

Capabilities

• multi-chain balance management

• stablecoin payment routing

• private loan qualification assistance

• savings and yield automation

• anomaly detection and protection

• merchant spending orchestration

Why it matters

Users don’t want to operate DeFi manually. They want:

• automation

• personalization

• safety

• cost optimization

The Eliza Agent delivers this without outsourcing privacy to centralized cloud inference.

Enclave Runtime (TEE Core)

The TEE runtime provides:

• isolated execution

• encrypted memory pages

• sealed storage persistence

• protected key usage (non-exportable)

• attestation capability (verifiable runtime identity)

This is the “private brain jar” of ElizaPay.

ZK Balance Shield (Core Proof Utility)

The ZK Balance Shield is ElizaPay’s proof layer for solvency and authorization.

What it does

Instead of revealing:

• total balance

• wallet addresses

• transaction history

Users can prove statements like:

• balance >= X

• risk score <= threshold

• debt ratio in safe range

• policy compliance true

Why it matters

It unlocks proof-based finance:

• private checkout

• private credit access

• privacy-preserving gating for premium services

Policy Engine (Hard Guardrails)

Policy is treated as code, not UI settings.

Example policies

• Spend Limits: daily total ≤ $200

• Transaction Limits: per tx ≤ $50

• Merchant Categories: denylist gambling contracts

• Chain Restrictions: only Ethereum L2s

• Protocol Restrictions: only audited pools

• Approval Rules: block infinite approvals

• Emergency Switch: freeze all outgoing transactions

How it enforces

Policies are checked inside enclave before signing.

That is the key: policy enforcement must happen before execution, not after.

Connector Modules (Multi-Chain Drivers)

Connectors are standardized plugins for:

• DEX routing

• bridging

• stablecoin transfers

• merchant payment rails

• lending protocols

Connectors:

• provide contract interaction templates

• include safety profiles (known addresses, ABI expectations)

• expose simulation hooks

This is how ElizaPay becomes an extensible OS.

Relayer & Broadcast Layer (Optional)

Depending on mode, ElizaPay can use:

• direct user broadcasting

• privacy-preserving relayers

• batchers (on L2s)

• paymasters (account abstraction)

Relayers can be designed so they do not learn context, receiving only:

• encrypted payloads

• signed transactions

• minimal metadata

Secure Memory Vault (Agent State)

The memory vault contains:

• encrypted state representation

• portfolio commitments

• policy configuration

• pending automation tasks

• previously verified receipts

This vault is sealed so even infrastructure cannot read it.