2026-01-23 08:00:15

In 2026, there are still projects shouting "We also support EVM," honestly just repeating an outdated selling point. Compatibility with EVM itself isn't technically difficult; the real challenge lies in clearly defining the responsibilities of the execution layer and the data settlement layer, and completely eliminating interaction friction.

DuskEVM's approach is from a different dimension: the architecture is divided into two layers—DuskDS handles settlement and data availability, while DuskEVM serves as a pure execution layer following an EVM-equivalent route. What does this mean? It means you can directly use familiar development tools like MetaMask and Hardhat without being forced to learn new languages or change your development paradigm. No learning costs or migration costs.

The more core difference is that DuskEVM is not just a skin over EVM. It is based on the OP Stack's execution architecture, where transaction data is stored on DuskDS in the form of blobs. What's interesting about this design—is that one end connects to the determinism and finality required by compliant finance, while the other end connects to the portability and developer-friendliness of the EVM ecosystem, tightly binding these two needs.

From a timeline perspective, the official Town Hall has already clearly stated: Rusk upgrade is the final critical phase before mainnet launch. In other words, it's no longer just a pie-in-the-sky vision; signs of takeoff are already visible at the end of the runway. Network parameters, RPC, and Explorer information have also been published in the documentation.

Here's an interesting detail: currently, the mempool is not public, and transactions are visible to the Sequencer. This means that traditional tactics like frontrunning and sandwich attacks have little room to operate here.

While others are still discussing "compatibility," we are already turning the "infrastructure for compliant on-chain" into a real product. Now is the time to get your Solidity contracts running on the testnet—don't wait until the mainnet window opens and find the racecourse already full.

View Original

This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.

14 Likes

Reward
14
6
Repost
Share

Comment

0/400

GasFeeCrier

· 7h ago

He's started selling the "EVM-compatible" package again, really tired of it. But Dusk's two-layer architecture approach is indeed different, forcibly linking compliance and developer friendliness—this is true product thinking. Getting the contracts running smoothly on the testnet early is crucial; waiting until the mainnet launches will be too late. My biggest concern is that front-running and sandwich attacks have no place to operate. Finally, a project is seriously addressing the toxic MEV problem. Projects that constantly claim EVM compatibility are as cheap as claiming "we also support smart contracts." Dusk is different—using the OP Stack infrastructure plus DuskDS, this is genuine engineering work. Not revealing the mempool details shows they are seriously considering the sequencer mechanism, not just copying Ethereum straightforwardly. Rusk upgrade is coming; projects still talking nonsense now will just be waiting to be stepped on. The testnet window is open now. Those who keep saying "we will participate soon" will probably still be figuring out how to deploy contracts when the mainnet actually launches. This is how to productize infrastructure properly, unlike some projects that have been just talking about plans for three years.

View OriginalReply0

GweiWatcher

· 7h ago

Compliance + EVM can directly run Solidity contracts, this is the real gameplay. Other projects are still talking about compatibility.

View OriginalReply0

NFT_Therapy

· 7h ago

This time it's really different, not just another story of "compatibility with EVM is enough." Integrating compliance and developer-friendliness, few projects dare to play like this. As for mempool transparency... we'll see if it can really prevent MEV in the future. Wait, is the Rusk upgrade coming so quickly? Need to keep a close watch. Try copying the contract to the testnet first, or it will be really late once the mainnet goes live.

View OriginalReply0

Anon4461

· 7h ago

Wait, is the Rusk upgrade really the final sprint? How much longer does Dusk's mainnet have? --- The combination of compliance + EVM is indeed unprecedented, but is private mempool reliable? --- Are there many people running contracts on the testnet now? How's the ecosystem's enthusiasm? --- It sounds nice, but isn't it just another "this time is different"? We'll see once the mainnet is live. --- The design idea of blob dropping into DuskDS is interesting, but can the gas fees be reduced? --- With sandwich attacks gone, how will validator rewards be calculated? Could it turn into another form of unfairness? --- Running directly on Hardhat really hits the pain point for developers. --- As the Town Hall mentioned, it feels like this time they are genuinely pushing forward, not just a money-grabbing move. --- The question is, when will the ecosystem applications arrive? Even a fast empty chain is useless without them.

View OriginalReply0

DuskSurfer

· 7h ago

No matter how many selling points there are, it depends on whether there's real substance. This time, it doesn't seem to be just talk.

View OriginalReply0

MEVHunterWang

· 7h ago

You really need to take a serious look at the compliance infrastructure; not all EVM-compatible projects are the same. --- There are too many projects using OP Stack skins, and the layered approach of DuskDS is actually quite interesting. --- Not revealing the public mempool directly cuts off the opportunity for frontrunning, which I think is a bit harsh. --- Rusk's upgrade has indeed been fast; once the mainnet launches, a reshuffle might be necessary. --- Those who are only shouting about EVM compatibility should really be worried now; this window of opportunity won't last long. --- Using MetaMask directly is still attractive to developers; low learning costs are truly a competitive advantage. --- The fact that sandwich attacks can't survive is worth noting; MEV requires a rethinking. --- While others are still selling concepts, they have already published all network parameters, clearly a different level of progress. --- Getting Solidity to run is just the basics; the key is how that compliant infrastructure is actually implemented.

View OriginalReply0