| Purpose |
Lightweight intermediary ensuring security in a multi-zone architecture. |
| Asset Management |
Zones manage their own assets and state transitions; the coordination layer does not define or manage assets. |
| Primary Function |
Verifies correct zone transitions and ensures exchanges between zones neither create nor destroy value. |
| Key Responsibilities |
1. State Transition Verification: Verifies zone state transitions using STF and Zone Ledger zk-proofs. 2.Inter-Zone Exchange Balancing: Ensures value-neutral exchanges through equality proofs provided by the block leader. |
| Validation Process |
- Validators verify minimal proofs: - Two proofs per zone (STF and Zone Ledger proofs). - One proof from the block leader for inter-zone exchange balancing.- Future plans include proof aggregation by leaders or third parties. |
| Architecture |
- Zones use a UTXO-based ledger model.- Coordination layer represents zones with a public account-based model (e.g., Ethereum).- Executors in each zone are responsible for submitting proofs to the coordination layer. |
| Efficiency |
- Minimal computation for validators with only a few proofs per zone.- Scalability ensured through zk-proofs, allowing verification without access to underlying data.- Simple account-based representation reduces complexity. |
| Scalability Focus |
- Ensures performance optimization by limiting computational/storage burden.- Future-proof design with potential for aggregated proof mechanisms. |
| Summary |
A proof-based, efficient verification system ensuring correctness and value neutrality in inter-zone exchanges while maintaining scalability and validator efficiency. |