#nil $NIL @Nillion
The more I look into Nillion’s Encrypted Markets lately, the more I think there’s something to it—especially the Covenants part.

In the past, placing stop-losses or limit orders on-chain was basically like putting your plans on display. Once people saw what price you were waiting for, MEV and snipers would be right on your tail. Covenants takes a straightforward approach: encrypt your trading intent and seal it on-chain. Until the conditions are met, neither nodes nor the project team can read it. When the price or time condition is met, the nodes work together to unlock and execute it. It relies on threshold cryptography: the secret is split among a group of nodes and only reconstructed after enough of them confirm. No keeper, no single trusted party.

This is already beyond the white paper stage. Dusk has launched on Ethereum mainnet—that’s the first step. It’s not just private transfers; it brings conditional execution directly to L1. Sealed orders, conditional payments, and even Agent strategies can run on it. Nodes need to stake at least 70,000 NIL, with rewards coming from 0.5% annual inflation plus trigger fees. Developers can integrate it using the TypeScript SDK, while identity-based encryption handles the underlying cryptography so they don’t have to.

What I’m most optimistic about is its positioning as a privacy overlay that requires no migration. It stays on Ethereum, so composability remains intact; it simply encrypts the trading intent itself. Before, you either hid in the mempool or moved to an entirely different chain. Covenants takes the middle route.

Over the next seven eras, Darkfall and Skyglow are set to expand to multiple EVM chains and even enable observation on chain A with settlement on chain B. Nightside and Neon, meanwhile, will bring custom conditional logic and a dedicated contract language. All of this is still in the works, so it’s too early to count it as a win.

When people think of privacy in crypto, many think only of mixers. Nillion is working on privacy at the strategy layer. Keeping instructions private doesn’t mean every trigger condition is hidden, and it certainly won’t make money for you. But at least the plans you stayed up all night researching don’t have to become someone else’s free homework. The rules can be publicly verified; there’s no need to show your hand to the whole table ahead of time.