Architecture
Zeny's architecture is designed for speed, transparency, and non-custodial operation.
System Components
- Facilitator API — Verifies and settles payments (REST endpoints)
- MegaETH RPC — On-chain balance checks and settlement
- USDM Contract — ERC-20 stablecoin at
0xfafddbb3...ef82079e7 - Seller Database — PostgreSQL for seller profiles, endpoints, and enriched tx data
- SDK — TypeScript client/server/React for integrators
Payment Flow
Agent → Protected API → 402 Response
↓
Agent → Signs Payment → Retries with Payment-Signature
↓
Server → Zeny /verify → Signature + balance check
↓
Server → Zeny /settle → On-chain USDM transfer
↓
Agent ← 200 OK + ResourceSecurity Model
- Non-custodial — Zeny never holds user funds
- Signature-based — EIP-712 typed data signatures
- On-chain verification — Balance and allowance checked on MegaETH
- Replay protection — Nonce-based to prevent double-spend
- Time-bounded — Authorizations expire after
validBefore
Chain Details
| Parameter | Value |
|---|---|
| Chain | MegaETH |
| Chain ID | 4326 |
| RPC | https://mainnet.megaeth.com/rpc |
| Block Time | ~10ms |
| TPS | 100,000+ |
| Settlement Asset | USDM |
| USDM Address | 0xfafddbb3fc7688494971a79cc65dca3ef82079e7 |