Live on SKALE Base - Encrypted Transactions (Phase 1) is available on SKALE Base Mainnet and Testnet.
What Are Encrypted Transactions?
BITE’s first phase hides theto address and data fields of transactions until after they execute. Once decrypted and executed, transaction details are visible on-chain like any other transaction.
The encryption protects during mempool and consensus—before finality. After execution, the transaction is part of the immutable blockchain record and fully visible.
How It Works
- Encrypt - Wallet encrypts the transaction payload using SKALE’s threshold public key
- Submit - Encrypted transaction is sent to the BITE precompile (magic address)
- Finalize - Consensus finalizes the encrypted transaction without seeing contents
- Decrypt - After finality, the validator committee runs threshold decryption
- Execute - Decrypted transaction executes in the EVM
MEV Resistance
MEV bots need visible transaction data to extract value. By encryptingto and data during mempool and consensus, BITE removes the information they rely on:
- No front-running - Transaction intent is hidden until execution
- No sandwich attacks - Bots cannot see incoming swaps
- No censorship - Validators cannot selectively filter based on content
Use Cases
Private Token Transfers
Encrypt ERC20 transfers to hide amounts and recipients:Confidential Contract Interactions
Keep function calls and parameters private:Private Voting
Encrypt votes to prevent bribery and coercion:NFT Mint Privacy
Hide metadata and mint details until reveal:Getting Started
- BITE API Reference - TypeScript SDK and JSON-RPC methods
- Encrypted Transactions Cookbook - Step-by-step tutorials
- Introduction - BITE Protocol overview
