Duskodino

Hedger is $Dusk latest dApp on confidential execution layer for regulated securities on an EVM-compatible L2. (finality, staking, consensus, DA still on L1) -FHE-based (Proved by #ZK) -Obfuscated order books -Private ownership -Auditable by regulators -In-browser proving (~2s)

$DUSK = #RWA #Tokenization Infra -Privacy: L1 #ZK PLONK / L2 ZK+HE EVM compatible -Auditable shielded transactions -Instant legal finality -Protocol-level licensing (MTF, Broker, ECSP, DLT-TSS) -Onboarding millions of RWA incl. real yield-bearing MMFs, stocks, bonds -MC=$80M

The next phase of tokenization is not about putting assets onchain. It is about making the market work onchain.

AFME has published a new vision paper for DLT-based European capital markets. Europe's next market architecture needs compliant network infrastructure. ↓ The paper points to a model built around: - multi-chain interoperability - regulated financial institutions operating asset ledgers - central-bank-money connectivity through Pontes - collateral eligibility for DLT securities Regulated assets need more than wrappers. They need identity, transfer controls, settlement finality, privacy, and disclosure rules inside the market workflow. Dusk approaches that through architecture: - Phoenix shielded transactions on DuskDS - Confidential transactions on DuskEVM with Hedger - Selective disclosure for compliance - Deterministic finality - Atomic DvP settlement for regulated financial workflows Tokenization gets assets onchain. Market infrastructure makes them usable.

RWAs are moving past the narrative cycle. In our recent Space with @ShiftRWA, the discussion kept returning to one point: tokenized assets only matter when the market around them works. That means issuance, settlement, access, privacy, liquidity, and compliance need to fit together. ↓ 1. Tokenization is the first step Most assets entering crypto today are wrappers around existing assets. For many markets, that is the practical entry point. It brings assets into a more open environment while issuers, venues, and regulators adapt. 2. Settlement is the real test Traditional markets still rely on delayed settlement, reconciliation, and intermediated records. Even after the move to T+1 in the U.S., DTCC data still shows fail rates at 3.19% for NSCC and 3.07% for DTC. Onchain settlement can take this further. With atomic delivery-versus-payment, the asset leg and payment leg execute together, or neither does. 3. Regulation is part of the product Regulated assets need market rules built into the system. That means KYC, eligibility checks, transfer controls, auditability, and clear legal accountability. The job is not to route around regulation. The job is to make regulated markets easier to run. 4. Privacy decides whether institutions can use it Public ledgers expose balances, counterparties, and trading activity. That doesn't work for regulated markets. Institutions need confidential transactions with selective disclosure, so auditors and regulators can access the information they need without making every position public. 5. Native issuance is the end state Tokenization brings existing assets into the market. Native issuance moves the asset lifecycle itself onchain: issuance, trading, settlement, servicing, and disclosure. Dusk is built for native issuance, with privacy, compliance controls, deterministic settlement, and infrastructure for regulated financial applications. RWAs don't become financial markets because assets are tokenized. They become financial markets when the market infrastructure is ready.

You can start building right away on $DUSK! You can use Forge to build smart contracts. It comes with a CLI to create scaffoldings: github.com/dusk-network/f… You can use Dusk Connect to build dApp frontends: github.com/dusk-network/c… You can join our Discord here and request the developer role: discord.gg/dusk-official

Institutions want rails they can trust. Users want products they actually enjoy using. @DuskFoundation and the SHIFT team sits together to discuss about what it takes to fix that. 📅 April 28, 3 PM UTC. Set your reminder: x.com/i/spaces/1DGle…

Updated the look and feel of Dusk Connect and Dusk Wallet. They’re starting to feel much more Dusk now. Good tooling needs a good UX too. Feedback would be much appreciated!

Building on Dusk has never been easier. Forge for smart contracts. Dusk Connect for wallet integration. The new Dusk Wallet for users, across browser, desktop, and mobile. Here's what you need to know. ↓ 1. Dusk Connect With Dusk Connect, developers no longer need custom code for specific wallets. The SDK includes: Automatic wallet discovery Wallets surface via EIP-6963 without manual config. Core dApp actions built in Account access, signing, transactions, and network helpers. Familiar, namespaced RPC Methods like dusk_requestAccounts and dusk_signMessage, clean of EVM collisions. Lightweight by design Zero runtime dependencies. Predictable wallet behavior Conformance tests enforce spec parity across implementations. 2. Dusk Wallet The new Dusk Wallet is available as a browser extension, desktop app, and mobile app, built around Dusk Connect. dApps can plug in directly to request accounts, ask users to sign, submit transactions, and handle permissions through a familiar wallet flow. Users get full Dusk functionality in one wallet: - public and private transfers - shield/unshield - staking and reward claiming - DRC-20 and DRC-721 assets - dApp permissions - and local key storage. With these, developer experience on Dusk is closer to the standards devs already know.

Tokenization is expanding fast, but where are the real opportunities today? Join us April 24, 3 PM UTC with: 🔹 @Neotamandua from @DuskFoundation 🔸 @_whalebird from @pendle_fi 🔹 @deankd_ from @RWA_xyz 🔸 @kasstawi from @hamilton_labs Don’t miss it 👇 x.com/i/spaces/1DxLd…

Very important step for anyone building on @DuskFoundation. Better tooling for builders, and a much stronger foundation for third-party apps and wallets to emerge across the network.

Building dApps on DuskDS just got simpler. Dusk Connect is a new SDK that lets dApps integrate with any compatible wallet. Alongside the new Dusk Wallet, a first-party wallet for browser extensions, desktop, and mobile. Repos are open for developer preview ↓

We're excited to join @HouseofChimera's RWA Megaspace this Friday. 🗓️ April 24, 17:00 CET Our Head of Product @Neotamandua will be joining as a speaker. Set a reminder ↓

Great to see @DuskFoundation represented on this megaspace hosted by @HouseofChimera. @Neotamandua, our Head of Product, will be joining to talk tokenization and RWAs. 💪

Very few projects are building this close to a real exchange.🏦 $Dusk working alongside @NPEX means real exposure to market structure, real constraints, the kind most teams never face. That setup is rare… and it’s about to matter a lot more.👇🏼 DYOR @DuskFoundation @HeinDauven #RWA #Tokenization #Web3‌‌

Tokenization and native issuance solve different problems. The difference comes down to where the asset actually lives, who holds it, and what happens when something goes wrong. Tokenization: - The bond still sits with a custodian - The token is a representation that tracks it - If the custodian fails, the token is a claim on a broken process Every tokenized asset needs reconciliation between the onchain record and the off-chain reality → settlement depends on intermediaries → reporting means cross-referencing two systems. The wrapper adds a layer. It does not remove one. Native issuance: - The asset is created onchain as the legal record - Settlement is atomic, custody is protocol-level - Corporate actions execute in code, no reconciliation required Dusk is built for native issuance. The protocol handles issuance, settlement, and corporate actions natively. NPEX, an AFM-regulated exchange, is pursuing the DLT-TSS license to natively issue securities on Dusk. Native issuance is how markets come onchain.

Very productive weekend. Got a lot of work done across security, tooling and infra. Hope to show some of the tooling work this week.

$DUSK = L1 #RWA infra: -powering the entire backend of a regulated exchange for secondary markets -bridging TradFi & DeFi w/ built-in auditable privacy + compliance at protocol level -deploying an EVM-compatible L2 (DuskEVM) with native L1 settlement Current MC=$87M

The rise of $DUSK compared to $ZEC. 👀 The new kid on the blocks. Proper @DuskFoundation 🚀 Hop on board, you’re still early. Lot’s of things happening behind the scenes. What is Dusk? x.com/i/spaces/1DxLd…