Inco brings confidentiality to Base

Inco announced on June 15 that Inco Lightning is now live on Base mainnet. The core fact is straightforward: developers can add encrypted data and confidential operations to existing Solidity contracts without deploying to a new chain or learning a new language. The announcement follows an April 2025 release on the Base Sepolia testnet and says the system was audited by Trail of Bits before moving into production.

The point is larger than another developer library. Public blockchains are valuable because their execution can be checked, but they also make balances, strategies, votes, and commercial parameters too easy to inspect. Many financial and institutional applications need a middle ground: keep the verifiable execution of a smart contract while limiting what every observer can read. Inco presents Lightning as that confidentiality layer for EVM-compatible chains, meaning environments that run contracts in the Ethereum style. That framing matters because privacy is often treated as a separate network or a special-purpose application, while this launch tries to place it inside a familiar developer workflow.

The technical entry point is intentionally ordinary: a Solidity import exposes encrypted types such as euint256, ebool, and eaddress. Those types can represent amounts, booleans, or addresses without revealing their plain values. The announcement also lists computation over encrypted data, comparisons, bitwise logic, verifiable randomness for games or auctions, and programmable access control to define who may view which data. When information needs to be revealed, Inco describes a decryption layer based on a quorum of TEE nodes, isolated execution environments whose state can be attested. The JavaScript SDK then handles client-side encryption, key management, signing, and local decryption for frontends.

What changes in practice is the granularity of onchain privacy. A protocol could design a vote where choices stay private until tallying, a game where cards are not publicly visible, or a lending flow where a threshold score is proven without exposing the full score. It could also support selective disclosure for compliance, where a counterparty sees enough proof to act without receiving a full data dump. Caution still matters: confidentiality introduces its own trust surface, including cryptographic assumptions, decryption nodes, and access rules. But mainnet availability on Base gives developers a real venue to test those trade-offs beyond testnet demonstrations, with the costs, tooling constraints, and user expectations of a production chain.