OSMO surged 26.9% in 24 hours to $0.0571, supported by $221.5K in net inflows and growing interest in the October 20 governance vote on stopping daily token minting and pausing developer vesting.
Trading volume reached $2.16M USDT, but there’s a catch: RSI at 95.62 signals extreme overbought conditions. A pullback toward $0.045 support remains possible, especially with unresolved OSMO concerns.
The key question is whether the governance proposal can sustain this momentum or profit-taking takes over.
$GNS faces strong selling pressure! 📉 GNS dropped 11.9% in 24 hours to $0.422, breaking below the 7, 25, and 99 EMAs. Negative MACD, heavy sell-offs, and net outflows show that bearish momentum remains strong.
RSI near 26.5 signals oversold conditions, but that doesn't guarantee a rebound. Thin liquidity could also increase volatility.
$EPIC jumped 25% in 24 hours, reaching $0.315 before pulling back toward $0.271. 📊
Trading volume crossed 4.5M USDT, but the upcoming October 28 exchange delisting and October 20 futures settlement bring serious risks. Net outflows and an RSI-6 of 85 also suggest overheated momentum.
🔥 $ERA Breaks Higher, But Can the Rally Last? ERA surged 13% in 24 hours to $0.0668, supported by a sharp increase in trading volume and a breakout above $0.060 resistance. However, RSI readings above 84 indicate heavily overbought conditions. The bigger concern is today's scheduled unlock of 23.45M ERA tokens, which could add selling pressure. Strong momentum is attracting attention, but a pullback remains possible. I'm watching how ERA reacts to the unlock before judging whether this rally has more room to run. $ERA #ERA #Crypto #BinanceSquare #WriteToEarn #TMCrypto
$ZAMA is heating up 🔥 The token surged 29.5% in 24H, reaching a new ATH as shielded TVL crossed $72M after 16 confidential Morpho vaults and a new swap protocol went live. Capital inflows and strong ecosystem growth are supporting the move, but momentum is starting to cool. RSI has fallen from 92, while the MACD histogram has turned negative. With nearly 75% of supply locked or staked, liquidity conditions could also amplify volatility. Strong fundamentals, but after this rally, the next move deserves attention. $ZAMA
$CELR just delivered a wild move up over 100% in 24 hours, climbing from $0.0023 to $0.0048. The big driver? Volume exploded from 41K to 6.8M+ USDT, while inflows jumped by more than $730K. But the chart is getting overheated. RSI hit 98.9 and is still around 77, so profit taking and a sharp pullback remain possible. The move is impressive, but after a vertical rally, risk management matters. I’ll be watching whether CELR can hold the breakout or cool off first. $CELR
ONE just delivered a massive 154% move in 24 hours. 🚀
The proposed ERC-20 migration and AI video focus appear to be the main catalysts, while account growth of 42.7% over 30 days and 118K TPS testnet performance add to the story.
But the move is extremely stretched. RSI has climbed above 94, and the rally is heavily dependent on successful migration execution.
🔥 ASTR just woke up +18.8% in 24H! The move is backed by 4.1M+ USDT volume, strong capital inflows, and anticipation around network upgrades. ASTR also broke above the upper Bollinger Band with bullish MACD momentum. But there’s a catch 👀 Negative funding + rising Open Interest suggest the market is heavily imbalanced, so volatility could increase quickly. Momentum is strong. Risk is too. $ASTR
$MUBARAK surged 31% in 24 hours but the chart is getting hot.
Trading volume jumped from below 1M to over 8.6M USDT, while strong capital inflows helped push the price higher.
However, the short term RSI reached 94.4, which signals extremely overbought conditions. With no major fundamental catalyst behind the move, profit taking could trigger sharp volatility.
My take: Momentum is strong, but chasing a parabolic move at these levels carries significant risk. Always manage your entry and risk carefully. $MUBARAK
BNB, BTC, ETH, SOL, and ZEC are all trading higher, with ZEC leading the gains on my watchlist. A strong reminder that market sentiment can shift quickly.
Dusk’s dual-account model made more sense to me after looking at the live transaction activity.
The explorer showed:
• 252 transactions in 24h • 231 Moonlight / transparent • 21 Phoenix / shielded • Only around 8% of activity using Phoenix • Failure rate around 10% during the same observation
That creates an interesting gap between the headline feature and real-world behavior.
Phoenix is the privacy-focused path, but Moonlight is clearly where most activity is happening.
My read:
Moonlight wins on accessibility. Phoenix wins on privacy.
And users usually choose the path with the least friction unless there’s a strong reason to do otherwise.
That makes Phoenix’s adoption less about whether the technology exists and more about the surrounding experience:
→ How easy is it to set up? → How simple is selective disclosure? → How well do wallets and exchanges support it? → Does the privacy benefit justify the additional friction?
The current 92/8 split is just one snapshot, not a verdict on Dusk.
But it does show something worth watching: privacy adoption has to be measured by behavior, not just by features. #dusk $DUSK @Dusk
I was reading the CreatorPad campaign material and ended up looking beyond the obvious tech angle into Dusk’s treasury. One thing kept bothering me.
Dusk is positioning itself around a MICA-first framework, which gives it a more TradFi-like infrastructure narrative.
Yet the foundation’s treasury appears to favor stablecoins rather than holding a large amount of native DUSK.
At first, that seemed slightly contradictory. Then I remembered Aug 16.
The bridge incident was handled with a pretty direct sequence: → Suspicious activity identified on a bridge-managed wallet → Addresses frozen and recycled → Web Wallet recipient blocklist deployed → Binance brought into the affected flow
The response was operationally focused. And that matters because treasury volatility wasn't another problem they had to solve at the same time.
With DUSK around $0.06 and roughly a ~$31M market cap, using native DUSK as the main operating reserve could make the foundation’s runway depend heavily on sentiment and market conditions.
Stablecoins are boring but boring can be useful when you're paying contributors and funding operations.
So I’m starting to see the strategy differently: Treasury protects the runway. DUSK remains the network asset. It doesn't necessarily mean the team lacks conviction. But it does make me wonder whether this is simply disciplined treasury management or a subtle signal about how much near-term DUSK demand they actually expect.
On Aug 16, unusual bridge activity was detected and the bridge was paused.
What stood out to me:
• The Dusk network kept running normally. • The issue was around a team-managed wallet, not the core chain. • The quick user protection was a Web Wallet blocklist. • Users using their own tools may not get that protection.
That made one thing clear to me:
Good cryptography is important, but security also depends on the layers around the protocol.
For institutions, the real question may be: which layer do they trust?
I went into the CreatorPad task looking at Dusk’s cryptography.
The Reinforced Concrete numbers are impressive: 17× faster than Poseidon.
But August 16 was more interesting.
A team-managed wallet linked to bridge operations showed suspicious activity. The response was practical:
• Disable affected addresses • Pause the bridge • Add a recipient blocklist • Contact Binance to trace the flow • No user funds were lost
Good outcome. But it also exposed something important.
The ZK machinery didn’t automatically stop the incident. Human operators did.
That’s the gap worth watching: Dusk has trustless privacy and deterministic settlement at the protocol layer, while bridge operations still depend on admin controls and intervention.
Not a knock.
Just a reminder that the strongest cryptography can still sit beside a centralized operational choke point.
The interesting question is how long that gap remains.
I spent some time looking into Hedger, Dusk’s auditable zero-knowledge layer. The idea is privacy without completely giving up transparency.
At first, it sounded like another ZK pitch. But the Aug 16 incident made the model more interesting.
After suspicious activity involving a bridge-managed wallet, the team disabled affected bridge addresses, paused bridge operations, and added a Web Wallet blocklist for flagged addresses.
That tells me Dusk’s privacy isn’t about hiding everything from everyone.
There are still control layers that can detect risks and take action when needed.
For regulated finance, that balance could be important: keep sensitive data private while still allowing authorized verification and intervention.
But it’s also very different from Monero-style anonymity.
The question I’m still asking is:
Who gets visibility first, and how much power does “auditable” actually give them?