Why Notional?
Notional combines the speed of centralized exchanges with the security of DeFi through hardware-based security (Trusted Execution Environments).What You Get:
- Sub-10ms execution - Hyperliquid-level speed with added margin
- No front-running - Orders stay private until execution (hardware-encrypted memory)
- Full transparency - All trades recorded on immutable blockchain, independently verifiable
Speed
5,000 TPS capacity with <10ms added latency over direct Hyperliquid access
Finality
Optimistic updates for instant feedback + blockchain settlement for security
How It Works
Notional runs inside a Trusted Execution Environment (TEE) - hardware that encrypts all memory and computation. Think of it as a black box that:- Executes trades at exchange-level speeds
- Keeps your orders private until execution (no front-running)
- Proves it’s running legitimate code via cryptographic attestation
- Cannot be tampered with by the host, cloud provider, or even Notional operators
Security Model
Trusted Execution Environment (TEE)
A TEE is a secure area of a processor that provides:- Hardware-encrypted memory - CPU encrypts RAM contents, host cannot read
- Isolated execution - Cloud provider (Azure) cannot inspect or modify the TEE
- Remote attestation - Cryptographic proof the system is running unmodified code
- Secure key management - Trading keys released only to verified TEEs
Speed vs Security Tradeoff
Notional uses a dual finality model that balances instant feedback with blockchain security: Optimistic Layer (Instant):- Unconfirmed fills applied immediately for <10ms responsiveness
- Updates positions and PnL in real-time
- Never affects withdrawable balances - can’t withdraw based on unconfirmed fills
- Reconciled against blockchain within ~1 second
- All Hyperliquid events (fills, deposits, withdrawals) confirmed on-chain
- Withdrawals only use blockchain-confirmed balances
- Internal operations (borrows, liquidations) finalize on commit
Transparency & Verification
Immutable Event Log: Every state change is recorded with:- Global sequence number (total ordering)
- Timestamp and event type
- Full event payload
- Hash chain linking to previous events
- Download the transaction log
- Replay all events from genesis
- Verify the reported state matches your computation
- Check TEE attestation to confirm hardware security
For a deeper technical dive, see Protocol Risks for threat model analysis and security boundaries.