AKASH KUMAR retweeted
Linda Noskova going to win wimbledon final🏆
#wimbledon #tennis
AKASH KUMAR retweeted
India’s IT ministry banned Telegram for one week because some users shared leaked exam questions.
This punishes 150M+ ordinary Telegram users in India — not the insiders who leaked the exam materials.
And the ban hasn't stopped anything. The leaks just moved to other apps.
Statement : Shutting down Telegram is a band aid solution and is a disproportionate answer to exam fraud
The Internet Freedom Foundation objects to the directions announced today in the National Testing Agency's press release on action against the Telegram platform. On the NTA's recommendation, the Ministry of Electronics and Information Technology has, under Section 69A of the Information Technology Act, 2000, restricted access to the whole of Telegram in India until 22 June 2026, and has separately ordered the platform to switch off message-editing for every Indian user until 30 June 2026. This is a blunt, nationwide measure aimed at the conduct of rampant fraud rackets, and on the Government's own admission is constitutionally incompatible.
At the outset it is important to note that Section 69A and the Blocking Rules of 2009 framed under it allow the Government to block access to specific “information” on a computer resource. They do not extend to switching off an entire intermediary, still less to ordering a company to redesign its product by removing a feature for a whole country. In Shreya Singhal v Union of India, the Supreme Court upheld Section 69A because it is narrow and hedged with procedural safeguards. Reading it to authorise shutting down a platform that lakhs use is an overbroad restriction by the NTAs own admission. For the message-editing direction the release identifies no source of power at all. If one exists, the order must say so.
The release argues against itself
A restriction on access has to be the least intrusive measure that achieves its aim as per the constitutional test of proportionality laid down in Justice K.S. Puttaswamy v. Union of India (2017) and applied in Anuradha Bhasin v. Union of India (2020). The NTA's own narration shows the block fails its nodal agency, the release says, “has secured the prompt take-down of a substantial number of Telegram channels, groups and bots”, and this targeted work “is the reason the harm caused by these rackets has been contained to the extent it has”. If channel level takedown contained the harm, the case for a blanket block collapses and hence the Government has reached for a heavier tool while conceding that a lighter one was working. The collateral cost sits on the record too as noted in the press release. The block, the NTA accepts, “affects lakhs of citizens who use the Telegram platform for legitimate personal, educational, professional and informational purposes”. The release also says there is "no such paper available outside the secured examination chain" and that “the security of the examination is unaffected by the action taken”. If the exam is secure and no leak exists, what is being suppressed is rumour, and rumour cannot justify closing a platform when specific blocking and criminal prosecution remain available.
Students use of Telegram
The block of telegram is reactive and ineffective and will punish ordinary users instead of addressing the systemic source of exam leaks. This blocking comes in the final days of NEET preparation, when thousands of students depend on Telegram for study groups, doubt-clearing, and shared resources. Also, it is important to consider that the source of exam papers leak will occur from inside the system, among insiders and across the printing and logistics chain, with the platform being the most downstream channel for distribution. Hence, switching off Telegram, is merely a deflection from the repeated failures that will continue while media attention is directed towards this Telegram ban.
Lack of transparency
At present only a press release from the NTA has been provided, which recommended the block but the reasoned order of MeitY, the authority that issued it, has not been released. The Anuradha Bhasin decision requires that orders restricting access be published so they can be tested in court. Here the order, and the reasoning of the committee behind it, stay out of view, and we do not know whether Telegram was heard at all. An announcement of a block is no substitute for an order the affected party can challenge.
Blunt to enforce and very easy to evade
Usually, app-level blocks run through IS-level DNS and IP filtering. They are over inclusive, sweeping in lawful use, yet simple to evade as a determined exam leak racket moves to a VPN or a mirror within minutes while ordinary users lose the service for a week.
We ask the Government to:
1) Publish the MeitY Section 69A order and the NTA recommendation behind it, with reasons;
2) State the legal basis for the message editing direction, or withdraw it;
3) Confirm whether Telegram was given a hearing under the Blocking Rules, and place the committee's record before any court that hears a challenge; and
4) Lift the platform-wide restriction and rely on the targeted takedowns the NTA itself credits with containing the harm.
We emphasise that the NEET (UG) 2026 re-examination is worth protecting and it concerns the future of lakhs of aspirants. It requires securing the entire process of examination rather than reaching for purported band aid solutions that instead cause more harm. The State cannot switch off a service used by lakhs to answer the wrongdoing of a few, and cannot do it through an order no one affected is allowed to read. On its own facts, the Government has done both.
New Delhi, 16 June 2026.
No complexity. No accident.
10/10 was caused by irresponsible marketing campaigns by certain companies.
On October 10, tens of billions of dollars were liquidated. As CEO of OKX, we observed clearly that the crypto market’s microstructure fundamentally changed after that day.
Many industry participants believe the damage was more severe than the FTX collapse. Since then, there has been extensive discussion about why it happened and how to prevent a recurrence. The root causes are not difficult to identify.
⸻
What actually happened
1.Binance launched a temporary user-acquisition campaign offering 12% APY on USDe, while allowing USDe to be used as collateral with the same treatment as USDT and USDC, and without effective limits.
2.USDe is a tokenized hedge fund product.
Ethena raises capital via a so-called “stablecoin,” deploys it into index arbitrage and algorithmic trading strategies, and tokenizes the resulting fund. The token can then be deposited on exchanges to earn yield.
3.USDe is fundamentally different from products such as
BlackRock BUIDL and Franklin Templeton BENJI, which are tokenized money market funds with low-risk profiles.
USDe, by contrast, embeds hedge-fund-level risk. This difference is structural, not cosmetic.
4.Binance users were encouraged to convert USDT and USDC into USDe to earn attractive yields, without sufficient emphasis on the underlying risks. From a user’s perspective, trading with USDe appeared no different from trading with traditional stablecoins—while the actual risk profile was materially higher.
5.Risk escalated further as users:
•converted USDT/USDC into USDe,
•used USDe as collateral to borrow USDT,
•converted the borrowed USDT back into USDe,
•and repeated the cycle.
This leverage loop produced artificial APYs of 24%, 36%, and even 70%+, widely perceived as “low risk” simply because they were offered by a major platform. Systemic risk accumulated rapidly across the global crypto market.
6.At that point, even a small market shock was sufficient to trigger a collapse.
When volatility hit, USDe depegged quickly. Cascading liquidations followed, and weaknesses in risk management around assets such as WETH and BNSOL further amplified the crash. Some tokens briefly traded near zero.
The damage to global users and companies—including OKX customers—was severe, and recovery will take time.
⸻
Why this matters
I am discussing the root cause, not assigning blame or launching an attack on Binance. Speaking openly about systemic risks is sometimes uncomfortable, but it is necessary if the industry is to mature responsibly.
I expect there may be significant misinformation and coordinated FUD directed at OKX in the near future. Even so, speaking honestly about systemic risk is the right thing to do—and we will continue to do so.
As the largest global platform, Binance has outsized influence—and corresponding responsibility—as an industry leader. Long-term trust in crypto cannot be built on short-term yield games, excessive leverage, or marketing practices that obscure risk.
The industry needs leaders who prioritize market stability, transparency, and responsible innovation—not a winner-take-all mentality where criticism is treated as hostility.
Crypto is still early.
What we choose to normalize today will determine whether this industry earns lasting trust—or repeats the same mistakes again.
Ethereum is for mobile payments.
42% of sub-Saharan Africa remains unbanked.
@ADI_Foundation is partnering with @MPesaAfrica to address this gap.
Our most significant African partnership to date aims to extend ADI Chain’s institutional-grade blockchain infrastructure to 60+ million users across eight African countries.
What this is going to enable:
→ Cross-border payment settlement via a dirham-backed stablecoin
→ Compliant blockchain systems designed for regulated environments
→ Digital rails for individuals and SMEs managing currency volatility
M-PESA has proven reach in emerging markets. ADI Chain delivers blockchain infrastructure tailored to their regulatory and monetary realities.
This is how ADI scales toward its goal: bringing 1 billion people onchain by 2030 - with Africa playing a central role.
That's different.
I saw $yUS and immediately said YES!
I'm officially registered for the Talus Airdrop.
Register before the Nov 28th cutoff & follow @TalusFoundation for the $US TGE date announcement!
teapawt.net/TalusFoundation/status…
1/2 Registration for the Talus airdrop is now live.
You helped bring the new agentic AI economy to the front pages. Now, it’s time to confirm your spot.
It's time to say $yUS
teapawt.net/TalusFoundation/status…
1
28
I just received a beautiful gift from ethOS! Check it out! @gifteddotart s.gifted.art/api/204c06a5
18
AKASH KUMAR retweeted
Ethereum is for shipping.
Here are 27 things the ecosystem launched, executed, and upgraded during the last few weeks.
0/ @OndoFinance launched Ondo Global Markets on @ethereum with 100+ tokenized U.S. stocks & ETFs. Having more traditional assets onchain means better liquidity, price discovery, and composability for builders.
1/ @PudgyPenguins launched the Pudgy Party mobile game app on iOS and Android, globally, expanding NFT IP to mainstream audiences.
2/ @AragonProject and @MetaLeX_Labs launched a new kind of onchain entity. BORGs are no-code, programmable legal entities that bridge the worlds of code & law. BORGs give onchain communities and DAOs new ways to interface with traditional legal structures.
3/ ChinaAMC, a major asset manager, launched on Ethereum. Institutional issuance on open standards increases liquidity and composability across the ecosystem.
4/ The Fusaka upgrade was successfully deployed to the Holesky testnet, marking the next milestone towards mainnet. Fusaka will support greater scale for Ethereum and L2s, while maintaining security and decentralization.
5/ @freedomfactory started shipping dGEN1, a mobile device built on Ethereum. It features a built-in non-custodial wallet, a native light client, xmtp messaging and native signing, so paying, minting, and using dapps works out of the box.
6/ Stablecoin transfer volume on @ethereum surpassed $5T in Q3 '25, an all-time high.
7/ Layer 2 (L2) networks on Ethereum processed 25M transactions in a single day, an all-time high.
8/ Ethereum L2 @worldnetwork hit 16M verified users on their platform, an all-time high.
9/ Stablecoin supply on @Arbitrum One reached $9B, an all-time high.
10/ The @Aave protocol now holds more assets than the 36th largest bank in the United States.
11/ @Artblocks_io artists have raised a total of $50M+ from their work for charity. Showing how culture, transparency, and impact can be supported by open protocols.
12/ In partnership with @Securitize, @FGNexusio announced it will be the first NASDAQ-listed company to bring dividend-paying preferred equity $FGNXP fully onchain and on Ethereum.
13/ In collaboration with Ethereum L2 @Base and @Coinbase Ventures, @YCombinator announced ‘Request for Startups: Fintech 3.0’ to support the next era of finance onchain.
14/ @Gizatechxyz, in partnership with @Pendle_fi introduced Pulse, the first agent that autonomously optimizes your PT portfolio.
15/ @Celo mainnet executed the ‘Ice Cream’ hardfork, activating @eigencloud’s EigenDA v2, reducing confirmation latency, improving performance, and paving the way for OP Succinct Lite integration.
16/ @AmericanExpress rolled out in-app passport stamps on @Base, giving travelers new ways to collect, own, and share their journeys.
17/ DeFi lending is actively rolling out on @Coinbase, powered by @MorphoLabs and @SteakhouseFi and running on @base. Coinbase users can lend their USDC and earn onchain, transparent, and trustless yields.
18/ @PrimeIntellect launched Reserved Instances, offering a way to pre-book guaranteed GPU capacity. Predictable compute offers faster ZK proving and onchain AI, pushing L2s toward real-time and safer apps.
19/ @YunfengGroup purchased 10,000 ETH as a ‘reserve asset’, strengthening network neutrality, and supporting the adoption of onchain finance in Asia.
20/ @OctantApp, in partnership with the @EthereumFndn Funding Coordination Team, selected 30 onchain creators to provide $1M in total funding to. The ecosystem will be able to vote on how funds are allocated.
21/ @Cloudflare launched x402 Foundation in partnership with @Coinbase, with support for x402 transactions.
22/ $1.3B was streamed onchain with @Superfluid_HQ, 2x what it was just ~1 year ago.
23/ @Safe hit 600M+ transactions, a milestone for self-sovereignty and programmable ownership.
24/ Ethereum saw ~$2.5B worth of tokenized gold, demonstrating that real-world assets (RWAs) are moving to Ethereum.
25/ In 9 months, @ether_fi Cash issued 11,280 cards and processed $38M across ~410k transactions.
26/ @Krakenfx announced that xStocks are coming to Ethereum via @xStocksFi, unlocking a new wave of opportunities for tokenized stocks and ETFs to be integrated across the network.
AKASH KUMAR retweeted
#ZKsync just shared a genuinely impressive load test with the Atlas update. Hitting 19,000 TPS, staying stable around 648 million gas per second, and delivering 0.3 to 0.46 second inclusion times pushes the bar for L2. On top of that, processing roughly 1,900 oracle price updates per second on-chain shows the system is ready for real-time flow. With sequencer improvements, the goal is clear: Web2-like latency and much higher throughput. The data makes it plain that ZKsync is backing its scale and speed claims.
Why it matters: it opens the door wide for gaming, HFT-style DeFi, real-time finance, and oracle-driven automation. With this update, ZKsync is not just saying “we are ready,” it is showing where things are headed. The message to builders is simple: ship your product, we will handle the load and the latency.
Congrats @zksync @gluk64 @Ozhar @portport255 👏👏👏👏👏👏🙏🙏
AKASH KUMAR retweeted
On Tempo, permissionlessness, L1 vs L2
Tempo will be a permissionless chain. On day 1, anyone will be able to deploy a token, and anyone will be able to transact on the chain. Some projects think that attracting real-world usage and serious institutions requires giving up on base layer neutrality. We do not think that, and that's not how we're building Tempo.
The plan for Tempo is to have permissionless validation and permissionless smart contract deployment as well as permissionless usage: just like Bitcoin, Ethereum, Solana, etc. We’ll start with a permissioned validator set to get going and decentralize further from there.
We’re building in features to make it easy for entities interacting with the blockchain (like asset issuers, money transmitters, etc.) to comply with their relevant obligations, but the base layer will remain neutral. This is a principle we feel incredibly strongly about (see: paradigm.xyz/2022/09/base-la…).
As many parts of the mainstream world look to adopt crypto, we think there is a risk that they adopt permissioned systems. Our goal with Tempo is to help onboard them onto crypto rails that solve specific payments needs while still being truly permissionless.
—
Why L1 rather than an Ethereum L2?
At Paradigm, we are heavily invested, both intellectually and literally, in the Ethereum ecosystem. We will continue to help it scale, and invest in and support companies building on Ethereum. We are also extremely excited about single-sequencer L2s for many use cases, including trading.
But building a network for global payments will require bringing together thousands of partners that may not trust us, or Stripe, or anyone as a platform. We think a decentralized validator set—for the chain itself—is a necessary requirement for those partners, and to ensure that the chain is unquestionably neutral in the long run.
From an operational perspective, we feel urgency to build for the demand that’s coming and want fewer dependencies, including on the rate of Ethereum L1 progress. With Tempo, we tried to remove all crypto tribalism and alignment games from our thinking and just focus on building the right product for crypto payments.
At a technical level, we are prioritizing attributes like fast finality (L2s are generally only as final as the underlying L1), multiple validators (vs. single sequencer), and custom transaction lanes and gas pricing. Some of these are technically possible for an L2, but could be complex, slow to implement, and/or introduce many external dependencies. Tempo is stablecoin-focused, so interoperability through native issuance is more relevant to us than the native bridge to Ethereum that L2s have.
We aren’t Bitcoin, Ethereum, or Tempo maximalists. We’re maximalists for permissionless crypto. We want Ethereum L1 to scale, and we want L2s to thrive. We love Bitcoin as a monetary asset. We find substance in Solana, Hyperliquid, and many other ecosystems. We want to ensure real-world payment flows happen on crypto rails, and that’s why we’re building Tempo.
AKASH KUMAR retweeted
The majority of L2 assets don't inherit Ethereum security even if the L2 is Stage 2.
This is a challenge we don't talk enough about in Ethereum. We should face it head on.
Below is a compilation of L2 assets compiled by @hazeflow_xyz based on @l2beat data.
Only the canonically bridged assets inherit Ethereum security guarantees. That's only 34% of L2 assets.
The other 66% rely either on a third-party bridge or the L2 itself.
Canonically bridged assets (34%) = Ethereum
Third-party bridged assets (38%) = Not Ethereum
Natively minted assets (28%) = Not Ethereum
In order to inherit Ethereum security the asset must be minted on Ethereum L1 and bridged natively.
More canonically bridge assets = L2 is more Ethereum
Less canonically bridge assets = L2 is less Ethereum
There's an incentive alignment problem here - an L2 may want more natively issued assets in order to maintain a valuable moat. Additionally, there's UX and cost advantages to minting on L2.
Based rollups paired with asset issuance on the L1 provide a strong solution to the problem.
In the least - asset issuance on L1 should be the strong default. But it's not entirely clear how this gets standardized or if it's practical.


























