~300m stolen → 580m user fund locked After 5 weeks, the 580m becomes a 3m seed that hopefully grows to 5m when 140m external fund were supposed to add to 280m locked Perhaps the locked are not treated in such way, but not clear. At least 50% loss even for long term believers

I don’t think the drift heist had been resolved anyway. Yet it had been quite deadly for the whole ecosystem, inevitable. The USDT white knight is not about saving drift, but a Solana dealt, that even evolve to an AAVE special episode. Asia has been toxic. Sigh.

Huge respect for @SolanaFndn for supporting Aave with USDT deposits and also bringing $AAVE to Solana. This is a great example how DeFi is united across all ecosystems. Grateful for @calilyliu and whole team! DeFi United.

I spent the entire day tracing the KelpDAO stolen funds by DPRK, specifically the TraderTraitor group. At 07:39 UTC, laundering began—just three hours after the Arbitrum Council froze 30.7 ETH (~$71M). The attacker split the remaining funds into three wallets: 0x62c72510016732333e68177d388a8111643FC64E - 25K ETH (~$57.6M) 0xD4B87bAB0ee142182f7F6DA030AeFe3E7f171530 - ~25.7K ETH (~$59.2M) 0xF9802c5EB6b972Ba686aFa7CA615910Ea8310b85 - 25K ETH (~$57.9M) The first two wallets are still holding funds, while the third began laundering immediately after receiving them and now holds ~3.8K ETH (~$8M). The funds were bridged to the Bitcoin network, with ~99% flowing through THORChain. THORChain’s swap volume today reached $211M, Over 10x its 30-day daily average, generating ~$189K in fees. During laundering, the funds were commingled with proceeds from other DPRK-linked incidents, including the BTC Turk (2025) and Bybit (2025) hacks: bc1qt3fxzwgqayqgukgr6ny5ns9vpdpcgt72f6wwfs 0xF585F57c93e4FB8ea97D9E8E6310354Bbc4DEfb9 Tracing the flows, a total of 442 BTC (~$33M) currently on the Bitcoin network across multiple wallets. This excludes funds still pending confirmations or withdrawals. Over 400 addresses have been used so far in the laundering process. I have 356, excluding several intermediary wallets not included. DPRK remains a major threat to the ecosystem. When actions like the Arbitrum Council’s intervention occur, they should be recognized for the difficult but necessary decisions they made. As for THORChain, we saw the same pattern during the Bybit hack, so nothing different should be expected. JP will likely use this moment to draw attention and appear in interviews discussing how the protocol was used to launder illicit funds. Stay smart

Today, Drift is announcing a collaboration with @tether and other partners totaling up to nearly $150 million to support our commitment to a relaunch with USDT at the center, and a path to user recovery. These funds encompass a $100M revenue-linked credit facility, an ecosystem grant, and loans to market makers, designed to fund a dedicated user recovery pool. Learn more 👇

参与了 @Solana_zh 的内测，drift出事以后，@PhoenixTrade团队成员@ethtwit 也是第一时间慰问和支持。早上刷到补充的信息，链接账户发现收到了5000u空投，真的太感动了，这就是solana的社区文化，Only possible on solana

Solana was built for security. As the ecosystem scales, so does our investment in the tools, standards, and support. Today that commitment deepens with a new security program, active monitoring, formal verification for top protocols, and a new crisis response network. Learn more 👇

1/ We've spent the last ~16 hours conducting an independent forensic investigation into the @DriftProtocol exploit. We are limited on what we can share publicly while we work alongside the Drift team and relevant authorities on the ongoing recovery effort. Here's what we can say. Built with @DivergSec

before the "timelocks reeeee" commenters find this, a misused timelock can fuck you just as bad. some operations need quick response and low coordination. there's no silver bullet. you actually have to do risk analysis and implement the appropriate things

不在阿布扎比现场？ 没关系！ 收看 Breakpoint 直播，一网打尽全部最新现场信息！

today, Solana changes forever we've solved the biggest data/RPC problem that exists solana historical/archival data — has now been redesigned quick context: today when you query historical data (getBlock/getTransaction/getSignaturesForAddress), it hits Google BigTable this is i) slow, ii) expensive, iii) inflexible for queries e.g., you physically can not get the first tx for a Solana address without looping back endlessly from the latest tx for busy addresses, this can take thousands of RPC calls — extremely slow, expensive, and annoying also, imagine you wanted to get the most recent 100 txs for an address, how do you do it? you first hit getSignaturesForAddress to get all the tx signatures and then call getTransaction on each tx to get its details — this can take 1,001 RPC calls in the worst case not anymore we have built a new distributed archival storage system that is 1,000x faster, more flexible, and more scalable the best part? we're introducing a new API method: getTransactionsForAddress with this method, you can now: i) combine getSignaturesForAddress and getTransaction calls into just 1 call instead of 1,000 ii) you can search in reverse order without needing to traverse iii) you can search historical transactions by time and slot ranges (e.g. get me all the txns from January 5th, 2025 until February 5th, 2025) what's more: - getBlock calls are now 10x faster - getTransaction calls are now 10x faster - getSignaturesForAddress calls are now 10x faster 10x lower latency, 100x fewer RPC calls, and 1000x less code enjoy! docs below

RT @Solana_zh: 👨‍💻熟悉的开发者咖啡活动回归，​这次搬到了广州！这也是Solar第一次在广州举办社区活动，尝试在大湾区布局更多站点。期待开发者们的加入！ ​​🗓️时间：9月13日 周六14:30-18:00 📝现在报名 t.co/xPSCxV4…

1/ SIMD-0268 by Alexander M. & @realbuffalojoe raises the CPI nesting limit from 4 to 8. This allows programs to make twice as many cross-program calls within a single transaction, improving composability across the network 🧵

i'm hearing oracle updates are about to get a priority boost no simds or gatekeepers required. ibrl

The community governance process for SIMD-0326: Alpenglow is complete. The proposal has passed: 98.27% voted Yes 1.05% voted No 0.69% voted Abstain 52% of stake cast a vote

I'm going to do an AMA about Alpenglow on Reddit right around the start of the SIMD-0326 governance voting phase. My temp reddit account is u/AlpenglowAMA

On tonight's market turbulence. As market's went into a flurry during J. Powell's update, @Backpack had a period of a bit over 10 minutes of degraded performance. Specifically, - Reading and loading the UI did not work for some users (orderbook wouldn't load for example). - Trading did work for most users. If you look at the trade stream, orders continued to get executed and everyone was able to open and close positions. - However, because the the UI did not work for many, or because it was slow/laggy, it meant that, in practice, trading was not working for most users. Why does the above happen? Well, it's because our system prioritizes writes over reads. And so all the writes to adjust positions, cancel orders, etc. all go through for API traders while the UI is unable to read data out of the engine because they are being starved, creating the above situation. So WTF Armani. This literally happened during the last PPI print a week ago. What are you doing about it? Yes it did, and it's the exact same issue. We took the critical feedback, previously, and as a result, we already have the fix. It just needs to be tested and released, which will happen over the next 1-2 weeks. Lag is extremely frustrating for a trading product during volatile moments. We take it EXTREMELY seriously, and we already have a very straightforward path to 10x our system capacity imminently. To be honest, we just never really prioritized performance as it was never really an issue. We got the high level architecture right, but some of these details never became an issue until we started hitting the scale that we are at today. As a result, we prioritized things other than performance (like daily proof of reserves). However, now performance is our number one priority. To everyone trading on Backpack and upset at today's lag, we hear you loud and clear, and we're on it.

Rust is a good thing. Yet sometimes readability in assembly is a lot more vivid than that in those decorated languages.

👀