Oh man, why is my position on Dusk so low? 😭@Dusk
After my loss in the Zama trading competition, I checked the Dusk CreatorPad leaderboard and found my name pretty low here too. Tough day. 😂
I was briefly checking $TUT and $GPS , but my attention quickly came back to Dusk.
So what now? Keep refreshing the leaderboard, or just have some chai and aloo chips and accept my fate? 😭😂
Aaj ka best decision: chai, chips, no emotional posting.
But while looking deeper into DuskEVM, I realised I had been thinking about EVM testnets too simply.#dusk
I used to think: Solidity works, developers deploy contracts, and that’s basically it.
Then I noticed DuskEVM went live on August 10, 2026, with Chain ID 745, DUSK as gas, and familiar Hardhat and Foundry tooling.
That part felt familiar.
What actually caught my attention was what happens underneath.
DuskEVM provides the EVM execution environment, while DuskDS remains connected to settlement and data availability.$DUSK
So this isn’t simply “Dusk has an EVM now.”
It’s a familiar Solidity environment connected to Dusk’s native architecture.
Maybe that makes it easier for developers to enter Dusk without leaving its settlement model behind.
Or maybe the real test starts when actual applications begin using the full stack.
The testnet is live.
Now I’m more curious about what developers actually build on it.
What would you test first on DuskEVM?
After my loss in the Zama trading competition, I checked the Dusk CreatorPad leaderboard and found my name pretty low here too. Tough day. 😂
I was briefly checking $TUT and $GPS , but my attention quickly came back to Dusk.
So what now? Keep refreshing the leaderboard, or just have some chai and aloo chips and accept my fate? 😭😂
Aaj ka best decision: chai, chips, no emotional posting.
But while looking deeper into DuskEVM, I realised I had been thinking about EVM testnets too simply.#dusk
I used to think: Solidity works, developers deploy contracts, and that’s basically it.
Then I noticed DuskEVM went live on August 10, 2026, with Chain ID 745, DUSK as gas, and familiar Hardhat and Foundry tooling.
That part felt familiar.
What actually caught my attention was what happens underneath.
DuskEVM provides the EVM execution environment, while DuskDS remains connected to settlement and data availability.$DUSK
So this isn’t simply “Dusk has an EVM now.”
It’s a familiar Solidity environment connected to Dusk’s native architecture.
Maybe that makes it easier for developers to enter Dusk without leaving its settlement model behind.
Or maybe the real test starts when actual applications begin using the full stack.
The testnet is live.
Now I’m more curious about what developers actually build on it.
What would you test first on DuskEVM?