Privacy-preserving blockchain infrastructure for regulated finance. L1 + EVM layer · ZK selective disclosure · RWAs · $DUSK
Joined June 2018
- Tweets4.2K
- Following369
- Followers97.2K
- Likes3.8K
Dusk retweeted
Building Dusk Domains taught me a lot about dApp development on dusk-network:native. Along the way I found a number of things to fix and improve that will pay off for everyone building on it.
The first one is live now in the form of a contract called Multicall, deployed on mainnet and testnet.
A dApp page needs a lot of values from the chain, like balances, token info and settings. Normally every value is its own query to a node, sent one after another. That's slow, and new blocks can land in between, so the answers don't always line up.
Multicall packs up to 256 contract reads into one query. The node runs them back to back against the same block and sends back one reply.
Reading 250 balances on mainnet: 8.9 s one query at a time -> 90 ms in one batch.
Any dApp or backend on Dusk can use it today. Read-only, immutable and MIT licensed:
github.com/HDauven/dusk-mult…
Mainnet and testnet contract ID: 93de287b7d349d678a0038fe7772e8960e1a84a1b5da2d0b1f62f532616ce1d4
Which financial app would you like to see a private onchain version of?
We just shipped 10 releases of Dusk's core cryptography.
Here's the simple version of what each piece does and what just got better.
→ Proofs (PLONK)
The engine that lets you prove something is true without revealing the details. It's how Dusk keeps transactions private and still verifiable. Creating and checking proofs is now roughly 2x faster.
→ Hashing (Poseidon)
A digital fingerprint for data. Same input, same fingerprint, and you can't reverse it. Inside a proof, it now does the same job with about a third less work.
→ Merkle trees
A way to prove one item is part of a huge list without showing the list. Those proofs now take a third less work, and the trees reject bad input.
→ Encryption (ElGamal + SAFE)
What locks private data so only the right people can read it. Decrypting an encrypted number inside a proof now takes up to 84% less work.
→ Signatures (Schnorr + BLS)
How the network knows a message really came from you. Multisig now has protection against key tricks, and checking a signature inside a proof takes 14% less work.
→ Curves
The math the whole stack is built on. Both foundation libraries were upgraded and now reject bad input.
Full breakdown in the thread ↓
Built for regulated finance, from the cryptography up.
Our CTO @HeinDauven’s latest article explains how owning the stack gives Dusk an edge ↓
Europe wants bigger onchain markets.
On 9 October, the EU Council backed changes that would allow more financial activity under the DLT Pilot Regime.
Currently, the DLT Pilot Regime lets authorised operators test blockchain-based trading and settlement under regulatory supervision.
Expanding it is part of a wider push to make it easier to invest across Europe and fund businesses.
The opportunity is in connecting the steps that make a market work. When trading, ownership records and payments sit in separate systems, operators have to keep matching them up.
Consider what happens when a bond changes hands.
The buyer needs to meet its eligibility rules. Ownership and payment need to transfer. The issuer needs to know who should receive the next interest payment.
Dusk provides infrastructure for connecting those steps onchain.
→ Securities issued natively onchain creates the bond directly onchain, with an ownership record that can support transfers and interest payments.
→ Citadel helps investors prove they qualify to buy the bond without publishing personal details onchain.
→ Delivery versus payment is a requirement that the security and payment transfers complete together, or neither complete, when both assets are onchain.
For issuers, that can mean fewer records to reconcile after a sale, with ownership changes reflected in the next interest payment.
Did you know Dusk is partnered with @chainlink?
Here’s how the integration is designed to connect DuskEVM to other blockchains and bring real-world market data into its apps.
→ Move assets between networks (CCIP)
CCIP connects blockchains so assets can move between them. For DuskEVM, the aim is to let tokenized shares and bonds reach other supported networks, while issuers keep control of their tokens.
→ Bring official exchange data into apps (DataLink)
A blockchain app needs a connection to information from the outside world. DataLink’s role is to bring official market data from NPEX, a Dutch securities venue, onchain. Developers can then build financial apps using data from the source.
→ Supply fast price updates (Data Streams)
Markets move, and trading apps need prices that keep up. Data Streams supplies frequent price updates, helping apps value assets and respond to market changes.
→ Make DUSK transferable across chains (CCT)
The Cross-Chain Token standard covers DUSK itself. The plan includes transfers across networks such as Ethereum and Solana, giving people and apps on those networks more ways to access and use DUSK.
Dusk (@duskfoundation) is adopting the Chainlink interoperability & data standards to enable compliant, cross-chain tokenized securities backed by real-world equities from NPEX, a fully regulated Dutch stock exchange with €200M+ in financing raised & 17.5K+ active investors.
prnewswire.com/news-releases…
Chainlink CCIP will serve as the canonical interoperability solution for tokenized NPEX assets, while also enabling the Dusk Network’s native token, DUSK, to be natively transferable across Ethereum and Solana via the Cross-Chain Token (CCT) standard.
Chainlink DataLink will serve as the exclusive data oracle solution for bringing NPEX exchange data onchain and cross-chain. Dusk and NPEX will become official data publishers of regulated market data, and Chainlink Data Streams will deliver low-latency price updates for institutional-grade DeFi applications on Dusk.
Together, this integration brings regulated securities, verified financial data, and cross-chain connectivity into a unified infrastructure, unlocking a new era of institutional capital markets onchain, powered by the Chainlink platform.
Dusk has been shipping release after release, and we're just getting started.
More are on the way as we close in on the next network upgrade.
One of the biggest in our 8-year history.
Dusk retweeted
We build and maintain the cryptography behind Dusk ourselves. This article explains what's in that stack and why we think owning it is worth it.
"Regulated finance asks more of privacy than most of crypto does. It needs confidentiality for the people trading and evidence for the people supervising, on the same ledger and at the same time."
Our CTO @HeinDauven on nearly seven years of cryptography behind Dusk ↓
Dusk retweeted
We’ve been building zero-knowledge cryptography for nearly seven years. In this article I explain what sits underneath Dusk.
That's how regulated assets go onchain without revealing your personal data.
See how it works ↓
docs.dusk.network/learn/mark…
End of official thread.
Any replies below are not part of this thread. Verify any link against the official @DuskFoundation account before interacting.
The first .dusk name I'm claiming is ______.dusk
Dusk Domains got a full redesign.
Think ENS, but for Dusk. A name like yourname.dusk replaces your long wallet address.
→ Claim your .dusk name
→ Link it to your addresses, site and avatar
→ Buy, sell or auction names
Built by our CTO @HeinDauven. Try it on testnet ↓
Dusk retweeted
Every transfer, tokenized asset and proof on Dusk runs on these libraries.
So we went through all of them: proofs, hashing, encryption, signatures, Merkle trees and the curves underneath. Test coverage and API safety went up, and we found large optimizations along the way.
It took time and an incredible amount of effort, and it's not the kind of work that's perceived as "bullish". But looking at what Dusk secures today, and at what it will secure as more real-world value moves onchain, hardening the math everything stands on is the most important work we can do.
It also compounds. Every asset, dApp and institution building on Dusk inherits the benefits.
Every one of these libraries is now being mutation-tested, so the tests themselves get tested. Preliminary results are very promising.
We also ran more audits with the newest AI models, and they turned up no serious flaws. We'll keep doing automated auditing of the stack continuously as the models improve.
Our next hard fork brings all of this to the network, and it will be the biggest and most comprehensive upgrade Dusk has ever done, making the network as a whole much more resilient and future proof.
We just shipped 10 releases of Dusk's core cryptography.
Here's the simple version of what each piece does and what just got better.
→ Proofs (PLONK)
The engine that lets you prove something is true without revealing the details. It's how Dusk keeps transactions private and still verifiable. Creating and checking proofs is now roughly 2x faster.
→ Hashing (Poseidon)
A digital fingerprint for data. Same input, same fingerprint, and you can't reverse it. Inside a proof, it now does the same job with about a third less work.
→ Merkle trees
A way to prove one item is part of a huge list without showing the list. Those proofs now take a third less work, and the trees reject bad input.
→ Encryption (ElGamal + SAFE)
What locks private data so only the right people can read it. Decrypting an encrypted number inside a proof now takes up to 84% less work.
→ Signatures (Schnorr + BLS)
How the network knows a message really came from you. Multisig now has protection against key tricks, and checking a signature inside a proof takes 14% less work.
→ Curves
The math the whole stack is built on. Both foundation libraries were upgraded and now reject bad input.
Full breakdown in the thread ↓
10/ dusk-plonk 0.24 github.com/dusk-network/plon…
dusk-poseidon 0.44 github.com/dusk-network/Pose…
poseidon-merkle 0.11 github.com/dusk-network/merk…
jubjub-elgamal 0.6 github.com/dusk-network/jubj…
jubjub-schnorr 0.7 github.com/dusk-network/jubj…
End of official thread.
Any replies below are not part of this thread. Verify any link against the official @DuskFoundation account before interacting.
