Dusk

Privacy-preserving blockchain infrastructure for institutional-grade finance. $DUSK

[Dusk @DuskFoundation]

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 👇

[Dusk @DuskFoundation]

Web wallet: https://t.co/sOJOo6YeLm

Explorer: https://t.co/myHwqCyKwA

[Dusk @DuskFoundation]

The Web Wallet and Explorer have a new look.

Cleaner interfaces, smoother navigation, and a more polished experience across two of the core Dusk tools.

Try them below ↓

[Dusk @DuskFoundation]

For more info, the original Dusk and NPEX partnership announcement is available here:
https://t.co/1CjlfSrbnF

[Dusk @DuskFoundation]

Tokenized securities need more than a wrapper.

They need issuer controls, investor access, privacy, disclosure, and settlement designed around regulated market workflows.

The Dusk and NPEX partnership focuses on that layer of regulated-market infrastructure.

Read more ↓

[Dusk @DuskFoundation]

Programmable privacy matters because tokenized assets carry sensitive information.

A tokenized bond, fund, equity, or real-world asset has more going on than a balance moving between two addresses.

Before someone can buy, hold, transfer, settle, or report on that asset, the system may need to check:

- who the investor is
- whether they are eligible
- what rules apply to the asset
- what the issuer needs to know
- what a venue is allowed to process
- what information can be shown when review is required

On a fully public chain, too much of that can become visible to everyone.

Investor balances.
Transfer history.
Position data.
Issuer information.
Trading permissions.
Review activity.

That is a problem for regulated finance.

Programmable privacy lets financial apps enforce rules without exposing every detail in public.

For issuers, asset rules, access conditions, corporate actions, and disclosure requirements can be part of the asset logic.

For investors, balances, transfers, and positions do not need to be broadcast to the entire internet.

For venues and institutions, permissions, settlement, and review can happen without exposing the full operating picture.

For builders, privacy covers the rules, the data, and the user experience, not only the address holding the token.

Dusk handles this across three parts:

DuskDS provides settlement and data availability, with deterministic finality and native models for confidential and transparent transactions.

DuskEVM is the EVM-compatible path for financial applications, with $DUSK as the native gas token, and privacy using our EVM privacy-module Hedger.

DuskVM gives native Dusk contracts a Rust/WASM path for privacy-aware logic built directly for DuskDS.

Private transfers protect transaction data.

Private smart contracts can protect the rules and data inside the financial product.

For RWA tokenization, that is the difference between putting an asset onchain and making regulated finance work onchain.

[Dusk @DuskFoundation]

Privacy gets interesting when it becomes programmable.

Private transfers protect transaction data. RWA tokenization needs smart contracts with confidential state, eligibility checks, and selective disclosure.

$DUSK brings programmable privacy to financial applications.

[Dusk @DuskFoundation]

Staking APR is variable.

It changes with network rewards, active stake, pool activity, deposits and withdrawals, and any active campaign incentives.

Check the live Sozu dashboard before staking.

[Dusk @DuskFoundation]

Holding $DUSK and not staking yet?

Sozu, our partner, is currently showing 29.08% APR, boosted by its June airdrop campaign.

If you've been waiting to stake, this is a good moment to check out Sozu.

[Sozu @sozu_dusk]

This week saw a major boost to the platform's APR, driven by the June airdrops 🚀

We have also distributed over 3M rewards to all our users! 🏆

[Hein Dauven @HeinDauven]

This puts into perspective how early tokenization still is. The market opportunity is enormous.

And beyond tokenizing existing assets, there is an even bigger opportunity, namely making capital markets more efficient for companies raising capital and investors deploying it.

[Hein Dauven @HeinDauven]

During the review we did flag a separate low-level concern in Phoenix, but after tracing the full transaction path it turned out not to be exploitable.

We added extra regression test coverage so it cannot become an issue in the future.

[Dusk @DuskFoundation]

More context on the Zcash Orchard incident:
https://t.co/4kKSarhhsz

[zooko🛡🦓🦓🦓 ⓩ @zooko]

https://t.co/v7BiOdzU9E

[Dusk @DuskFoundation]

After the Zcash Orchard disclosure affecting $ZEC, Dusk ran a precautionary review.

Orchard uses Halo2 and Dusk uses its own PLONK implementation. We reviewed that proof-system risk class anyway and found no overlap.

We did not identify this class of issue on the Dusk network.

[Hein Dauven @HeinDauven]

This is terrible news for any protocol, and I feel for the $ZEC team given how top notch they are.

But given the complexity of what is being built in this industry, bugs like this are also bound to happen. Even if you audit often, even if you hire good firms, cryptography and blockchain infrastructure are unforgiving.

At @DuskFoundation we made a conscious decision to spend a large part of the first half of 2026 on hardening and heavily auditing our own network.

Far from sexy and it does not generate headlines. And sadly enough, no matter how big the network upgrade is, this kind of work is often not perceived as "delivering".

But it is exactly the work you want done before privacy blockchain infrastructure is trusted with large amounts of real value.

More broadly, I think the industry needs to spend less time rolling its own cryptography in isolation, and more time standardizing, reviewing and formally verifying the shared primitives we all end up relying on.

In an ideal world, we formally verify as much as possible up and down the stack.

[Dusk @DuskFoundation]

Earlier this month Dusk attended Fintech Meets the Regulators in Amsterdam.

The event brought fintech companies together with the Dutch Ministry of Finance, the Dutch Central Bank (DNB), and the Netherlands Authority for the Financial Markets (AFM).

@heindauven heard one theme repeatedly. Compliant use cases need privacy.

The next phase of financial infrastructure needs privacy that regulators, issuers, and markets can trust.

[Hein Dauven @HeinDauven]

It was great to hear so many industry players talk about the need for privacy in their compliant use-cases, proving once again that Dusk has been building the right solution from the start

[Dusk @DuskFoundation]

More on Dusk’s privacy stack for financial applications:
https://t.co/ckomEMcCDG

[Dusk @DuskFoundation]

Privacy gets interesting when it becomes programmable.

Private transfers protect transaction data. RWA tokenization needs smart contracts with confidential state, eligibility checks, and selective disclosure.

$DUSK brings programmable privacy to financial applications.

[Dusk @DuskFoundation]

Repo: https://t.co/rvd2wCcoS0

Release: https://t.co/M9nDdosjY9

[Dusk @DuskFoundation]

The State Snapshots tool for Node Operators is live.

It helps node runners, provisioners, and service providers package, verify, publish, restore, and retain state for Rusk nodes.

Repo links below ↓

[Dusk @DuskFoundation]

@kevinolearytv Enterprise adoption needs more than just fast rails. Regulated assets need privacy, compliance, issuer controls, reporting, settlement, and corporate actions onchain. That's what Dusk ($DUSK) is. Kevin, we should talk.

[Dusk @DuskFoundation]

The new Dusk Wallet is making staking simpler.

Manage owner-based staking directly in the wallet, or use @sozu_dusk liquid staking without running a node.

Coming to your browser.

[Hein Dauven @HeinDauven]

And it works. 😎
@sozu_dusk 🤝 @DuskFoundation

[Hein Dauven @HeinDauven]

If you hold $stDUSK, the wallet will automatically detect the asset.

From there you can transfer it and approve spending, like an ERC20/DRC20 token.