Deep Dive
1. Security Patch & Contract Audit (April 2026)
Overview: This was a critical security update. The team paused the main token contract, deployed a patched version to fix a bug, and fully restored all user balances after an attacker drained funds from foundation wallets.
On April 29, 2026, an attacker exploited a bug in the SWEAT token contract on the NEAR Protocol, draining approximately 13.71 billion tokens (about 65% of the supply) within 30 seconds. The team's rapid response involved pausing the contract, collaborating with exchanges to freeze stolen funds, and deploying a corrected contract. All external user balances were restored. The smart contracts have been temporarily closed from public view pending a comprehensive security audit.
What this means: This is neutral to cautiously bullish for SWEAT because it demonstrates the team's capability to respond decisively to a crisis, ensuring user funds were protected. The commitment to a full audit aims to strengthen long-term security, though the event highlights inherent risks in smart contracts.
(CoinMarketCap)
2. Multichain "1-1-1" Wallet Update (November 2025)
Overview: This was a foundational upgrade to the Sweat Wallet, introducing a "1-1-1" model: one wallet interface, one master key, and one token (SWEAT) for gas across multiple blockchains.
Launched on November 26, 2025, the update expanded support to Ethereum, Base, BNB Smart Chain, Arbitrum, and NEAR. It allows users to manage assets across all these chains from a single interface and pay transaction fees directly with SWEAT tokens, eliminating the need to hold separate native gas tokens. The update also included deeper AI integration for user support and expanded language localization.
What this means: This is bullish for SWEAT because it significantly improves the user experience, making crypto more accessible to its massive mobile user base. By increasing the utility of SWEAT as a necessary gas token across multiple ecosystems, it drives organic demand and strengthens the token's fundamental use case.
(Cointelegraph)
Conclusion
SWEAT's development trajectory shows a clear focus on fortifying security post-incident while aggressively improving mainstream usability through chain abstraction. How will the upcoming security audit findings shape the next phase of protocol development?