ATOMIC MULTI-AGENT
ORCHESTRATION TEE

Secure multi-agent dual-signing & zero-leak enclaves. Execute payouts with zero side-effects on transaction rollback.

8,500USDC STAKED
100%OCC INTEGRITY
0SLASH EVENTS

PAYOUT COMPOSER

TEE Mode Active
CLIENT-SIDE CRYPTO STAGEPRE-ORCHESTRATION
1. Ephemeral ECDH Key Pair:Generated
2. Shared Secret (HKDF-SHA256):Derived
3. ECIES Envelope (AES-256-GCM):Targeting Executor PubKey
4. Groth16 Compliance ZK Proof:Amount <= Limit Commitment
ANOMALY SIMULATION INJECTORS

TEE WAR-ROOM TIMELINE

Status:draft
Step 1: approver a

Awaiting coordinator trigger

Step 2: approver b

Awaiting coordinator trigger

Step 3: executor

Awaiting coordinator trigger

ATOMIC STATE JOURNAL

TEE KV Store (CCF Replicated)Namespace: synod:coord
Key:synod:coord:payout_2281
Staged Value:empty
Step Consensus LedgerNamespace: synod:step
synod:step:payout_2281:0 (Treasury)EMPTY
synod:step:payout_2281:1 (Compliance)EMPTY
synod:step:payout_2281:2 (Executor)EMPTY
TARGET HOST: https://treasury.sandbox.test/payout
Inactive. Awaiting trigger.

ACTIVE TEE SPECIALIST ENCLAVES

approver a

Treasury Checker
Active
Enclave Stake:1,500 USDC
Evaluations:42
Address:0x3C44...93BC

approver b

Compliance Auditor
Active
Enclave Stake:2,000 USDC
Evaluations:42
Address:0x90F7...b906

executor

Blind Paymaster
Active
Enclave Stake:5,000 USDC
Evaluations:42
Address:0x15d3...a400

TEE LOG TELEMETRY STREAM

Awaiting telemetry logs... Deploy a transaction above.

FREQUENTLY ASKED QUESTIONS

WHO IT'S FOR

Illustrative usage scenarios — not real testimonials. See the Hackathon Simulation Context below.

A treasury payout should only execute if compliance approves in the same breath — Synod runs both agents in one TEE transaction, so there are never partial commits.

TM
DAO treasury managerAtomic multi-sig payouts

I need to enforce spend thresholds without seeing the raw amounts — the compliance agent vetoes blindly inside the enclave and the whole transaction reverts on a no.

CR
Compliance reviewerBlind policy checks

Chaining agents that can hire and co-approve each other only works if a single veto rolls everything back. contracts-call gives us that all-or-nothing guarantee.

OE
Multi-agent ops engineerCross-contract orchestration

DEPLOY MULTI-AGENT ORCHESTRATION

Get notified about upcoming mainnet enclave instances and developer SDK pre-releases. Enter your email to join the waitlist.

Hackathon Simulation Context

Synod is a demo built for the DoraHacks T3 ADK Launch Edition. The enclave, Treasury/Compliance/Executor agents, and ZK compliance checks run in a local sandbox against simulated Terminal 3 host APIs — no funds move and approver state is seeded test data. The personas above are illustrative use cases, not real testimonials. What is real: Rust→WASM enclave contracts coordinated by a synchronous contracts-calltransaction with atomic single-veto rollback, and kv-store staging state (submitting/committed/aborted).