Real-world asset interoperability helps issuers reach more investors.
But when a natively issued asset becomes interoperable across blockchains, how do ownership and investor rights work?
Read our new article on RWA interoperability ↓
Your payments shouldn’t be visible to everyone.
On public blockchains, a payment can reveal more of your financial life than you might expect.
How this affects you 👇
Putting financial assets onchain shouldn’t make every position public.
Market participants need confidentiality, while authorized reviewers need evidence.
Here’s how Hedger serves both on DuskEVM 👇
Privacy works differently from one blockchain to another.
To understand why, ask:
→ What stays private?
→ How is it protected?
→ Who can see shared information?
→ Can developers build apps beyond payments?
Read our latest article to understand blockchain privacy better ↓
Quite a lot landed across $DUSK this past week.
We're improving the stack in every direction at once. ZK performance, cryptographic safety, wallet security, serialization, DuskEVM compatibility, node reliability and dependency hygiene.
Check it out:
https://t.co/sy9s3shIYF
Dusk x @binance CreatorPad is now live.
Join the campaign, create content about Dusk, and climb the leaderboard for a share of 480,000 DUSK.
Campaign details and entry link ↓
Automating finance on public blockchains can expose sensitive data.
Institutions can use smart contracts for checks, payments, settlement and reporting.
On Dusk, you can use privacy-perserving smart contracts to keep your data confidential.
See the docs in the replies ↓
Public blockchains can expose more than an investor’s holdings.
Transfers, dividend payments and shareholder votes can reveal positions and strategy.
Dusk’s privacy-preserving smart contracts can protect sensitive data while enabling automatic financial flows.
“OpenDusk is about empowering the community and giving the community the tools to develop use cases for Dusk.” - @tminus_dusk
Listen to the full conversation ↓
Our archive nodes got a major efficiency boost.
Event storage fell by more than 90%, from 310.7 MB to 27.7 MB, while preserving historical results and reducing infrastructure needs.
Read the full Dusk Progress Update ↓
Sozu, our liquid staking partner, has completed its first external security audit.
mocello engineering, led by Dusk Foundation core developer Moana Marcello, conducted the review. Congratulations to the Sozu team!
Check out more details below ↓
Build native Dusk smart contracts with less boilerplate.
Dusk Forge is a Rust/WASM framework that generates exports, schemas and data drivers from one module, giving developers a simpler path from code to applications.
Get started with Forge ↓
A private transfer protects one payment.
Privacy-preserving smart contracts can protect what happens around it: who can take part, which rules are enforced and what stays confidential.
On Dusk, privacy can extend from payments to financial applications.
DuskEVM connects Dusk to the EVM economy without leaving institutional privacy behind.
That expands Dusk in two directions:
- EVM compatibility gives builders a familiar way in.
- Hedger, Dusk's privacy module, keeps sensitive financial activity private while allowing it to be checked when needed.
Teams don't need to rebuild applications around a custom blockchain stack. They can use Solidity on DuskEVM with familiar wallets, libraries and developer tools.
Chainlink CCIP extends that reach across networks through cross-chain messaging and routes for tokenized assets. That gives EVM assets and liquidity a practical path toward Dusk.
Bringing assets closer is only part of the job.
Banks, exchanges and asset managers cannot expose every balance, position, transfer amount or counterparty, but they still need to prove that rules were followed.
Hedger brings both together inside DuskEVM, keeping sensitive financial activity confidential while transactions remain verifiable and auditable.
Together, that gives Dusk a wider path to builders, applications, assets and liquidity.