New Discord Announcement from THORChain Devs #🚨thornode-mainnet 🚨 ALERT 🚨 Developers and THORSec have been investigating today’s incident continuously throughout the day. While new information may still emerge, I want to provide the community with an update based on what we currently know. The goal of this update is to clarify the current understanding of the situation as accurately and transparently as possible. A newly churned node, thor16ucjv3v695mq283me7esh0wdhajjalengcn84q, which entered the network several days ago, is currently believed to be associated with the attack. Developers have identified links between Ethereum addresses used to acquire and bond RUNE for this node, and Ethereum addresses that later received the stolen funds. Based on current evidence, it is believed this was conducted by a single malicious operator, though the investigation remains ongoing. At this time, the leading theory is the attacker exploited a vulnerability within the GG20 TSS implementation which allowed sensitive key material from vault participants to leak over time. By accumulating enough leaked information, the attacker was ultimately able to reconstruct the vault’s TSS private key and execute unauthorized outbound transactions. The Treasury is actively collecting forensic data and coordinating with Outrider Analytics and relevant law enforcement agencies in an effort to identify the attacker and pursue recovery of stolen funds where possible. Due to multiple node operators executing make pause, the network is currently paused. Unless further action is taken, the pause state will automatically expire in approximately 12 hours. At this time, the development team is comfortable allowing the pause to expire in order to restore RUNE transfers and chain observation activity. However, trading, signing, LP actions, and other sensitive operations will remain paused until the network and community align on a comprehensive recovery and remediation plan. The recovery process will likely require node governance decisions regarding how losses are ultimately handled. Several potential approaches are already being discussed, including: Slashing the bond of nodes participating in the affected vault Allowing Protocol-Owned Liquidity (POL) to absorb the loss Additional recovery proposals that may emerge from the broader community At this stage, no final decisions have been made. The team is continuing to work on a complete recovery and restart plan for the network. Bringing trading and full functionality back online will likely take several days, and potentially longer depending on the complexity of the chosen remediation path. We will continue to provide updates as more information becomes available. Finally, I want to thank the developers, node operators, security contributors, and the broader THORChain community for the enormous amount of work done today. One of THORChain’s greatest strengths has always been the community’s ability to come together under pressure, collaborate quickly, and solve difficult problems together.

Right where it should be.

💡 Freelancer Tip: The 5 highest-paid Web3 freelance skills Based on current market data: 1. Smart Contract Auditing — $150-300/hr 2. Solidity/Rust Development — $100-250/hr 3. DeFi Protocol Engineering — $120-280/hr 4. Blockchain Architecture — $100-200/hr 5. Web3 UI/UX Design — $80-150/hr All of these are in demand on LaborX right now. What's your experience? Tell us below 👇 #ChronoTech #LaborX #Web3Jobs #Freelancing #Crypto #FutureOfWork

TRX up 26% over three months amid persistent investor skepticism; concerns over Justin Sun manipulation allegations, ongoing lawsuits, and regulatory scrutiny cited, according to Santiment. mt in max

Join us today for another round of Alpha Leaks 📻 👀 ⏰ 15:00 CET 📍 X and YT Source ⚫️ Aurora Twitter | Blog | Youtube | Discord | Telegram | Developer Portal ⚫️

Last week on @BNBCHAIN's AI-focused AMA, we made an important point: ANYONE can build on BNB Chain right now. I've never written code, and I recently deployed a project using the ChainGPT skill for Claude Code. If I can do it, so can you! → github.com/ChainGPT-org/chaingpt-claude-skill

Soil XRP Vaults are live with 5% APR through June. Yield is only one part of the story. With Palisade (Ripple Wallet), Fireblocks, and Safe Wallet, SOIL brings institutional custody standards to on-chain yield. Because DeFi access should not mean unnecessary custody risk.

x.com

Soil XRP Vaults are live with 5% APR through June. Yield is only one part of the story. With Palisade (Ripple Wallet), Fireblocks, and Safe Wallet, SOIL brings institutional custody standards to on-chain yield. Because DeFi access should not mean unnecessary custody risk.

x.com

New Discord Announcement from THORChain Devs #🚨thornode-mainnet **🚨 ALERT 🚨** We have identified unauthorized outbound transactions from one of the Asgard vaults. As a result, funds were lost from that vault. This investigation is still in its very early stages, and the information below is preliminary and subject to change as we continue analysis. We ask the community to give the node operators and development teams time to complete a thorough investigation before drawing conclusions. What we currently know: - One of the six Asgard vaults appears to have been compromised. - Current estimates place the loss at approximately $7.4m USD. - The network automatically detected the abnormal behavior and halted signing activity, which alerted the broader community and prevented further outbound activity. - Node operators securing the vault maintain bonded RUNE which is subject to slashing in the event of unauthorized outbound transactions. - Churn activity has been paused while the investigation is ongoing and remediation steps are evaluated. - As a result, onboarding of additional chains and any operations requiring churns will be delayed until the network is stabilized. At this stage, the root cause has not yet been determined. Current areas under investigation include: - A potential vulnerability in the GG20 implementation layer - Infrastructure or operational compromise affecting a sufficient number of nodes - Other attack vectors that could have enabled unauthorized signing activity At this time, we do not have evidence supporting any specific conclusion, and we want to avoid premature assumptions until the investigation is complete. We are asking all node operators to immediately review their infrastructure, hosts, key management systems, and operational security for any signs of compromise or abnormal behavior, and to report anything suspicious to the dev team. Additionally, node operators participating in the affected vault are requested to securely provide Bifrost logs to the dev team for analysis using `make relay`. We will continue to provide updates as we learn more.