Spent the last hour poking around Dusk after wrapping the CreatorPad task, and the thing that actually stuck with me wasn't the mainnet numbers, it was the DuskEVM testnet going live on August 13. Dusk (@Dusk , $DUSK , #dusk ) has been pitching privacy preserving EVM compatibility for a while, so I went in expecting a fairly plug and play experience for anyone coming from Ethereum tooling.
That's not quite what I found. Deploying against a chain where confidential state and selective disclosure sit underneath the EVM layer means a lot of the usual assumptions about how you read transaction data don't transfer cleanly. Contracts behave the same on the surface, but debugging and indexing feel different once privacy is baked in rather than bolted on.
Small honest admission: I went in thinking "EVM compatible" basically meant "copy-paste your contracts," and that assumption didn't survive contact. It's testnet, so rough edges are expected, but it made the privacy-compliance tradeoff feel more structural than marketing copy usually lets on.
Curious whether that friction eases once tooling matures, or if it's just the permanent cost of doing privacy at the protocol level.
Did the DuskEVM testnet friction change how you see Dusk?
Spent an hour poking around TermMax's vaults last week and pulled up the DeFiLlama breakdown almost as an afterthought. That's when something stood out. TermMax, tagged #TermMax , is deployed on nine chains, Ethereum, Arbitrum, BNB Chain, Berachain, Robinhood Chain, BSquared, and a few others @TermMax has quietly added. On paper that reads as genuine multi-chain reach.
Then you check where the money actually sits. Ethereum alone holds 98.4% of the protocol's roughly $31M TVL. Everything else combined is rounding error. TVL is also down about 7.2% over the trailing 30 days, alongside roughly $19.9K in fees generated over that same window, small, but it's real usage, not just deployment noise.
I'd assumed shipping to nine chains meant liquidity would spread out reasonably evenly, or at least meaningfully. It doesn't. Curators and lenders on Ethereum are getting first access to whatever depth exists, while the other eight chains function more like optionality than active markets right now. Slightly humbling to watch a "multi-chain" label mean something so different in practice than what it implies on a landing page.
Not sure if that's a maturity curve other chains will eventually climb, or just where the actual demand lives.
What made me stop was the shape of TermMax’s fee activity, not the headline number.
After spending time with #TermMax and @TermMax , I checked how the protocol’s fees actually show up on-chain. The latest indexed snapshot shows $4,984 in fees over 24h, with $4,982 coming from Ethereum, while the full 7-day figure was only $5,954.24.
That was a small shift in how I was looking at it. I initially expected protocol activity to read more evenly from day to day. Instead, the fee transfers suggest the economics can be quite lumpy, with a large share of the observed revenue appearing in short settlement windows rather than as a smooth flow.
I’m still cautious about reading too much into one window. It tells me activity is happening, but not yet what specifically caused the concentration. I’d want to trace the underlying maturity and settlement transactions before calling it a trend.
What made me stop was seeing a 2,534,019 DUSK unstake land on the @Dusk mainnet, followed minutes later by a 109,925.797 DUSK withdrawal. Looking through Project Dusk and $DUSK , I expected the interesting part to be usage around the application layer. Instead, the clearest behavior sitting in front of me was still capital moving around the staking layer. #dusk
That changed my read a little. The network currently has a large active staking base, but individual position changes can still be meaningful enough to notice on the explorer. The transaction itself does not tell me why the holder moved the funds, so I’m trying not to turn one withdrawal into a bigger story than it is.
I also hesitated before treating the unstake as a bearish signal. It could simply be routine portfolio management, a provisioner change, or someone rotating liquidity elsewhere. That uncertainty is probably the useful part.
What I’m left watching is whether these large staking movements stay isolated, or start becoming a recurring pattern across Dusk’s active provisioners.
What do you think is driving these large $DUSK staking moves? 👀
Went into this CreatorPad task on TermMax expecting to write about TVL and market count. Ended up staring at a chain breakdown instead. #TermMax 's protocol-wide fees over the past 7 days sit at $3,098.68 and $2,999 of that came from the BSquared deployment. Not Ethereum, which holds 98.3% of @TermMax 's total value locked.
The part that made me pause: BSquared's TVL on the same dashboard currently reads $0. So almost the entire week's fee revenue traces back to a chain that, right now, has nothing sitting in it.
My first assumption was that fees roughly track locked capital, more TVL, more organic borrow/lend activity, more fees. This breaks that pretty cleanly. Whatever generated that $2,999 (liquidation, performance fee on a closed position, something maturing out) happened, extracted value, and left. The chain looks empty in the snapshot but wasn't inactive at all.
Makes me want to check whether this is a one-off event or a repeating pattern on smaller deployments. Haven't decided yet if that's a feature of fixed-term lending or just noise.
Deployed a small test contract on DuskEVM this week, not long after @Dusk pushed the testnet live, and the gas estimate confused me for a second. I'd budgeted for a normal EIP-1559 execution fee, the kind you get used to on any L2. The actual cost came in higher, and digging into it, I realized it wasn't a pricing bug, it was two separate charges bundled together. #dusk
DuskEVM splits fees into an execution fee and a data-availability fee, since the batcher has to post transaction data to DuskDS separately from the sequencer executing it. I'd read that in the docs earlier and skimmed past it. Paying for it directly made it click in a way the documentation didn't.
What struck me is that "fast inclusion" and "settled" are genuinely different moments here, and the fee structure is basically forcing you to pay for both stages up front, whether you think about them or not. I'd assumed L2 gas was just execution cost with a markup. Wrong assumption, apparently.
Curious whether that DA cost stays proportionally small once real volume shows up, or whether it starts to bite. $DUSK Which part surprised you most?
Deploying a small test contract on Dusk's testnet, live since August 10, felt like standard Hardhat work until the tx just... confirmed. No pending state, no mempool to watch, no waiting for gas competition to settle. For a second I thought my RPC was broken. It wasn't, DuskEVM simply doesn't run a public mempool. It's sequencer-only, by design. That's the detail from this CreatorPad task on @Dusk and $DUSK , #dusk that actually stuck with me.
I'd assumed EVM-compatible meant EVM-behaved, mempool included. Checking the deployment on the Blockscout testnet explorer confirmed it: transactions go straight from the batcher to execution, no visible pre-confirmation window. Coming from chains where you can watch a tx sit and sweat a little, this felt almost too quiet.
My first reaction was mild annoyance, I like seeing pending states, it's part of how I gauge network load. Then I reconsidered: no public mempool also means no front-running the usual way, which fits a chain built around privacy and compliance rather than open DeFi theater.
Still not sure how that holds up once real liquidity and more sequencer decentralization enter the picture. DYOR, this is just testnet behavior so far, not a settled property of the mainnet architecture.
Delegated a small amount of $DUSK through Sozu earlier this week to see Hyperstaking work in practice, and the part that actually stuck with me wasn't the yield, it was the wait. #dusk 's stake abstraction docs mention a 4,320 block maturity period before new stake goes active, which comes out to roughly 12 hours. I knew that going in, but watching it count down in real time on-chain hits different than reading it in a spec.
I'd assumed "delegated staking" meant near-instant participation, the way liquid staking on some other chains feels. @Dusk 's version is closer to a cooling-off period than a switch you flip. Nothing broke, nothing was hidden, it just made me sit with the fact that the network prioritizes settled state over speed.
Small reaction: I actually appreciated it more the longer I waited. It reframed the maturity window less as friction and more as a deliberate filter against stake churn, which fits Dusk's whole compliance-first posture.
Still not sure how that delay feels once volumes get heavier through Sozu. Worth watching.
Went to check a recent block on @Dusk and landed on DuskScan instead of the usual explorer, turns out it wasn't built by the core team at all. Some noodling around $DUSK pages later, I realized this thing shipped from a community dev, pieswap_dusk, and Dusk Foundation just reposted it like it was theirs to begin with.
Small detail, but it stuck with me. I'd assumed the tooling layer, explorers, dashboards, the stuff you actually use to verify what the chain is doing, was still mostly in-house here, given how compliance-heavy the project's positioning is. Turns out someone outside the foundation looked at the gap and just filled it, and the foundation didn't gatekeep it, just pointed people toward it.
Made me slightly reconsider what "auditable" actually depends on in practice. It's not just the ZK machinery, it's whether enough outside people care to build the boring verification tools nobody pays them for.
Still not sure if that's a sign of a healthy dev community or just one person carrying more weight than they should. Worth watching who maintains it in six months.
#dusk Who should build critical chain tools like explorers? 👀
Spent twenty minutes clicking through DuskScan, the new community-built explorer for @Dusk that went live this past week, before I noticed what I wasn't seeing. Blocks, provisioners, bridges, all laid out cleanly. But scroll into the transaction feed and most entries just say "Phoenix" with a fee attached. No sender, no receiver, no amount.
That's when it clicked for me. I'd assumed a fresh explorer for $DUSK meant more visibility into what the network's actually doing. Instead it mostly formalized how much is intentionally withheld by design shielded transfers don't leak anything just because there's a nicer UI in front of them.
Small reframe on my end: I came in expecting explorer to mean transparency tool in the usual crypto sense. Here it's closer to a shell showing you that activity is happening without telling you what it is. Not a flaw exactly, just a different default than I'm used to.
Still not sure who the primary reader of that feed is meant to be, provisioners checking uptime, or someone actually trying to audit flow. Open question for me right now.
#dusk Privacy or visibility — which matters more to you?
In 2022, BlackRock launched its private Bitcoin trust while retail was selling, then filed for a Spot ETF when almost everyone had given up on the market.
By the time the ETF was approved, Bitcoin had pumped from $38,700 to $126,000.
Retail bought after the news.
Now CLARITY keeps getting delayed.
What if institutions want cheaper $BTC before regulation opens the door for TRILLIONS of dollars to enter crypto?