Muhammadaftab10

Iran is now letting only selected countries pass through the Strait of Hormuz.
Here are the countries allowed through.
China. India. Pakistan. Turkey.
Malaysia. Iraq. Bangladesh. Sri Lanka.
Now here are the countries strictly blocked.
United States. Israel. Japan. South Korea.
Even the $2 million yuan fee that was rumored to buy passage? Not accepted. Those four nations are completely locked out.
This is the largest and most crucial toll gate on earth. Twenty percent of the world's oil flows through that narrow passage. And now Iran controls who gets through.
The message is clear.
Friends get oil. Enemies get nothing.
China and India are still receiving crude.
Their economies keep running. Their supply chains stay intact.
The U.S., Japan, and South Korea? Cut off. Israel doesn't produce oil but its allies are now blocked.
Oil prices jumped again on this news. Brent crude is pushing back toward $110. The war premium just came back.
This is no longer just a military conflict. It's an economic weapon. Iran is using the strait to punish its enemies and reward its allies.
The U.S. can't force its way through without escalating the war.
$ONT $SIREN $JCT #TrumpSaysIranWarHasBeenWon #US5DayHalt

I’m Writing What the Metrics Miss: A High-Performance L1 That Wins by Saying “No”
I’m logging this at 02:13, after another quiet alert cycle that didn’t escalate but didn’t feel benign either. The dashboards show stability—finality times tight, validator participation clean—but the real signal isn’t in the metrics everyone tweets about. It’s in how the system constrains behavior. This project, an SVM-based high-performance L1 built around zero-knowledge proofs, isn’t chasing throughput vanity. It’s building guardrails. And the more I trace the flows—tokens, sessions, permissions—the clearer it becomes: the design is less about speed and more about controlled exposure.
Tokenomics first, because everything downstream inherits its incentives. The supply schedule is front-loaded in perception but staggered in reality. Vesting cliffs are distributed across core contributors, early backers, and ecosystem funds, but the real pressure isn’t the cliffs themselves—it’s the predictability of their unlock cadence. Markets don’t fear dilution; they price certainty. What I’m watching is how unlocked supply behaves when it meets actual usage demand, not speculative liquidity. If emissions consistently outpace organic sink mechanisms—fees, staking lockups, or protocol-enforced utility—the token becomes a transit asset, not a destination. And transit assets don’t hold narratives for long.
The token is positioned as security fuel, and that framing matters. It ties value accrual not to abstract governance, but to enforced participation in network integrity. Staking here reads less like yield farming and more like assigned responsibility. Validators aren’t just earning—they’re underwriting the correctness of zero-knowledge verified execution. But responsibility only holds weight if slashing conditions are credible and enforced. I’ve been reviewing audit notes and internal risk committee transcripts; the debates aren’t about APR—they’re about fault domains. What happens when a proving system fails silently? What happens when delegation scopes are misconfigured? These are the questions that don’t show up on marketing decks but define long-term trust.
Adoption is where the narrative fractures from reality. Headline partnerships and ecosystem grants create surface-level activity, but I’m filtering for unprompted usage—developers building without incentives, contracts being called outside of coordinated campaigns. The signal I keep returning to is Project Sessions: enforced, time-bound, scope-bound delegation. This is where the architecture differentiates itself. Instead of users signing endlessly, exposing keys across fragmented interactions, the system constrains what a session can do and for how long. Scoped delegation + fewer signatures is the next wave of on-chain UX. It’s not just convenience—it’s risk compression.
At 2 a.m., when alerts trigger, they’re rarely about throughput degradation. They’re about permission anomalies—unexpected contract calls within valid sessions, edge cases where scope definitions blur. That’s where failure lives. Not in slow blocks, but in excessive trust surfaces. The industry’s obsession with TPS misses this entirely. A chain can process a million transactions per second and still fail catastrophically if key exposure is poorly managed. This design acknowledges that. It assumes users will make mistakes and tries to limit the blast radius.
Revenue flows are still early, but the structure is forming. Fees generated from execution—especially ZK proof verification and session management—feed into validator rewards and, in some cases, partial buyback mechanisms. I’m cautious here. Buybacks only matter if they’re tied to real usage, not treasury discretion. Otherwise, they become cosmetic. What I want to see is a direct, programmatic link between network activity and token demand—where increased session creation, proof verification, and contract interaction mechanically require more token throughput. Without that, revenue is just a number on a dashboard, not a force shaping price discovery.
Bridges remain the silent risk. The system’s internal logic is tight, but cross-chain interactions introduce external dependencies that no amount of ZK abstraction can fully neutralize. I’ve written this in the margin of every audit report: Trust doesn’t degrade politely—it snaps. One compromised bridge, one mispriced assumption about external state, and the entire security model inherits that failure. The project acknowledges this, but acknowledgment isn’t mitigation. I want to see stricter limits on bridged asset exposure and clearer isolation between native and external liquidity.
There’s also a tension between modular execution and settlement conservatism. The architecture leans into modularity—high-performance execution layers sitting above a more conservative base. EVM compatibility is treated as tooling friction reduction, not ideological alignment. That’s the right approach. It lowers the barrier for developers without compromising the underlying model. But it also introduces complexity. Every additional layer is another place where assumptions can drift. I’ve seen this before: systems that are technically elegant but operationally fragile.
What would change my thesis? Not announcements—commitments. On-chain indicators that can’t be faked. Sustained growth in session-based interactions without corresponding spikes in failed or reverted transactions. A rising ratio of fees derived from ZK verification relative to simple transfers. Validator set diversification without concentration creep. And most importantly, evidence that users are actually relying on scoped delegation in production, not just in demos.
I keep coming back to a simple idea. A fast ledger is impressive, but speed doesn’t prevent failure. Constraint does. The ability to say “no”—to reject actions outside defined scopes, to limit what a compromised key can do, to enforce boundaries at the protocol level—that’s what changes outcomes. This project is trying to encode that philosophy into its core. If it works, it won’t just be another high-performance chain. It will be a system that understands that the real threat isn’t latency—it’s permission without limits.
@MidnightNetwork #night $NIGHT

US President Donald Trump told CBS News in a phone interview that the U.S. war with Iran is “pretty much” complete and said he is considering “taking over” the Strait of Hormuz, while warning Tehran against disrupting the critical waterway. Commercial shipping through Hormuz—through which about 20% of global oil supply flows—has effectively ground to a halt, keeping markets focused on energy security risks. Following the interview, U.S. benchmark crude briefly plunged as much as 13.7% (about $13 a barrel) before paring losses; major U.S. stock indices closed higher after trading mostly lower earlier in the session.
#TrumpSaysIranWarWillEndVerySoon #Trump'sCyberStrategy