Architecture
How Tenebrae Protocol is put together — on host chains you already use.
How it fits
Tenebrae client runs ZK circuits and proves in the browser with client-side ZK Proofs (Noir). Your wallet signs the on-chain submit. On-chain verifiers check those proofs. The Gateway contract is the entry for Protocol operations.
Policy is checked in settlement proofs — upstream KYC and screening stay with you. Detail: Compliance.
Off-client services (indexer · notification) stay untrusted for private details. Detail: Privacy boundaries.
Public assets enter and leave Protocol private state through the Gateway contract (entry surface only — not the product brand). Private transfers and Confidential DeFi update Protocol settlement state.
Protocol building blocks
| Piece | Role |
|---|---|
| ZK circuits | Define valid settlement without revealing private inputs |
| On-chain verifiers | Check submitted proofs on the host chain |
| Gateway contract | On-chain entry for Protocol operations |
| Hub trees | On-chain identity, compliance, and private-asset structures |
| Asset treasury | On-chain vault that holds deposited ERC-20 until withdraw |
| Private transfer links | How recipients are found for private transfers |