[#TSS_REELS#] Still not over Hwang In Youp’s sweet and kilig-filled moments with Filipino fans! 🥹💙 Full video ➡️ Thank you @LSquaredProdPH for the media invite! 🫶🏻 #HWANGINYOUP# #황인엽# #TO_YOU# #HWANGINYOUPINMANILA#

[#TSS_REELS#] Still not over Lee Junho's charming interactions with fans 🥰 Definitely a handsome heart stealer 🫠💘 Full video ➡️ Thank you @Official_CUCKOO for the media invite! #LeeJunho# #이준호# #CUCKOOTOPIA2026# #CUCKOOxLEEJUNHO#

[#TSS_REELS#] Actor Kim Bum who? We only know Idol Kim Bum! 😎💪 Full video ➡️ Thank you @withusind for the media invite! #kimbumPAGE∞# #kimbumjakarta2026#

[#TSS_REELS#] Hwang In Youp says YES to every dance challenge?! 😉💃 From T-ARA’s “Bo Peep Bo Peep” to CORTIS’ “GO” and ATEEZ’s “BAD”! 🔥 Full video➡️ Thank you @TMA_ID for the media invite! ❤️ #To_you# #황인엽# #HWANGINYOUP# #KNSTUDIO# #Threemountainsave#

thorchain gg20/tss attack path i reproduced the suspected gg20 leakage mechanics against the tss-lib version they used. it accepts malformed paillier material, exposes a type 5 / type 7 oracle shape, and the go-tss wrapper misses some important checks.

BAB EL-MANDEB MOVED IN THE OPPOSITE DIRECTION. CROSSINGS RECOVERED 9.7% TO 248 AND LADEN TRAFFIC ROSE FROM 103 TO 109. DARK TRANSITS HELD NEAR 23 AND TSS ADHERENCE REMAINED AROUND 91%. THE DATA POINTS TO GROWING PRESSURE ON GULF SHIPPING, WHILE RED SEA TRAFFIC CONTINUES TO SHOW GREATER OPERATIONAL RESILIENCE. - MARINETRAFFIC

THORChain incident update #1# THORChain contributors shared a new update in the dev discord regarding the ongoing incident. TLDR - Current evidence points toward a newly churned node linked to the attack, likely operated by a single malicious actor - The leading theory is an exploit in the GG20 TSS implementation, allowing vault key material to leak over time. The attacker may have reconstructed the vault private key and executed unauthorized outbound txs - Current network status: -- The network is paused after multiple node operators executed make pause -- RUNE transfers and chain observation may resume within ~12h unless decided otherwise by the nodes. -- Trading, LP actions, signing, and sensitive operations remain paused for now - Recovery discussions currently include slashing affected node bonds, using POL to absorb losses, or other community-driven solutions The investigation is still ongoing alongside THORSec and Outrider Analytics. ## Full Announcement ## 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.

Red Sea traffic rebounds Shipping activity across two key Middle East chokepoints moved in opposite directions on 18 August. Confirmed Strait of Hormuz crossings declined 17% from the previous day to 10, with six vessels exiting the MEG and four entering. Five transits used the Iranian Unilateral Scheme, while none were confirmed through the Hormuz TSS. At Bab el-Mandeb, confirmed crossings increased 53% to 46, with 30 vessels entering the Red Sea and 16 exiting. No dark transits were recorded. There was also a new IMO-confirmed attack on the bulk carrier MINOAN DIGNITY in the Strait of Hormuz on 17 August, resulting in the death of one seafarer. Stay ahead of the market with #Kpler# Insight:

Hormuz traffic falls as risks rise Traffic through the Strait of Hormuz weakened last week, with confirmed crossings falling 19.5% to 95 and reaching just three on 16 August. Routing also remained constrained, with vessels using the Iranian Unilateral Scheme or undetermined routes, while no crossings were recorded through the Hormuz TSS or Omani routes. Bab el-Mandeb moved in the opposite direction. Crossings increased 6.7% to 254, while dark transits fell from 40 to 16. Yet security conditions remain volatile. Two attacks on 11 August resulted in six seafarer fatalities and 10 injuries, underscoring the gap between resilient traffic volumes and persistent regional risk. Stay ahead of the market with #Kpler# Insight: