@bluthner
🧵 PART 2 - “Inside Zama’s Coordination Layer: The Part No One Talks About”
Once encrypted data enters the system, it needs a coordinator something to route, verify and bridge encrypted states.
That’s where the Gateway comes in.
Think of it as
@zama
’s “air traffic controller”:
✔️ verifies FHE computations
✔️ handles decrypt requests
✔️ moves encrypted assets between chains
✔️ charges tiny protocol fees (paid in $ZAMA)
To keep this insanely fast, Zama runs the Gateway on a dedicated Arbitrum rollup built exclusively for Zama, not for public deployments.
But the Gateway doesn’t compute anything itself.
That job belongs to a different class of nodes…
And you’ll meet them in Part 3. 🔥
#ZamaCreatorProgram