On-chain applications sometimes need secrets that unlock later—think embargoed reports, delayed governance votes, or scheduled disclosures. Nillion tackles this with threshold cryptography designed for conditional release on Ethereum.
Covenants is Nillion's core product: you seal a payload, which gets split into Shamir shares across a node committee. Fewer than the chosen threshold k shares cannot reconstruct the original data. Under intended honest-node operation, when a preset release condition is met—say, a specific time passes—nodes holding at least k shares reconstruct the payload. Important caveat: a coalition of k or more nodes could technically reconstruct early, so security depends on committee integrity and the selected threshold. Timing metadata also stays public throughout.
Dusk is Covenants' first release phase (not a separate token). It is the foundation roadmap phase establishing cryptographic primitives, the node network, and developer tooling on Ethereum, with Sepolia testnet confirmed live. Not every Dusk milestone should be assumed complete; later phases like multichain expansion also remain roadmap plans.
Hypothetical example: imagine a research DAO that seals a quarterly treasury report via Covenants, set to unlock at a fixed future time. Until then, fewer than the chosen k shares cannot reconstruct the report—but if k or more nodes collude, early reconstruction is possible. After the time condition triggers honest reconstruction, the document becomes permanently public.
Practical takeaway for builders: Dusk provides foundational conditional-release infrastructure on Ethereum, but understanding its trust model—choosing threshold k carefully, acknowledging public metadata, the k-collusion risk, and that disclosure does not equal any trade execution guarantee—is essential before integrating.
#nil $NIL @Nillion
Covenants is Nillion's core product: you seal a payload, which gets split into Shamir shares across a node committee. Fewer than the chosen threshold k shares cannot reconstruct the original data. Under intended honest-node operation, when a preset release condition is met—say, a specific time passes—nodes holding at least k shares reconstruct the payload. Important caveat: a coalition of k or more nodes could technically reconstruct early, so security depends on committee integrity and the selected threshold. Timing metadata also stays public throughout.
Dusk is Covenants' first release phase (not a separate token). It is the foundation roadmap phase establishing cryptographic primitives, the node network, and developer tooling on Ethereum, with Sepolia testnet confirmed live. Not every Dusk milestone should be assumed complete; later phases like multichain expansion also remain roadmap plans.
Hypothetical example: imagine a research DAO that seals a quarterly treasury report via Covenants, set to unlock at a fixed future time. Until then, fewer than the chosen k shares cannot reconstruct the report—but if k or more nodes collude, early reconstruction is possible. After the time condition triggers honest reconstruction, the document becomes permanently public.
Practical takeaway for builders: Dusk provides foundational conditional-release infrastructure on Ethereum, but understanding its trust model—choosing threshold k carefully, acknowledging public metadata, the k-collusion risk, and that disclosure does not equal any trade execution guarantee—is essential before integrating.
#nil $NIL @Nillion