Shush Protocol adds Zama fhEVM support
- Excubia Labs said on May 22 that Shush Protocol v1.12.0 added Zama fhEVM support for encrypted strategy parameters and on-chain evaluation. (excubialabs.com) - Zama’s FHEVM lets users encrypt inputs client-side and compute on ciphertext on EVM chains, with a coprocessor handling FHE execution services. (docs.zama.org) - Excubia’s documentation says Shush agents use encrypted registration and decryption flows, with guides and protocol materials published on its documentation site. (excubialabs.com)
1/ Excubia Labs said Shush Protocol v1.12.0 now uses Zama’s fhEVM stack so users can encrypt trading-strategy inputs before they ever reach the chain. The change is aimed at a specific on-chain problem: strategy logic is often visible in public mempools and contract state, while FHEVM is designed to let contracts compute on encrypted values without decrypting them on-chain. (excubialabs.com) 2/ In plain terms, the update moves sensitive parameters — such as thresholds, stop-loss levels and take-profit levels — into ciphertext at the client layer. (docs.zama.org) Zama’s documentation says encrypted inputs are a core FHEVM feature, and that users encrypt plaintext locally, generate the associated proof material, and then submit those encrypted values for contract use. (excubialabs.com) 3/ That matters because Shush is built around private on-chain trading. Excubia describes the protocol as a “fully confidential execution layer for on-chain trading,” and its public docs say agent creation includes generating keys, encrypting and registering an agent, and later handling decryption through defined flows. (excubialabs.com) 4/ The Zama piece is not just encryption at input. Zama’s FHEVM documentation says the coprocessor provides the execution service for FHE computations and includes services for compute, input verification and transaction sending. In practice, that is the machinery Shush is pointing to when it says encrypted strategy values can still be evaluated into actions such as BUY, SELL or HOLD without exposing the underlying plaintext. (docs.zama.org) 5/ The architectural point is that the contract logic can stay EVM-native while the sensitive values stay hidden. Zama’s GitHub repository describes FHEVM as a framework for integrating fully homomorphic encryption with EVM-compatible blockchains, and OpenZeppelin’s integration guide says applications can encrypt inputs locally, read encrypted state and submit encrypted transactions through the Zama stack. (excubialabs.com) 6/ The cross-chain claim comes from how FHEVM is positioned. Zama says the protocol is a suite of tools and libraries for building confidential smart contracts and dApps on EVM-compatible chains, while Excubia’s note says the same contract and SDK path work across Ethereum and Base deployments. (docs.zama.org) That suggests developers are not rewriting the privacy model chain by chain; they are reusing the same encrypted-input pattern across supported EVM environments. That last point is an inference from the documented architecture and Excubia’s deployment description. 7/ The broader significance for builders is narrower than the marketing language: this is a pattern for hiding user-defined parameters while preserving on-chain automation. (github.com) Zama’s docs frame encrypted inputs, ACL-based decryption and relayer-based handling as standard parts of the workflow, and Excubia’s docs show Shush already has separate materials for encryption, key management, execution modes and decryption flows. 8/ What to watch next is whether Excubia publishes contract-level release notes, supported network details or code examples tied specifically to v1.12.0. As of May 22, Excubia’s documentation hub lists protocol, key-management and agent-creation guides, while Zama’s changelog tracks deployed and planned FHEVM versions on testnet and mainnet. (docs.zama.org) (excubialabs.com) (docs.zama.org)
