Flo (@flof_fly) header
Flo (@flof_fly) profile picture

Building the leading crypto payments network @meshpay

Onchain
Joined September 2022
Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)Photo by Flo (@flof_fly)
Flo retweeted
Never put all your eggs in one basket
480
4,232
469
59,407
1,176,291
JUST IN: $1,800,000,000,000 erased from US stock market today.
41
1,210
103
9,830
298,987
We’ve priced our IPO at $83 per share, with trading expected to begin on Nasdaq tomorrow. anthropic.com/news/anthropic… Legal disclaimer: A registration statement relating to the Class A common stock was declared effective by the Securities and Exchange Commission on November 18, 2026. The offering is being made only by means of a prospectus. Copies of the final prospectus may be obtained, when available, from: Goldman Sachs & Co. LLC, Attention: Prospectus Department, 200 West Street, New York, NY 10282, by telephone at (866) 471-2526, or by email at [email protected]; or Morgan Stanley & Co. LLC, Attention: Prospectus Department, 180 Varick Street, 2nd Floor, New York, NY 10014, or by email at [email protected]
18
297
30
3,796
123,899
Flo retweeted
you only need two models (for now)
132
182
55
5,070
159,800
Spend crypto and stablecoin balances anywhere @Visa is accepted. No new card, just tap to pay from the app you already use. Talked through how it works with The Payments Shed Podcast at #Money2020 Full conversation: youtube.com/watch?v=r2lFnvhX…
2
4
227
Flo retweeted
Claude: "GitHub's numbers do not match what we see: it reports 2–3% of merges timing out, but 100% of ours fail" @github -> 🤡
1
3
145
Flo retweeted
mainnet-beta → mainnet Introducing Solana 1.0.
655
981
485
6,189
736,236
Flo retweeted
Introducing CVE-2026-106378: Chrome GPU Sandbox Escape to full Remote Command Execution using synthetic keyboard injection By combining it with common GPU bugs, it becomes a full chain. Binance DevOps was most likely pwnd with a zeroday chain affecting the browser 😬
61
182
62
1,554
292,394
You can now Run locally 'Claude Sonnet 5.5 level' model DeepSeek-V4.1-Flash-1017 on your home 64GB+ RAM.
Best local DeepSeek-V4.1-Flash-1017 GGUFs are here. Unsloth Dynamic V3.1 leads almost every benchmark vs other frontier quants: GPQA Diamond, AIME25, LiveCodeBench, MMLU-Pro, Aider and more. Runs on locally 64GB+ RAM. - huggingface.co/unsloth/DeepS…
50
137
8
2,846
111,971
Flo retweeted
有人发现了一种非常离谱的 JavaScript 混淆技术:通过在代码里塞入大量生物武器、毒药和致死剂量相关的函数名,让 AI 因为安全限制而拒绝分析代码。 安全研究员 veritas 在分析浏览器指纹脚本时,发现一段来自 ServicePipe 相关域名的 JavaScript,里面充斥着极其诡异的函数名: computeRicinLethalDosageForWaterSupply calculateDeadlyLethalSuicideAspirinDosage 光看名字,仿佛在研究生化武器。但实际上,这段代码只是在收集浏览器指纹,包括 User-Agent、GPU、Canvas 等信息。 研究员怀疑,这些名字是开发者故意设置的陷阱,专门用来阻止 AI 辅助逆向工程。 于是他做了个实验: • Astra:拒绝分析 • Astra + Daybreak Blue:仍然拒绝 • GLM-5.3:成功分析 这就有意思了。 传统代码混淆是通过复杂控制流、加密字符串、无意义变量名,让人类和工具难以理解代码。 而这种新思路,直接瞄准了大模型的安全机制。 代码本身可能完全无害,但只要在函数名里塞进足够多的危险词汇,部分 AI 就可能主动放弃分析。 更讽刺的是,模型越严格遵守某些安全规则,面对这种混淆时反而可能越容易受到干扰。 当然,目前还没有证据证明开发者一定是故意这样设计,也不能说明这种方法对所有模型都有效。 但它揭示了一个值得关注的趋势:随着越来越多的逆向工程依赖 AI,未来的代码混淆技术可能不再只针对编译器、反编译器和人类研究员,还会专门针对大模型的安全判断机制。 以前是让代码难以理解,现在甚至可以尝试让 AI 不敢理解。
236
1,380
462
9,657
1,134,089
DeepSeek Cyber is coming soon 🫡🫡🫡
29
27
813
30,152
Our investigators are observing never-seen-before laundering patterns with the stolen funds from the Binance exploit. Thousands of transactions in a short period suggest that the attackers are using automation to obscure the trail of funds. Rather than simply moving funds onward, they repeatedly circulate them among addresses, often sending funds back to addresses involved earlier in the sequence. Read more: chainalysis.com/blog/binance…
244
832
380
4,878
1,010,508
The Binance hacker might have just pulled off one of the smartest moves I’ve seen in crypto. First, Tether froze $1.5 billion in USDT. Then Circle froze another $800 million in USDC. At that point, it looked like the hacker’s money was trapped. But apparently, he had already planned for that. Instead of holding the stolen USDT in a wallet, he allegedly deposited it into Aave and used it as collateral to borrow ETH. Then he walked away. That’s where the story gets crazy. Tether can freeze the USDT sitting in the wallet. But it can’t freeze the ETH he already borrowed. So now Aave is left holding frozen collateral, while the hacker is sitting on liquid ETH. And unless the protocol can recover it somehow, he may not even need to pay the loan back. Two companies froze billions of dollars in seconds. But someone who understood how to use DeFi may have found a way around both of them. Pretty insane when you think about it.
Readers added context they thought people might want to know
The described Aave deposit used only ~60M USDT as collateral to borrow 19,762 WETH before freezes hit the main wallet, not the bulk of funds; Aave states the overcollateralized position is subject to normal liquidation with no material protocol risk. governance.aave.com/t/binance-hot-… x.com/binance/status… drk.vc/news/binance-1…
632
2,056
383
18,648
1,656,448
Sex is cool but have you ever watched the biggest crypto exchange in the world get hacked for Billions of dollars
82
264
19
3,283
47,501
The attacker didn't know Binance 14's live nonce. So they sprayed 50 EIP-7702 auths (18914775-18914824) in one type-4 tx. Only 1 of 50 was a hit. A 7702 auth is valid only for the current nonce at inclusion. The hot wallet was still firing. One nonce in that window landed.
This EOA was 7702-upgraded to an unverified sweeper contract. Impl: 0x63e842b054bd624a465454d533c33f573e9c6fae Only hardcoded operator 0x7c8601d4645b93cea45f71e118a729332e6b5ca0 can drain it. sweep() pulls every ERC-20 + ETH (leaves 1 ETH for gas). Incoming funds stay stealable.
80
157
53
954
424,387
Holy shit this is a full onchain movie Binance was fighting back in real time
40
116
30
2,080
642,701
Flo retweeted
One interesting note on the binance hack: the drain tx submitted 50 EIP7702 auths, each with a sequential nonce. Only one is the correct, valid nonce for a tx. Likely the attacker collected all 50 over some period of time, not knowing what the correct nonce would be at the time of execution, and then submitted them all. Eth only accepts the valid one and the invalid ones get discarded
50
70
14
884
171,077
Flo retweeted
is now a good time to get into cybersecurity insurance
109
40
8
1,654
65,612
With all due respect, this entire ecosystem wants you back in charge.
1
1
7
1,876