"Onchain does not have to mean public."
That's the core claim from @cifer_security's latest post, and here's exactly what it means in practice.
The Cifer SDK lets EVM apps encrypt data before it's ever written onchain. That order matters: encrypting first means the raw data never touches the chain unprotected, even for a moment. Once encrypted, decryption access is granted only to specific wallets the app chooses, not to anyone scanning the chain.
It's built for multiple chains, not one. Ethereum, Base, Avalanche, and Robinhood are named directly, with more chains supported beyond that list. This isn't a single-ecosystem tool, it's meant to plug into whichever EVM chain an app is already building on.
It's available right now, not announced for later. Installable directly via npm, meaning a developer can add this to a live project today rather than waiting on a release.
Put together, that's three facts working as one system: encryption happens before the data touches the chain, access is controlled at the wallet level after that, and it works across several major EVM chains at once. Onchain data doesn't have to trade transparency for privacy, this SDK is built specifically so it doesn't have to choose.
If you're building on any of these four chains and handling anything sensitive, this is already installable.