The NEAR community is built different. People across this ecosystem show up for each other when it counts, fast and in force, to make NEAR and this whole industry stronger. Be part of NEAR.

NEAR Intents hack suddenly got resolved pretty quickly, and in a positive way not something you see too often after a sizable hack in crypto

The attacker has proactively contacted NEAR Intents, potentially turning the tide in the $3.8 million security incident. The suspect has transferred 1 BNB to the near:native Intents Recovery Wallet, accompanied by a message expressing willingness to cooperate and requesting a Signal contact. This address is one of the primary attacker addresses previously identified by ZachXBT. Previously, Alex Shevchenko publicly called on the attacker, stating that evidence has been gathered and demanding repayment within 48 hours to designated Bitcoin, BNB, Ethereum, and Solana addresses. The attacker’s response now suggests that both parties may have officially entered negotiation stages. If the attacker accepts the proposal, they may receive a 5%–10% bounty.

$NEAR ETF nets over $50M in two days. This ETF holds 0.76% of #NEAR's supply after just two days of trading. Two days show a pulse, not a pattern. Steady ETF flows after launch can show whether new buyers keep adding.

Narratives come, narratives go. I've scaled down on my $NEAR position. Not that I don't believe in the project. The actual opposite of that. However, portfolio management and fundamental thesis can be two different things. It's had a maximum amount of sentiment and narrative over the past few weeks. If it corrects, from a technical standpoint, that's completely fine. I'm happy to be buying and scaling this back in. Levels I'm monitoring: - $4.30 - $3.90 - $3.50 And yes, after that, we'll go to $10+.

🚨UPDATE: NEAR INTENTS GOT THE $3.8M BACK! @AlexAuroraDev says the money from yesterday’s bug was returned in full and the investigation is stopping. That was the swap product, not the near:native protocol. He also told the sender to use the bug bounty next time instead of breaking the service.