Layer 3 · TEE + ZK Rollup · Robinhood Chain

Private strategies,
run in a TEE, proven by ZK.

ZKHood is a Layer 3 hybrid rollup for tokenized stocks on the Robinhood Chain — your strategies run privately inside a hardware TEE, then a zero-knowledge proof of each batch settles trustlessly onchain. TEE for speed, ZK for finality.

Explore ZKHood Read the Docs
Hood Robinhood Markets
$103.62 ▲ 11.54%
AMZN
$262.07 ▲ 0.47%
COIN
$179.48 ▲ 21.68%

TEE Powered

Hardware-isolated execution

ZK Verified

Zero-knowledge settlement

Instant & Trustless

TEE speed · ZK finality

🔒

Private Portfolios

Deploy capital and rebalance Stock Token positions inside a sealed enclave, hidden from the host and public observers.

⚡

In-Enclave Execution

REVM runs your transactions inside the TEE at the speed of silicon — no heavy cryptographic proving required.

🛡️

ZK-Proven Settlement

A zero-knowledge proof of each batch is submitted to the Robinhood Chain for trustless, hardware-independent final settlement.

Hybrid TEE + ZK Rollup

Execute in a sealed enclave. Settle with a ZK proof.

Within the Layer 3 dApp, users deploy capital, rebalance Stock Token portfolios, and execute strategies with full privacy. Transactions run inside a Trusted Execution Environment — an isolated REVM (Rust EVM) — for instant, private execution. A zero-knowledge proof of the resulting batch is then generated and submitted to the Robinhood Chain for trustless final settlement.

  • 1 User sends a transaction encrypted to the enclave key
  • 2 REVM executes it privately inside the TEE (SGX / TDX)
  • 3 A ZK proof of the resulting batch is generated
  • 4 The proof settles trustlessly on the Robinhood Chain
The Stack

Inside the Enclave

ZKHood runs a super-light REVM inside a TEE for instant, private execution — ferried by Gramine and grounded by a Helios light client — then proves each batch in zero-knowledge for trustless settlement.

🧩

Intel SGX / TDX

Confidential hardware: isolated memory enclaves (SGX) or fully-encrypted VMs (TDX / AMD SEV).

root of trust
⚡

REVM

A modular, ultra-light Rust EVM — the same engine as Reth — running without a full OS.

execution
🚦

Gramine

A Library OS that runs unmodified Rust (REVM) inside SGX, handling its syscall & network limits.

library OS
🛰️

Helios Light Client

Downloads only block headers and verifies Robinhood Chain balances via Merkle proofs.

state verification
execute_private_tx.rs
// Hybrid TEE + ZK: private execution, then ZK settlement
fn execute_private_tx_in_tee(tx: EncryptedTx, proof: StateProof) {
    let decrypted = decrypt_with_tee_key(tx);          // decrypt in sealed memory
    let mut db = CacheDB::new(EmptyDB::default());
    inject_verified_state(&mut db, proof);             // Helios Merkle proofs

    let mut evm = EVM::new();
    evm.database(db);
    evm.env.tx.caller       = decrypted.sender;
    evm.env.tx.transact_to  = TransactTo::Call(decrypted.to);
    evm.env.tx.data         = decrypted.data.into();

    let result   = evm.transact_commit().unwrap();     // Stage 1: silicon-speed execution
    let zk_proof = prove_batch(result.state_root);    // Stage 2: succinct validity proof
    settle_on_robinhood_chain(zk_proof);
}

Cross-Chain Settlement

Move tokenized equities into the hybrid rollup for confidential execution, then settle them back to the Robinhood Chain with a succinct zero-knowledge proof.

Read the Docs
Native Token

The access key to the ZK layer.

At the heart of the protocol is a native token issued on the Robinhood Chain. It acts as a cryptographic access mechanism and powers the economics of confidential execution and proof generation — creating a direct pathway for capturing and accruing protocol value.

🗝️

Staked Access

Users stake the native token to unlock the TEE + ZK layer and enter private, in-enclave execution.

⚙️

Proof-Generation Fees

The token is the payment mechanism for ZK proof-generation and execution fees within the rollup.

📈

Value Accrual

Fee flows establish a direct pathway for capturing and accruing protocol value to the token.

Privacy Built Into the Settlement Layer

ZKHood protects sensitive financial information across the transaction lifecycle. A TEE executes privately while a zero-knowledge proof settles each batch — proving correctness without exposing the underlying values.

Trusted Execution Environment

Transactions run inside isolated hardware, hidden from the host and the public chain.

REVM Execution

A super-light Rust EVM executes contracts at silicon speed inside the enclave.

Zero-Knowledge Proofs

Each batch is finalized with a succinct proof, verified onchain without revealing data.

Remote Attestation

Intel-signed certificates prove a genuine REVM is running inside a real TEE.

Native Token Access

Staking unlocks the TEE + ZK layer and pays for proof generation.

Built on Robinhood Chain

Final settlement is anchored to the Robinhood Chain, which verifies every proof.

Make Onchain Strategies Private.

ZKHood brings confidential, in-enclave execution and zero-knowledge settlement to tokenized stocks on the Robinhood Chain.

Explore ZKHood Read the Docs

Frequently Asked Questions

Clear answers to the most common questions about ZKHood.

How does ZKHood keep strategies private? +

Execution happens inside a Trusted Execution Environment (TEE) on a Layer 3 rollup. Your transaction is decrypted and run in sealed hardware memory, so balances, amounts, and strategy stay private — then only a zero-knowledge proof of the batch is published onchain.

What is a TEE? +

A Trusted Execution Environment is an isolated region of a CPU (Intel SGX / TDX or AMD SEV) that runs code and data invisibly to the host machine, with hardware guarantees of integrity and confidentiality.

How do TEE and ZK work together? +

ZKHood is a hybrid rollup. The TEE executes your strategy instantly and privately (Stage 1); then a zero-knowledge proof of the batch settles on the Robinhood Chain (Stage 2). The TEE gives speed and confidentiality, while ZK gives trustless, hardware-independent finality.

What is remote attestation? +

When the REVM boots inside the enclave it generates an internal key and an Intel-signed certificate proving that this exact public key belongs to a genuine REVM running in a real TEE. The Robinhood Chain contract only accepts batches signed by that attested key.

How does the enclave know the chain state? +

A Helios light client runs alongside the REVM inside the enclave. It downloads only block headers and verifies the balances it needs via Merkle proofs — no 1TB node required inside protected memory.

Is ZKHood a wallet? +

No. ZKHood is hybrid TEE + ZK rollup infrastructure for tokenized stocks. You connect through compatible wallets over an attested TLS channel while the rollup handles private execution and ZK-proven settlement.