#nil $NIL @Nillion Most privacy tools hide data while you compute on it. Dusk does something narrower and, for markets, more useful: it lets you post an instruction that stays unreadable until a condition is true.
You write something like “buy $50k of ETH if BTC hits $80k,” seal it, and put it on Ethereum. Anyone can see that a Covenant exists. Nobody can read the size, the asset, or the exact trigger. Not other traders, not searchers, not the nodes. The payload is split across a committee. Any single node only holds a useless piece. When a live data feed shows the condition is met, enough nodes publish their shares, the instruction reconstructs on-chain, and it can settle. No keeper sits in the middle deciding whether to open it.
Before:
👉Watch for BTC to hit $80k
👉Then submit the ETH trade
👉The trade sits visible before it fills
With Covenants:
👉Write the ETH trade in advance
👉Seal it to BTC hitting $80k
👉It fires on its own and stays sealed until then
Two details matter more than the pitch. Small orders are easy to guess, so a nonce is added before the commitment; without it, “sell 100 ETH” could be brute-forced. And once you post, you cannot cancel. If the condition never arrives, the instruction simply expires still sealed. That removes the usual leak where cancelling itself tells the market what you wanted.
For a new user, the practical version is simple: you can leave a trade, a bid, or a payment on-chain without advertising your intent while you wait. Agents can do the same without showing their hand.
On $NIL , the old L2 story is ending. Node operators now stake on Ethereum and earn from the Covenants that actually get posted. If Dusk stays a demo, the token is just another staking asset. If people start sealing real orders because they are tired of being front-run, then NIL becomes the bond that keeps those sealed instructions honest.
That is the only demand that feels durable to me.
You write something like “buy $50k of ETH if BTC hits $80k,” seal it, and put it on Ethereum. Anyone can see that a Covenant exists. Nobody can read the size, the asset, or the exact trigger. Not other traders, not searchers, not the nodes. The payload is split across a committee. Any single node only holds a useless piece. When a live data feed shows the condition is met, enough nodes publish their shares, the instruction reconstructs on-chain, and it can settle. No keeper sits in the middle deciding whether to open it.
Before:
👉Watch for BTC to hit $80k
👉Then submit the ETH trade
👉The trade sits visible before it fills
With Covenants:
👉Write the ETH trade in advance
👉Seal it to BTC hitting $80k
👉It fires on its own and stays sealed until then
Two details matter more than the pitch. Small orders are easy to guess, so a nonce is added before the commitment; without it, “sell 100 ETH” could be brute-forced. And once you post, you cannot cancel. If the condition never arrives, the instruction simply expires still sealed. That removes the usual leak where cancelling itself tells the market what you wanted.
For a new user, the practical version is simple: you can leave a trade, a bid, or a payment on-chain without advertising your intent while you wait. Agents can do the same without showing their hand.
On $NIL , the old L2 story is ending. Node operators now stake on Ethereum and earn from the Covenants that actually get posted. If Dusk stays a demo, the token is just another staking asset. If people start sealing real orders because they are tired of being front-run, then NIL becomes the bond that keeps those sealed instructions honest.
That is the only demand that feels durable to me.