Every stop-loss you’ve ever set is a public confession.
Open the liquidation map for any perpetual contract, and you’ll see thousands of people’s exit prices laid out in the open, hours in advance. Nobody leaked anything—the chain is transparent by design. That’s why stop-losses get hunted, and why large orders always move against the people placing them.
@Nillion ’s Covenants tackle this problem from a different angle. A Covenant is an instruction that “no one can read before it’s triggered”: you seal it to a particular condition and send it to the chain, encrypted from start to finish. As soon as the condition becomes true, it opens automatically. No bots to maintain, no keeper, and no third party holding your order and promising not to peek.
My take: the cleverest part isn’t the encryption—it’s eliminating the role of “who decides when to execute.” Releasing it becomes a bounty that anyone can win by contributing enough shares, while the sealed content must match an on-chain commitment. There’s nothing to gain by forging one. Trust shifts from a person to a verifiable committee threshold, and I like that.
But let’s be clear about the downside: the existence of a Covenant, the identity of the committee, and the amount of the bounty in custody are still public. What’s hidden is the content, not the footprint. That’s why how decentralized the node network eventually becomes matters more than any slogan.
Nillion’s Dusk phase is now live on Ethereum mainnet. This is a full launch, not a testnet. Anyone can create a Covenant, operate a node, or build with the SDK today. It’s also just the first of seven eras in the roadmap, with a deliberately narrow scope: conditions are based on price or time, because those are what can work today without a trusted party. Stop-losses that can’t be hunted, bids that stay sealed until an auction ends, and payments that release automatically at a specified time—all fall within that scope.
In the next few eras, I’ll be watching two things: whether conditions can expand beyond price and time, and just how widely distributed the operators staking $NIL ultimately become.
#nil $NIL @Nillion
What’s the first “if…then…” instruction you’d seal?
Open the liquidation map for any perpetual contract, and you’ll see thousands of people’s exit prices laid out in the open, hours in advance. Nobody leaked anything—the chain is transparent by design. That’s why stop-losses get hunted, and why large orders always move against the people placing them.
@Nillion ’s Covenants tackle this problem from a different angle. A Covenant is an instruction that “no one can read before it’s triggered”: you seal it to a particular condition and send it to the chain, encrypted from start to finish. As soon as the condition becomes true, it opens automatically. No bots to maintain, no keeper, and no third party holding your order and promising not to peek.
My take: the cleverest part isn’t the encryption—it’s eliminating the role of “who decides when to execute.” Releasing it becomes a bounty that anyone can win by contributing enough shares, while the sealed content must match an on-chain commitment. There’s nothing to gain by forging one. Trust shifts from a person to a verifiable committee threshold, and I like that.
But let’s be clear about the downside: the existence of a Covenant, the identity of the committee, and the amount of the bounty in custody are still public. What’s hidden is the content, not the footprint. That’s why how decentralized the node network eventually becomes matters more than any slogan.
Nillion’s Dusk phase is now live on Ethereum mainnet. This is a full launch, not a testnet. Anyone can create a Covenant, operate a node, or build with the SDK today. It’s also just the first of seven eras in the roadmap, with a deliberately narrow scope: conditions are based on price or time, because those are what can work today without a trusted party. Stop-losses that can’t be hunted, bids that stay sealed until an auction ends, and payments that release automatically at a specified time—all fall within that scope.
In the next few eras, I’ll be watching two things: whether conditions can expand beyond price and time, and just how widely distributed the operators staking $NIL ultimately become.
#nil $NIL @Nillion
What’s the first “if…then…” instruction you’d seal?