How Seismic Works

What happens when you send a transaction or read your data — explained simply.

Sending a Transaction

When you send a transaction on Seismic, here's what happens in simple terms:

  1. Your wallet encrypts the transaction — using a shared key with the network
  2. The encrypted transaction is sent — nobody can read it on the way
  3. The TEE chip decrypts and executes it — inside the secure zone
  4. Results are stored encrypted — nobody can read them after either

The key point: your data is never visible in plain text. Not while it's being sent, not while it's being processed, not after it's stored.

It's like putting a letter in a locked box, sending it to a vault, and having a robot read it inside the vault without anyone else seeing.

Reading Your Private Data

On Ethereum, anyone can read any data — no ID check needed. But on Seismic, private data is... private. So how do YOU read YOUR data?

The answer: signed reads. You sign your request with your wallet to prove it's really you.

Without this:

  • Anyone could pretend to be you and read your private balance
  • That would defeat the whole purpose of privacy

With signed reads:

  • You prove your identity by signing the request
  • The response is encrypted so only you can read it
  • Fakers get nothing (their address is zeroed out)

Think of it like a bank: you can check your own balance, but you need to show your ID first.

Quiz — Test Your Knowledge

4 questions — 25 points each — 100 points max