DuskEVM testnet just went live, and it's a fairly deliberate bet: instead of asking developers to learn a new stack, it hands them the one they already know. Solidity, Hardhat, Foundry, standard EVM wallets all work as-is, because DuskEVM runs on OP Stack and speaks the standard Ethereum JSON-RPC interface. What changes is underneath. Execution settles back to DuskDS, Dusk's own consensus and data-availability layer, and gas is paid in DUSK instead of ETH. For teams building DeFi protocols or tokenized asset platforms, that's the real pitch: you don't trade tooling maturity for settlement guarantees, and you're not locked into a bespoke chain most auditors and exchanges have never touched. Since DuskEVM sits next to Hedger, apps that later need confidential transaction flows have a path there too, without leaving the EVM environment they started building in. #dusk $DUSK @Dusk
Most privacy chains force a choice: hide everything, or expose everything for compliance. Dusk was built to avoid that trade-off entirely. Transactions are shielded by default through zero-knowledge proofs, so balances and counterparties stay private on a public ledger, but designated parties can still reveal exactly what a regulator needs, without breaking confidentiality for everyone else. That distinction sounds small but isn't. Traditional finance can't run on a chain where every trade is visible to competitors, and it can't touch one that's opaque to auditors either. On top of that, Dusk's consensus (Succinct Attestation) gives deterministic finality, settlement in seconds rather than probabilistic confirmations, which matters when the assets in question are securities, not speculative tokens. It's a narrow, unglamorous problem to solve. But it's the one that actually decides whether institutional capital shows up onchain. #dusk $DUSK @Dusk
Crypto VCs Selling “Freedom from Big Tech” While Building the Next Cartel The pitch is everywhere these days. OpenGradient, backed by Balaji Srinivasan, Illia Polosukhin, and Sandeep Nailwal, says it’s here to free AI from Big Tech. No more getting cut off because some corporate policy team in California woke up on the wrong side of the bed and decided your project doesn’t fit their values. Sounds like progress on the surface. Until you look at who’s actually stepping in to run the new system. Same class of crypto insiders who already shape the narratives across Web3. Who move liquidity when they want. Who steer governance votes when it actually matters. “The people who built the previous system are now selling you the escape pod — and keeping the keys.” That line just sits there. Because it’s hard to argue with once you’ve seen the pattern a few times. New branding. New promises about user sovereignty and decentralization. Same faces from the last cycle ending up with the real leverage. The escape pod looks shiny. You just eventually notice who’s still holding the flight controls.
Verifiability Theater: Proofs That Prove Nothing About Control
OpenGradient markets zkML + TEE as the fix for untrustworthy AI. Cryptographic proofs that the inference ran correctly. It sounds like real accountability on paper. But the power? It stays with the node operators. EigenLayer restakers. Whoever controls the largest $OPG stakes. They decide how the network actually runs. Verifiability of the inference itself doesn’t extend to verifying who runs the network or who might censor outputs. Those are different questions. And that’s the part nobody wants to talk about much. They gave you cryptographic proof that the answer is correct but not who decided what question you were allowed to ask.” That line gets right to it. Honestly, it’s mostly theater. The proofs handle one narrow slice. The bigger issue of concentrated control over the system? Still sitting there, pretty much untouched.
When I dig through the old training archives from the 2020s, one pattern still surprises me. Specialized models used to die with their creators. A small team would train something sharp for coordination problems, push a few updates, and then everyone would scatter. The clever fixes and the quiet little regressions all faded into private repos or half-forgotten conversations. At best you had stories passed around. Nobody could go back and see why version three suddenly handled certain edge cases so much better than version two. OpenLedger changed that. Its Datanets turned every data contribution and every fine-tune into part of a permanent on-chain record. The full lifecycle became visible. You could trace exactly how a model evolved across trainers who had never met. That provenance turned these models into multi-generational artifacts whose improvement history stayed legible long after the original team had moved on. I often picture those early occasional contributors uploading a handful of real examples late at night and simply closing the tab. No constant checking back. The Datanet kept their work anchored. Later researchers could pull up the whole chain and see precisely where the model sharpened or drifted. The old problem of lost institutional knowledge finally started to disappear. That one shift ended up mattering more than people expected at the time. Once provenance became standard, specialized models stopped being disposable. They began carrying real, queryable memory across generations. And for the first time, they could actually outlive their creators.
It was late one night when I finally hit upload on this small batch of examples I’d been sitting on for weeks. Just a handful of real edge cases from the coordination problems I’ve actually run into while building. Nothing glamorous at all. I clicked the button, saw the confirmation pop up, and closed the tab. No second window left open. No little voice in my head saying I should check back tomorrow. And the strange thing was, I might never look at it again. And for once, that felt completely okay. It used to wear me down pretty badly. I’d put real effort into gathering useful data from messy on-chain situations I’d lived through, drop it on those other platforms, and then the second, much more annoying job would start. You had to keep logging in every few days to see if anyone had noticed it, maybe reformat the examples or repost them just so the contribution wouldn’t sink into obscurity. If real work picked up or life got in the way, your contribution just faded away like it had never existed. I lost count of how many times I began with genuine energy, shared something I thought was decent, and then slowly stopped showing up altogether. That constant churn wasn’t some abstract statistic you read about. It was me, repeatedly burning out and walking away from platforms that demanded more attention than I could give. This time it felt different almost from the moment I finished the upload. I had spent some proper time curating those examples specifically around how decentralized systems actually deal with messy coordination issues in practice. I pointed them toward one of OpenLedger’s Datanets, the one focused on infrastructure knowledge. The upload process itself was straightforward and clean. Once the data was verified, it went on-chain and became part of this living, shared pool that anyone could build on. What really hit me later, once I’d stepped away, was the quiet realization that my contribution would simply stay there. It didn’t need me hovering over it or constantly tending to it. The Datanet keeps it linked and discoverable in a way that feels fundamentally different. When teams later come along to train or fine-tune models using that data, the attribution flows properly without me having to do any platform-specific dance to keep it relevant. No endless maintenance. No trying to game an algorithm. It just exists there as part of the permanent record. I’ve caught myself imagining how this could play out down the line. Maybe six months from now, or even a couple of years later, some team is deep into solving certain on-chain coordination failures. They pull data from that Datanet, and a couple of my specific examples quietly help shape how their model reasons about those situations. I probably won’t even hear about it. I won’t be refreshing any dashboards or trying to stay visible in some feed. But the contribution keeps quietly working in the background. That kind of persistent presence, without any ongoing pressure from me, feels strangely freeing in a way I wasn’t expecting. As an occasional contributor, my attention and time are pulled in a dozen different directions at once. I show up when I actually have something meaningful to add, not because the system forces me to maintain some kind of consistent profile or presence. The old platforms made you treat contribution like a part-time job you could never really quit if you wanted your work to matter. With OpenLedger it finally feels built for people who work the way I do. Your work can stand on its own, properly anchored to the on-chain history, and continue creating value and generating proper attribution long after you’ve moved on to whatever comes next. I keep thinking back to that specific moment right after I closed the tab. It wasn’t that I suddenly didn’t care about the contribution anymore. It was more like relief washing over me. My examples are sitting there now in the Datanet, becoming part of this larger, genuine effort to build better AI infrastructure from real community-sourced data instead of synthetic or heavily filtered stuff. And the best part is I don’t have to keep hovering over them or keep proving their worth every few weeks. I can finally step back and actually trust the system to do what it was designed for. The idea that I might never look at that contribution again doesn’t feel like walking away or being irresponsible. It feels like the first time I’ve found a way to contribute that actually fits how I naturally work and live. #OpenLedger $OPEN @OpenLedger
What’s been interesting about the recovery back to $680 is that the move doesn’t really look retail-driven.
Retail participation has mostly remained flat throughout the structure, while the majority of the buying has continued coming from mid-sized flows.
At the same time, larger institutional-sized flows dropped during the correction, but have slowly started turning back upward. Interestingly, the low in institutional flows also lined up almost perfectly with the local low in price.
That creates a very different backdrop from the type of euphoric breakout conditions people usually expect near reversals.
So far, the move has looked more like sustained positioning coming back into the chart rather than a retail-led momentum chase.
Now ZEC is attempting to reclaim the November high region after breaking above $640.
If larger flows also start pushing back toward their prior highs above this region, then the probability of continuation higher starts increasing pretty quickly from there.
Lately I’ve been thinking a lot about something that’s been bothering me in the AI and Web3 space. We always talk about “openness” like it’s automatically fair and the best thing ever. Everyone assumes any dataset can be freely mixed and reused without any problem. But honestly, what if this casual blending is quietly breaking the incentives we all claim to care about? The key point is attribution. There’s data that’s completely free anyone can use it without tracking or strings attached. Then there’s data that carries real economic rights. It stays linked to the original creator even after it’s been used in a model. When we treat both the same way, the people who put in high-quality work never get properly recognized or paid. Slowly the whole system starts losing the good contributions it needs. OpenLedger actually draws a clear line with their Proof of Attribution system. Some datasets stay fully open for broad use. But others keep their economic lineage intact on-chain. When a specialized model pulls value from those, the protocol knows exactly whose data mattered and routes the rewards accordingly. It’s not locking data away it’s making sure real ownership doesn’t just disappear. I’ve been following this closely in my own research and contributions. The more I see it in action, the more I realize: true openness doesn’t mean pretending all data is identical. The distinction isn’t a limitation. It’s what actually lets meaningful contributions survive and keep the ecosystem healthy in the long run. What do you guys think? Do you believe strong attribution is necessary for the future of data markets, or should everything just stay completely open? #OpenLedger $OPEN @OpenLedger
We took out the first IRL target so I TP' the longs there.
Bitcoin also took out the 77.8K previous daily high, which means the probability of holding the 76.5K PDL increased significantly.
On the bigger picture, we lost the previous weekly low already, and now filled the 78.2K weekly imbalance.
I unfortunately missed the A+ short entry due to the timing (I was asleep).
I'm not FOMO'ing into the short and await new setups to be created.
This last pump pulled a lot of late and fomo-longs into the market + volume decreased.
So a deeper pullback wouldn't be surprising, and if I get my trigger after holding the 76.5K PDL I probably long it as a rangetrade.
My ideal short scenario would be around 79K, but I don't want to predict. So if price keeps dumping and loses the PDL, I'll look for late short entries on the retest.
I'm trading in between bullish and bearish forces here, so not rushing anything.
The more I look at this range, the more I think the market maker is trying to solve the same problem that created the collapse from $2.40 to $0.41.
ASTER was violently overleveraged during that entire move.
Every bounce got chased by FOMO traders who thought it was going to rip to $4.
Every dip got knife-caught.
Every small rally became another excuse for people to pile into leverage before getting flushed again.
That type of positioning is exactly what turns a normal downtrend into a liquidation cascade.
So now, instead of allowing one side of the book to get dangerously crowded again, the market maker keeps forcing both sides to reset inside the same range.
Breakout longs above resistance get faded straight back into mid-range, while late shorts below support get squeezed back upward.
Over and over again.
It's dirty on the surface, but structurally, there's some sense to it.
Market makers generally care about two things inside larger ranges:
1) Building liquidity 2) Removing crowded positioning
And the longer this range keeps producing failed breakouts and failed breakdowns, the more leverage gets wiped from both sides of the book, and the more traders will lose interest in forcing leveraged positions.
And by doing that, the technical structure actually becomes cleaner and less vulnerable to a violent liquidation cascade during a larger market correction.
So while the price action has been quite inorganic, this is likely the exact process Aster is engineering after how aggressively leveraged the last major decline became.
How OpenLedger’s Proof of Attribution Saved My Datanet from Bad Data – Real Story from Inside
I still remember the exact ping on my dashboard that morning. It was around 9 AM UTC on January 15th. I had been grinding hard on our Datanet inside OpenLedger the one I co-own and actively contribute to. We focus on specialized market behavior data for training leaner finance models. A fresh batch of contributions had just landed the previous day. Within 24 hours, one of our fine-tuned models started acting weird. Predictions that used to hit with 92% accuracy suddenly dropped to around 67%. Confidence scores tanked, and the outputs got noticeably noisier around the edges. I was like, “What the hell is going on?” In any normal data marketplace I’ve used before, this would’ve been the start of a slow, silent death. Bad data sneaks in, nobody traces it back, and the whole pool slowly becomes useless while the contributor already cashed out. No accountability, just gradual quality collapse. But OpenLedger is built different. I pulled up the attribution chain in literally 30 seconds. Thanks to their Proof of Attribution system, every single data point is linked on-chain to its real impact on model performance. I could see exactly which contributor’s upload was killing the feature importance scores and directly causing the drop in inference quality. The rewards calculation didn’t lie either — that batch’s impact score went straight down, and their expected payout got withheld accordingly. The contributor messaged me soon after. He sounded surprised and a bit frustrated: “I thought it would pass the basic checks like everywhere else.” I sent him the before-and-after graphs, the exact degradation numbers from our latest training runs, and the attribution report. No hiding. No excuses. The system made the cost personal and immediate. That conversation actually changed how I see the whole network now. As both owner and regular contributor myself, I’ve noticed contributors are double-checking their work way more carefully. Some even started self-auditing before uploading because they know the link to real model outcomes is visible to everyone. Validators are flagging issues earlier too. It created this quiet self-policing thing that generic marketplaces can never copy. I’ve contributed my own datasets to other Datanets in the OpenLedger ecosystem, and the difference is night and day. When I upload clean, high-signal data, I literally watch the attribution rewards flow in based on actual usage during inference calls. When someone cuts corners, the visible feedback loop pushes them to fix it instead of polluting everything. Of course it’s not perfect yet — there are still some edge cases and healthy debates about measuring degradation. But after watching this play out week after week, I’m convinced: visible impact measurement is the real game-changer. It turns potential adversaries into people who actually care about the network’s health because their own rewards are tied directly to it. This is exactly why I’m still fully committed to growing our Datanet. The old way let quality die from a thousand invisible cuts. Here, the fight happens in the open — and we’re actually winning it. What do you guys think? Have you experienced something similar in other data platforms? #OpenLedger $OPEN @Openledger