#nil $NIL @Nillion
Nillion Covenants: Keep the Trade Secret Until It Matters
The market doesn’t need to see your order to use it against you. Sometimes, knowing what an instruction is waiting for is enough to trade ahead of it.
Nillion Covenants aim to close that window by encrypting instructions until a predefined condition permits disclosure. Dusk is the first phase of that approach.
How the Mechanism Works
Instead of trusting a single custodian, an author selects a committee and sets a reconstruction threshold. Encrypted shares are distributed across nodes.
Once the condition is met, nodes release their shares. When enough arrive, the instruction is reconstructed and checked against its original commitment. A connected contract can then execute the intended action.
Why Traders Should Care
Imagine a conditional sell order whose size remains hidden until its trigger fires.
Outsiders may see that a Covenant exists, but they cannot simply read the full instruction while it waits.
The benefit isn’t invisibility. It’s control over when sensitive information becomes public.
Where Privacy Ends
Covenants do not conceal every trace. Some metadata stays visible, and the instruction becomes public after release.
A sufficiently coordinated committee could also reconstruct it prematurely. Committee composition and share thresholds are therefore security decisions, not minor settings.
What Comes Next
Nillion’s seven-phase roadmap points toward more flexible release conditions, conditions concealed from evaluating nodes, and cheaper operation.
Those are future goals, not features to assume are live today.
What I would measure is straightforward: Does confidentiality hold while the instruction waits? Is release dependable? Are costs reasonable enough for actual trading workflows?
Privacy can stop information from leaking too soon. It cannot fix poor execution, bad risk management, or a weak strategy.
Nillion Covenants: Keep the Trade Secret Until It Matters
The market doesn’t need to see your order to use it against you. Sometimes, knowing what an instruction is waiting for is enough to trade ahead of it.
Nillion Covenants aim to close that window by encrypting instructions until a predefined condition permits disclosure. Dusk is the first phase of that approach.
How the Mechanism Works
Instead of trusting a single custodian, an author selects a committee and sets a reconstruction threshold. Encrypted shares are distributed across nodes.
Once the condition is met, nodes release their shares. When enough arrive, the instruction is reconstructed and checked against its original commitment. A connected contract can then execute the intended action.
Why Traders Should Care
Imagine a conditional sell order whose size remains hidden until its trigger fires.
Outsiders may see that a Covenant exists, but they cannot simply read the full instruction while it waits.
The benefit isn’t invisibility. It’s control over when sensitive information becomes public.
Where Privacy Ends
Covenants do not conceal every trace. Some metadata stays visible, and the instruction becomes public after release.
A sufficiently coordinated committee could also reconstruct it prematurely. Committee composition and share thresholds are therefore security decisions, not minor settings.
What Comes Next
Nillion’s seven-phase roadmap points toward more flexible release conditions, conditions concealed from evaluating nodes, and cheaper operation.
Those are future goals, not features to assume are live today.
What I would measure is straightforward: Does confidentiality hold while the instruction waits? Is release dependable? Are costs reasonable enough for actual trading workflows?
Privacy can stop information from leaking too soon. It cannot fix poor execution, bad risk management, or a weak strategy.