Privacy-preserving blockchain infrastructure for regulated finance. L1 + EVM layer · ZK selective disclosure · RWAs · $DUSK
Joined June 2018
- Tweets4.2K
- Following370
- Followers97K
- Likes3.8K
Introducing T-Minus 90, a program that takes three dApps from idea to mainnet on Dusk in 90 days.
Our CTO @HeinDauven, creator of Dusk Domains, and @tminus_dusk, creator of @sozu_dusk, launched it and mentor each team from the first contract onward.
Selected builders get:
→ Help with deployment costs
→ A weekly call with both mentors
→ A Claude Team seat for 3 months
→ Product reviews and a security review before launch
In return, each project is developed in public with an open-source repo. It needs a working proof of concept on testnet by December 1 and a mainnet launch by February 1. Builders keep full ownership, and no equity is taken.
Distribution counts most, so applications should show who will use the dApp and why. ZK, privacy, AI and agentic use cases are a plus.
Applications close October 30. Apply below ↓
Full details and the application in Hein's thread ↓ xitter.cf/HeinDauven/status/2113…
T-Minus 90 is a builder program for Dusk that @tminus_dusk and I are running together. Over 90 days, we help 3 builders take a dApp from idea to mainnet.
We've both shipped on Dusk. Tminus built @sozu_dusk, I built Dusk Domains. So the mentoring comes from people who've been through it, from the first contract to the mainnet deploy.
The deal
You get a Claude Team seat for 3 months, a weekly call with both of us, product reviews along the way and a security review before you go live. You also get shoutouts from my X account, help with the mainnet deployment costs and a private Discord with the other builders.
In return, you build in public, with an open-source repo and a short weekly update. Your proof of concept needs to work on testnet by December 1st. If it doesn't, your seat goes to the next person on the waitlist. The dApp needs to be live on mainnet by February 1st.
You fully own what you build. We don't take equity.
Who we're looking for
What matters most to us is distribution. Who is going to use your dApp and why will they use it? ZK and privacy, AI or agentic use cases are a plus, but the proof of concept on testnet needs to work first. The ZK or AI parts can come later.
Applying takes about 5 minutes. If you're not picked, you're on the waitlist.
Timeline
Oct 23, 2026 applications open
Oct 30, 2026 applications close
Nov 1, 2026 3 builders picked, kickoff, Discord opens
Dec 1, 2026 testnet PoC check
Feb 1, 2027 mainnet launch, then a retro
Apply below 👇
End of official thread.
Any replies below are not part of this thread. Verify any link against the official @DuskFoundation account before interacting.
Dusk retweeted
The cool thing about this is that @DuskFoundation is now also tracked: defillama.com/chain/dusk
I've opened a PR for @sozu_dusk too: github.com/DefiLlama/DefiLla…
As soon as it gets accepted, dusk-network:native staked on Sozu will also be tracked on @DefiLlama 💪
Dusk Domains is now on @DefiLlama.
It tracks fees and revenue on-chain. Every registration, renewal and 2.5% market fee, read from the treasury vault's events.
defillama.com/protocol/dusk-…
Dusk retweeted
Building tools for Dusk usually means you have to use either JavaScript or Rust.
Need Python or Go for your stack? I ported W3sper, Dusk's wallet and transaction SDK, to both as an experiment.
If you're a builder, try them on testnet and tell me what breaks. PRs welcome:
github.com/HDauven/w3sper.py
github.com/HDauven/w3sper.go
Dusk retweeted
Joined Binance Pick yet?
How many Scores have you collected? Drop your total below.
Earn Scores through eligible dusk-network:native trading, use them for virtual predictions and compete for a share of 1,000,000 USDC.
Dusk is sponsoring @binance Pick, powered by @predictdotfun.
→ Earn Scores through eligible dusk-network:native trading
→ Use them to make virtual predictions
→ Compete for a share of 1,000,000 USDC
Explore the campaign ↓
Joined Binance Pick yet?
How many Scores have you collected? Drop your total below.
Earn Scores through eligible dusk-network:native trading, use them for virtual predictions and compete for a share of 1,000,000 USDC.
Dusk is sponsoring @binance Pick, powered by @predictdotfun.
→ Earn Scores through eligible dusk-network:native trading
→ Use them to make virtual predictions
→ Compete for a share of 1,000,000 USDC
Explore the campaign ↓
Dusk retweeted
Dusk Domains is now on @DefiLlama.
It tracks fees and revenue on-chain. Every registration, renewal and 2.5% market fee, read from the treasury vault's events.
defillama.com/protocol/dusk-…
Got your .dusk name yet? Drop it in the comments ↓
Dusk Domains is live on mainnet.
Give your long wallet address a memorable .dusk name.
→ Register from 10 dusk-network:native a year
→ Buy and sell names on the marketplace
Get yours today at dusk.domains
Dusk retweeted
T-Minus 90 is a builder program for Dusk that @tminus_dusk and I are running together. Over 90 days, we help 3 builders take a dApp from idea to mainnet.
We've both shipped on Dusk. Tminus built @sozu_dusk, I built Dusk Domains. So the mentoring comes from people who've been through it, from the first contract to the mainnet deploy.
The deal
You get a Claude Team seat for 3 months, a weekly call with both of us, product reviews along the way and a security review before you go live. You also get shoutouts from my X account, help with the mainnet deployment costs and a private Discord with the other builders.
In return, you build in public, with an open-source repo and a short weekly update. Your proof of concept needs to work on testnet by December 1st. If it doesn't, your seat goes to the next person on the waitlist. The dApp needs to be live on mainnet by February 1st.
You fully own what you build. We don't take equity.
Who we're looking for
What matters most to us is distribution. Who is going to use your dApp and why will they use it? ZK and privacy, AI or agentic use cases are a plus, but the proof of concept on testnet needs to work first. The ZK or AI parts can come later.
Applying takes about 5 minutes. If you're not picked, you're on the waitlist.
Timeline
Oct 23, 2026 applications open
Oct 30, 2026 applications close
Nov 1, 2026 3 builders picked, kickoff, Discord opens
Dec 1, 2026 testnet PoC check
Feb 1, 2027 mainnet launch, then a retro
Apply below 👇
Dusk is sponsoring @binance Pick, powered by @predictdotfun.
→ Earn Scores through eligible dusk-network:native trading
→ Use them to make virtual predictions
→ Compete for a share of 1,000,000 USDC
Explore the campaign ↓
Binance Pick Week 1 ends soon and Earnings Season is live. Predict with Scores, climb the leaderboards and share 1,000,000 USDC.
Join: app.binance.com/uni-qr/proph…
Powered by @predictdotfun
Sponsored by $ACE $DUSK $SXT
T&Cs apply. Not available in all regions.
We've upgraded private transfers on Dusk.
The latest Phoenix releases brings stronger user protection, with more efficient proof generation.
Here's the simple version of what's improved ↓
→ Finding your funds (ownership checks)
Phoenix represents private funds as records called notes. Your wallet checks which ones belong to you. Each check now uses 36% less CPU time, so the same processing time can handle about 156 checks instead of 100.
→ Reading private amounts (note validation)
Your wallet decrypts a note to read its amount. Phoenix checks that the recovered amount is consistent with the note, rejecting mismatches. This helps prevent inconsistent payment data from being accepted.
→ Checking private transfers (zero-knowledge proofs)
A proof lets the network verify that a transfer follows the rules without seeing its private details. The updated proofs reject malformed keys and attempts to use the same note twice in one transfer.
→ Protecting the sender (sender encryption)
Phoenix uses random values to help hide sender data. The updated proofs reject values that could reveal a sender's key or make transfers linkable to the same sender.
→ Protecting key data (secret handling)
Phoenix now clears key's secret data from memory when discarded. It also hides secret key material and private proof inputs from debug output, reducing exposure when developers troubleshoot software.
These go live with Dusk's next network upgrade.
Dusk retweeted
Fun fact: .dusk names made ~30k dusk-network:native (~$3,400) in revenue on day one.
1 day -> ahead of ~80% of protocols on DefiLlama
7 days -> ahead of ~2 in 3
Pretty crazy, and that's out of 1,300+ listed protocols. A lot of adoption room still left for crypto dApps.
Dusk retweeted
Nothing beats seeing a side project get real users.
Thanks to everyone who registered a name, listed one or helped test Dusk Domains before launch. Great first day 💪
Wallet support is up next!
Dusk Domains is live on Dusk mainnet.
One readable .dusk name for your Dusk address, from 10 DUSK a year.
dusk.domains
Dusk retweeted
For the record, we're monitoring our infrastructure closely as the CVEs keep coming in.
None of our servers run PHP. The eMudhra certificates are distrusted on our servers. The new NGINX CVEs depend on features we don't use. Node.js has been patched on all our services.
Today's PHP disclosure is by the way a good example of why we at Dusk have invested so much time in making continuous AI-assisted audits and reviews part of how we build.
PHP patched two critical bugs, CVE-2026-109618 and CVE-2026-109619. Both let an attacker run code on a web server without logging in. One sits in how PHP cleans up after running out of memory. The other is state that survives from one request to the next after its memory has been freed. The oldest affected code goes back to PHP 5.4 in 2012.
Calif and Wiz found them independently using AI. Calif did it with no special setup and only models anyone can access. PHP runs a huge part of the web and a lot of people have looked at its code over the years, yet these bugs sat there for over a decade. Getting the fixes right took the PHP team weeks.
This won't be the last case like it. The same tools are available to attackers, and a lot of older code has never been looked at this deeply, as the speed at which AI can inspect, test and validate invariants is impossible for a human to match.
It also matches what we see in our own stack. Most of what turns up is in code written before we had these tools, so that's where we've put the majority of our focus, going back through all of our older code. The fixes go out in our public repos, like the Phoenix release below.
The tools only get you so far. Finding bugs is a numbers game in the end, and with enough compute you'll find something in almost any codebase. The hard part is understanding what you found and which invariants matter in the first place. Without that you end up with fixes that don't hold up. A bad fix is dangerous because it gives people a false sense of safety. Judging what's a real issue and fixing it properly still takes people who know what they're doing, especially when dealing with cryptography.
That costs a lot of time, testing and compute upfront. Our bet is that it pays off in the long run though.
CVEs for reference:
github.com/php/php-src/secur…
github.com/php/php-src/secur…
Dusk Domains is live on mainnet.
Give your long wallet address a memorable .dusk name.
→ Register from 10 dusk-network:native a year
→ Buy and sell names on the marketplace
Get yours today at dusk.domains
Dusk Domains is live on Dusk mainnet.
One readable .dusk name for your Dusk address, from 10 DUSK a year.
dusk.domains
Dusk retweeted
This Phoenix release comes out of a re-review of our whole cryptography stack, which we started months ago.
With how much easier AI has made exploit hunting since, and the incidents we've all been seeing, I'm glad we did.
A lot of effort, testing and compute went into it. We also rechecked the implementation against the protocol's formal proofs. It doesn't guarantee we're bug free, but we should be a lot safer than before.
Dusk retweeted
Dusk Domains is live on Dusk mainnet.
One readable .dusk name for your Dusk address, from 10 DUSK a year.
dusk.domains
Release notes:
→ github.com/dusk-network/phoe…
→ github.com/dusk-network/phoe…
End of official thread.
Any replies below are not part of this thread. Verify any link against the official @DuskFoundation account before interacting.
