Binance Square
Aina-
11.4k Publications

Aina-

🖤👈🏻
44 Suivis
1.0K+ Abonnés
3.6K+ J’aime
Publications
PINNED
·
--
Vérifié
‎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 👍 ‎ #dusk $DUSK @Dusk_Foundation
‎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 👍
‎

#dusk

$DUSK

@Dusk
PINNED
·
--
‎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? ‎ #dusk $DUSK @Dusk_Foundation
‎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?
‎

#dusk

$DUSK

@Dusk
·
--
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. @nillionnetwork 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 @nillionnetwork
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
Darkfall
Skyglow
Non-EVM
Both together
17 heure(s) restante(s)
·
--
🌸
🌸
Hoorain_X
·
--
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
·
--
🎙️ 🚀 PROM 深度解析|探索 Binance 生态新机会
avatar
Fin
02 h 34 min 05 sec
6.2k
16
14
·
--
🎙️ 币圈行情交流;新人问题解答✅共建币安广场🦅传播自由理念!维护生态平衡!
cover
Fin
03 h 13 min 42 sec
10.1k
28
75
·
--
🎙️ CZ Binance Founder: This Crypto Bull Run Could Make You Rich
avatar
Fin
03 h 23 min 56 sec
5k
8
3
·
--
🎙️ PROM × 币安生态权益专题直播
cover
Fin
02 h 01 min 00 sec
6.3k
18
12
·
--
🎙️ 建设币安广场,关注 BTC ETH BNB SOL 主流价值货币🚀🚀🚀🚀
cover
Fin
02 h 31 min 21 sec
3.1k
15
17
·
--
🎙️ 币圈行情交流;新人问题解答✅共建币安广场🦅传播自由理念!维护生态平衡!
cover
Fin
03 h 14 min 25 sec
9.6k
33
74
·
--
🎙️ تعلم التداول مع البركه
avatar
Fin
06 h 00 min 00 sec
3.9k
15
10
·
--
🎙️ 晚上好⁶⁶⁶,没事儿进来睡觉。
cover
Fin
03 h 20 min 47 sec
2.1k
1
0
·
--
🎙️ 实盘交易、定投BNB
avatar
Fin
01 h 35 min 26 sec
3.2k
8
8
·
--
wOw❤❤❤👈🏻
wOw❤❤❤👈🏻
Votre contenu coté a été supprimé
·
--
🎙️ /PROM 代币介绍/币安生态权益详解
cover
Fin
02 h 11 min 57 sec
4.9k
27
41
·
--
🎙️ Crypto Market Scenarios
avatar
Fin
02 h 16 min 17 sec
491
5
5
·
--
🎙️ 建设币安广场,坚持💪🏻定投 BTC ETH BNB SOL 主流价值货币🚀🚀🚀
cover
Fin
02 h 36 min 01 sec
2.5k
6
13
·
--
🎙️ 币圈行情交流;新人问题解答✅共建币安广场🦅传播自由理念!维护生态平衡!
cover
Fin
03 h 15 min 12 sec
8.7k
32
83
·
--
🎙️ 让我们一起看看周五市场行情热不热烈
avatar
Fin
01 h 32 min 03 sec
140
1
0
·
--
🎙️ 建设广场,MUA空投继续,来来!
cover
Fin
04 h 10 min 57 sec
3.4k
17
23
Connectez-vous pour découvrir plus de contenu
Rejoignez la communauté mondiale des adeptes de cryptomonnaies sur Binance Square
⚡️ Suviez les dernières informations importantes sur les cryptomonnaies.
💬 Jugé digne de confiance par la plus grande plateforme d’échange de cryptomonnaies au monde.
👍 Découvrez les connaissances que partagent les créateurs vérifiés.
Adresse e-mail/Nº de téléphone
Plan du site
Préférences de cookies
CGU de la plateforme