Dusk

Dusk Trade waitlist is now open. Our regulated RWA trading platform, built with NPEX, a licensed exchange with €300M AUM, bringing tokenized assets and funds on-chain. Sign up for a chance to win up to $500 in RWAs 👇

What "hardening the network" looks like: - Node and networking security. - Key management across the stack. - Execution safety, memory integrity, fee handling, signature authentication. - Adversarial stress testing. In an AI-accelerated world, regulated finance needs a strong and secure foundation.

There’s a massive opportunity right now for whoever builds the first truly optimized native DEX on @DuskFoundation . When you start digging into the capabilities of Moonlight smart contracts, the architecture practically writes itself. You could design a constant-product AMM where the Pair contracts natively handle their own LP token balances, drastically cutting down on unnecessary Inter-Contract Calls to save on fees. Pair that infrastructure with the DRC-20 standard, specifically utilizing off-chain BLS signature permits, and you solve DeFi’s biggest UX problem: token approvals. Swapping becomes a seamless, single-click, gasless experience for the end user. The building blocks for next-generation UX are sitting right in front of us. Who knows, maybe one day Noctis Wallet will natively integrate an exchange that uses this exact architecture... 🦉✨

@Eterna_Markets @Eterna_Hybrid Thanks for the listing!

New Listing on Eterna Exchange @DuskFoundation is now live on @Eterna_Hybrid. Pair: DUSK/USDT Min/Max Order: 1 / 900,000 Min Value: $5 Maximum Leverage: 12.5x Trade here: ehx.app/t/DUSK Eterna - Trust the Signal.

@desire4changes Only a matter of time.

@DuskFoundation Hope liquidity of tokenized RWAs gets deep enough that they start replacing stablecoins in real trading flows.

Read more about Dusk's privacy features here ↓ #privacy-by-design-transparent-when-needed" target="_blank" rel="nofollow noopener">docs.dusk.network/learn/overview…

Blockchains proved they can handle real economic volume. Now the bottleneck is that you can't move serious cashflow on a system where every competitor can see your books. Dusk treats privacy as a prerequisite for institutional adoption.

Every few weeks another protocol has a bridge exploit, a front-end compromise, or an oracle attack. That doesn't work when the goal is to bring regulated financial markets on-chain. That's why we're hardening every layer of Dusk before scaling. Not after.

The ECB's Appia roadmap. The EU DLT Pilot Regime going live. €1.7 billion in tokenized bonds issued in Europe in 2024 alone. BlackRock's BUIDL crossing $4 billion. Over 60% of asset managers planning to launch tokenized funds. The direction is clear. What Europe needs now is blockchain infrastructure that handles the full asset lifecycle on-chain with built-in privacy and compliance. That's what Dusk was built for.

This week our integration with @pieswap_dusk went live! This means iPhone users can now stake $DUSK with just a few taps. Whether you're on Android or iOS, seamless staking is now at your fingertips.

The AEGIS Security Analysis is one of the most detailed reports we've published. Every critical finding, how it could have been exploited, and what changed. Full analysis below ↓

The Aegis hard fork is the biggest protocol-level change we've shipped since $DUSK mainnet. Deep Rusk hardening, with multiple bug and vulnerability fixes. Our toughest upgrade to ship so far due to the multiple layers of change, but a major step forward for protocol resilience and security.

Read the technical breakdown below ↓ dusk.network/news/aegis-sec…

AEGIS was the most significant protocol upgrade since mainnet launch. 7 critical findings across 4 root causes. 39 total fixes shipped across execution safety, memory integrity, fee handling, and signature authentication. We've published the full technical breakdown. ↓

Two ways(at least) to build a wallet on Dusk. Same Rust core under the hood, different paths to get there. The official toolkit for web is w3sper.js. It compiles Dusk’s Rust wallet core to WebAssembly and wraps it in a JavaScript SDK. That makes it ideal for browser environments: extensions, web wallets, and dApps. Developers can call high-level functions like transfer() or sync() from JavaScript while the cryptography runs inside WASM in the browser sandbox. It’s a very clean developer experience and works anywhere JavaScript runs. Noctis takes a different route. Instead of compiling the wallet core to WebAssembly, the Rust code is compiled directly to native machine code (ARM / x86) and exposed as a shared library. A C FFI interface defines the boundary, a JNI bridge connects it to Kotlin(In case of Android app), and the app calls those functions directly. When Noctis scans notes or builds a Phoenix transaction, it’s executing native Rust code on the device CPU. Why choose that approach? Performance WebAssembly is very fast for web environments. Native execution simply removes another runtime layer, which can help when processing large batches of encrypted notes during shielded sync. Memory control Running the wallet core natively allows explicit control over how sensitive data is handled in memory. For example, seed material can be wiped immediately after use using explicit zeroization routines. In managed runtimes like JavaScript, memory lifecycle is typically controlled by garbage collection, which changes how that type of control is implemented. Platform integration Native mobile apps can integrate directly with operating system security features such as Android Keystore, biometric authentication, and OS-level protections like screenshot blocking. These capabilities are part of the mobile platform itself rather than something accessed through a browser environment. The tradeoff The native route is more complex to build and maintain. It requires defining FFI interfaces, writing bridge code, managing memory boundaries between languages, and maintaining compatibility across platforms. Tooling like w3sper significantly reduces that complexity for web-based applications. So which approach is better? Neither, they serve different environments. w3sper is a natural fit for web applications and browser wallets. A native Rust integration makes sense when building a mobile-first wallet that needs deep OS integration and full control over the runtime environment. Noctis chose the native route because a phone wallet operates in a very different environment than a browser wallet, and that environment benefits from an architecture designed specifically for it.

@pieswap_dusk @gnosispay @sozu_dusk Moonpie is moving quickly. Wallet, staking, and now a Apple Pay payments. Amazing work! 👏

🥧 Moonpie gets a Visa card 💳 Self-custodial. Apple Pay. Powered by @gnosispay. • top up with $DUSK • pay anywhere Visa is accepted • tap to pay with Apple Pay One app. Piewallet, staking via @sozu_dusk, bank, and now a debit card. Be prepared for the next update 👀

Europe's financial markets are moving on-chain. The ECB just published the roadmap that defines what's needed. Their Appia roadmap calls for the full lifecycle of a financial asset to live on a single DLT platform. Issuance, trading, settlement, custody, servicing. All on-chain. That eliminates off-chain ledgers with tokenized layers on top. It eliminates platforms that handle one step while the rest runs through intermediaries. This covers regulated financial institutions handling large-scale transactions. EU law requires these transactions to stay confidential. You can't settle securities on a chain where every competitor can see what you're buying, selling, and for how much. Dusk was built for this. Native issuance and settlement on-chain, confidential transactions with selective disclosure, compliance built into the protocol.

@pieswap_dusk @sozu_dusk Pieswap is cooking! 👏🔥

Moonpie just dropped 🥧📱 monitor your node. use Piewallet. stake $DUSK via @sozu_dusk. explore the blockchain. all from your phone. built for the @DuskFoundation ecosystem. 🔗 apps.apple.com/app/moonpie/id…