I came across Dusk's own October 2025 update recently and something about the internal naming kept nagging at me. What we now know as Dusk Trade started life under a completely different, internal codename — alongside DuskEVM and a regulatory exemption called DLT-TSS, pursued with NPEX and legal advisors Norton Rose Fulbright, specifically for native on-chain issuance. What seems interesting is that same October update explicitly describes STOX as complementary to, but distinct from, the NPEX work — meaning Dusk was building two separate regulated-trading efforts in parallel, not one project under two names. Looking from the outside, that internal-to-public rename tracks with something specific: Dusk's own update states STOX would launch with a few carefully selected partners first, then expand — a staged rollout timeline that matches roughly when Dusk Trade's public waitlist actually opened. It makes me think the deeper question isn't "what was STOX called before" — it's that tracking exactly when an internal codename becomes a public-facing product name is often the clearest signal of when something moved from internal build-phase to actual external rollout, more reliable than any announcement date alone. Anyway, time will tell 👍
Spent the afternoon digging into what Piecrust actually changes versus plain WASM, figuring it'd mostly be cosmetic. It isn't. Piecrust replaced the old RuskVM, and it's built around Wasmer, a WASM runtime — but Dusk's own materials say it's fundamentally different in two specific ways: it natively supports ZK operations like SNARK verification right inside the VM, and it handles memory in a completely different way than most blockchain VMs bother with. That's the part that stuck with me. You give up the simplicity of a plain, off-the-shelf WASM runtime, and in exchange you get a VM that can natively verify zero-knowledge proofs without routing that work somewhere else entirely. But hold on, let me be honest about what I actually know versus what I'm guessing. Dusk confirms Piecrust handles memory differently and does ZK natively. What I couldn't find anywhere is an actual measurable performance-delta between old RuskVM and current Piecrust. Kept coming back to why this matters beyond the technical description — a VM built to natively handle the exact cryptographic work Dusk's whole privacy model runs on isn't some generic pick retrofitted after the fact. So does building a VM this specialized actually pay off long-term, or does it just make things harder to extend later once requirements shift?
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
went into @Nillion 's Encrypted Markets thinking trading privacy was mostly about people seeing your wallet activity. Then I started looking at Covenants and realised there's another problem hiding in plain sight.
Your strategy can be exposed before your trade even happens.
Think about it.
When you place an order, others see ur entry price or liquidation level. They don't need to know who you are to understand your plan. Once they see it, they can react before your trade goes through.
Here's where Covenants get interesting.
Instead of publishing an instruction in readable form, you seal it to a predefined condition. The encrypted instruction stays unreadable while Nillion's node network waits for that condition. When it triggers, nodes release the necessary cryptographic shares, allowing the instruction to be reconstructed and resolved on Ethereum.
Your strategy can be prepared in advance without broadcasting its details to everyone watching the chain.
Hmm. The part I keep coming back to is that this isn't simply about hiding a transaction. It's about changing what other market participants can learn before execution.
Imagine setting a conditional ETH buy without exposing your intended entry beforehand, or preparing a stop-loss that stays sealed until its trigger arrives.
Of course, confidentiality doesn't guarantee better execution, eliminate every form of MEV, or prevent every implementation flaw. The conditions and execution mechanism still matter.
But the idea is worth paying attention to.
We've spent years making financial activity transparent enough to verify, sometimes at the cost of revealing strategies traders would rather keep private.
so what do you like most about covenants??? #NIL $NIL