A private instruction that only works on one chain is useful, but limited. That's the gap I want Nillion to close after Dusk's Ethereum mainnet launch on 28 September.
Here's how Covenants work today. You attach an instruction to a condition, it stays encrypted while it waits, and it opens when that condition is met. Good start, but it's stuck on one chain.
That's why Darkfall and Skyglow caught my eye on Nillion's seven-phase roadmap.
Darkfall is scheduled for November 2026 to February 2027. The idea is to bring everything Dusk does to multiple EVM chains through one network, with chain-specific nodes and tooling so operators and developers can work natively on each chain. @Nillion
Skyglow goes a step further. The roadmap describes a condition being verified on one chain while the instruction settles on another, with cryptographic proofs checking the reveal. It also targets support beyond EVM chains. #NIL
What I care about most is simple: the released action should follow its condition without adding a new party to trust. Connecting chains is the easy part. Holding that guarantee through the handoff is the tricky bit, and I suspect it's where most cross-chain designs struggle. Get it right and private instructions stop feeling so niche.
To be clear, Darkfall and Skyglow are roadmap goals, not live features.
Which roadmap step should Nillion deliver first? $NIL
#nil $NIL @Nillion
Here's how Covenants work today. You attach an instruction to a condition, it stays encrypted while it waits, and it opens when that condition is met. Good start, but it's stuck on one chain.
That's why Darkfall and Skyglow caught my eye on Nillion's seven-phase roadmap.
Darkfall is scheduled for November 2026 to February 2027. The idea is to bring everything Dusk does to multiple EVM chains through one network, with chain-specific nodes and tooling so operators and developers can work natively on each chain. @Nillion
Skyglow goes a step further. The roadmap describes a condition being verified on one chain while the instruction settles on another, with cryptographic proofs checking the reveal. It also targets support beyond EVM chains. #NIL
What I care about most is simple: the released action should follow its condition without adding a new party to trust. Connecting chains is the easy part. Holding that guarantee through the handoff is the tricky bit, and I suspect it's where most cross-chain designs struggle. Get it right and private instructions stop feeling so niche.
To be clear, Darkfall and Skyglow are roadmap goals, not live features.
Which roadmap step should Nillion deliver first? $NIL
#nil $NIL @Nillion
Darkfall
Skyglow
Non-EVM
Both together
14 heure(s) restante(s)