Learn NEAR Club | (L)Earn🕺
5.6K posts

Learn NEAR Club | (L)Earn🕺
@LearnNear
Learn with responsible and verifiable AI. Powered by open sourced @NEARprotocol @near_ai and @WordPress.


Quantum computing is a threat to every blockchain protocol. NEAR's architecture already makes accounts and assets more quantum-secure than most chains. The team is now adding post-quantum cryptography to secure NEAR and the wider Intents ecosystem. Here's what's underway 🧵


90% of exploited smart contracts were previously audited. The industry's response was to do more audits. At some point you have to ask different questions.



We are pleased to confirm that ALL external account balances have been fully restored and operations are back to normal. We deeply appreciate the support and advice from the community that helped us to resolve this quickly. Special thanks goes to @MEXC for prompt freezing of the attacker’s account and to @rhea_finance for coordinating the response across @NEARProtocol ecosystem. More details on the incident below.


x402 broke a million transactions in the last two weeks alone, as endpoints keep going live across the ecosystem. Yet, a number of them appear to be unauthorized wrappers of services whose terms EXPLICITLY prohibit reselling. Right now there's no way to tell which is which. Three cases to consider: - Wolfram Alpha prohibits "resellers and aggregators," bans scraping, and bars sublicensing without permission. Yet, there's a third-party endpoint available for accessing it via x402 - Amadeus, a travel service, requires formal certification for any third-party connection, documented in a Service Order. You can access via Stabletravel. Whether the endpoint meets that standard isn't visible from the outside - A third-party wrapper was sourcing Google Flights data via SerpApi — a company Google is actively suing for scraping Search results and reselling access. Endpoint was recently removed from the Agentic Market storefront To be clear — the accountability here does NOT sit with x402. It's an open protocol, same as HTTP. It sits with those packaging unauthorized endpoints and collecting fees. With these current dynamics, providers bear the server load and see NONE of the revenue. A cleaner model already exists. MPP marks first-party integrations directly on each service card. Exa announced native x402 support, going first-party and citing the Linux Foundation's governance as the reason for choosing it. If there's no accountability here, it poisons the well. Potential native integrators become adversaries rather than participants. That revenue belongs to the providers. Native integration is how they claim it, and how x402 earns the legitimacy it needs to grow.

10h ago @litecoin experienced a coordinated attack on the chain that resulted in 13 blocks reorg that took more than 3h to generate. During this time attackers were performing double spend attacks on multiple cross-chain swapping protocols. We are investigating the situation.









NEAR Intents and near.com have resumed services. NEAR Intents and near.com were not at risk from the incident involving @rhea_finance. The pause was a precautionary measure to assess transactions that may have been linked to the exploit and to support the recovery of stolen funds, consistent with Intents’ compliance and monitoring procedures. We are continuing to work closely with the Rhea team and relevant third parties to investigate the incident, and will share updates as information becomes available.

#CertiKInsight 🚨 We have seen an incident affecting @rhea_finance The attacker created fake token contracts and added liquidity in fresh pools, likely misleading the oracle and validation layer. In total, at least ~$7.6M was extracted nearblocks.io/address/31ac7a…





