This morning, I got almost nothing done because I kept digging around the new DuskEVM testnet from @Dusk
DuskEVM officially went live on August 10, and most of what I saw mentioned was Solidity and Hardhat support. That’s pretty solid, but honestly, it wasn’t enough to keep me digging.
What really caught my attention was how DuskEVM separates execution from settlement. Contracts are processed by the sequencer on DuskEVM, while transaction data is still batched back to DuskDS as blobs, and the proposer anchors the state commitment there. Computation happens on DuskEVM, while finality is tied to the base layer.
Another detail I found interesting: gas is paid in DUSK. The token has to be bridged from DuskDS to DuskEVM first, which means liquidity has to enter the system before the first contract can even be deployed.
The more I thought about it, the more I kept coming back to this. Before a developer writes their first line of Solidity, actual #dusk has already had to be bridged onto DuskEVM. I like that because it’s not just a “user experience” feeling or an adoption story-the transaction has actually happened.
Out of curiosity, I checked the testnet explorer and found contracts had already appeared a few days ago. DuskEVM is only six days old, so early activity like that, to me, can’t really be called “nothing.”
Still, I don’t want to jump to a conclusion. I keep wondering whether this settlement model will actually change how NPEX-style assets operate once they enter the EVM, or whether I’m simply reading too much into an OP Stack-like pattern.
Right now, I lean toward the former, but I don’t have enough data to say that confidently.
What I’m most curious about now: have any developers already deployed products on it, or is everyone still just reading the docs like me?$DUSK $AEON $STRIKE
What’s happening on DuskEVM?
DuskEVM officially went live on August 10, and most of what I saw mentioned was Solidity and Hardhat support. That’s pretty solid, but honestly, it wasn’t enough to keep me digging.
What really caught my attention was how DuskEVM separates execution from settlement. Contracts are processed by the sequencer on DuskEVM, while transaction data is still batched back to DuskDS as blobs, and the proposer anchors the state commitment there. Computation happens on DuskEVM, while finality is tied to the base layer.
Another detail I found interesting: gas is paid in DUSK. The token has to be bridged from DuskDS to DuskEVM first, which means liquidity has to enter the system before the first contract can even be deployed.
The more I thought about it, the more I kept coming back to this. Before a developer writes their first line of Solidity, actual #dusk has already had to be bridged onto DuskEVM. I like that because it’s not just a “user experience” feeling or an adoption story-the transaction has actually happened.
Out of curiosity, I checked the testnet explorer and found contracts had already appeared a few days ago. DuskEVM is only six days old, so early activity like that, to me, can’t really be called “nothing.”
Still, I don’t want to jump to a conclusion. I keep wondering whether this settlement model will actually change how NPEX-style assets operate once they enter the EVM, or whether I’m simply reading too much into an OP Stack-like pattern.
Right now, I lean toward the former, but I don’t have enough data to say that confidently.
What I’m most curious about now: have any developers already deployed products on it, or is everyone still just reading the docs like me?$DUSK $AEON $STRIKE
What’s happening on DuskEVM?
🛠️ Builders are deploying
50%
📚 Still reading docs
25%
🔍 Too early to tell
25%
4 votes • Voting closed