CTO @BitMEX | ADHD-fueled agentic crack team dictator
New York, NY
Joined December 2011
- Tweets368
- Following247
- Followers618
- Likes439
how tf can individual engineers willy nilly spin up prod containers (gitops anyone?), submit & sign blockchain transactions (no taptap rules?)..
someone is so busy sowing chaos throughout Europe, amplifying unrest through essential resource scarcity. the political motives are blatant, I can’t wait to learn all about it six months once the elections are settled & when everyone's distracted worrying about shampoo prices!
neat experiment showing how openrig is just that good github.com/guregodevo/memdoo…
herdr-app is legit - time to double the agent count to 120
it only takes 10min to inventory all internet-exposed services/resources across dozens of AWS accounts & Kubernetes clusters with a good model & a few scripts. there’s no excuse not to monitor that very closely.
Quentin Machu retweeted
we will need to rebuild and rewrite much of software to adapt to a new, faster pace.
code used to arrive one drop at a time. soon, if not already, code will be written as if it were a continuous stream, like a violent river twisting and turning as it pleases.
this is not a new thing: big tech cos have had to deal with this with the enormous scale of their engineering teams. but now ai has brought an incredibly elastic and capable workforce wielded by every engineer. this is your problem now, and the only way to adapt is to evolve your systems so agents - even and especially the ones with little context about the right way of doing things - can thrive. make the easy thing the right thing.
your codebase is becoming organic architecture. agent contributions grow around the constraints and guardrails you’ve designed. good software engineering matters even more now! and no, the continuous stream of code is not something you have to watch helplessly. be more ambitious and design systems, frameworks, and languages to control the chaos.
the time for mourning coding is long over
imagine having your entire threat model behind $6+B rely on an engineer not pulling the wrong npm/pip transitive dependency 😮💨
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified.
The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far.
Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete.
As an immediate precaution, Binance has:
- temporarily suspended deposits and withdrawals while security checks are completed;
- revoked the affected address authorisation;
- engaged law enforcement and blockchain intelligence partners to trace and recover funds.
Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice.
Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions.
binance.com/en/support/annou…
Proud to say BitMEX has never lost a single satoshi during its lifetime. First perp exchange, last to have never been pwnd.
U.S. govt's Palo Alto Networks firewalls + Active Directory pwned through php2shell (CVE-2026-109618) & fragnesia (CVE-2026-46300)... Public-facing management interface & escalation vuln released in May 2026 btw... dreamgroup.com/blog/chained-…
Quentin Machu retweeted
‼️ BREAKING: US officials believe Nvidia CEO Jensen Huang is the target of a Chinese spy plot.
They believe Alice Huang, a Megaspeed executive seen at his side in Taiwan, is a Chinese intelligence asset.
President Trump has been briefed about the matter.
Quentin Machu retweeted
中国社区逆向拆解了Claude的封号机制。以下是他们的发现
Claude使用积分制。注册时账号获得初始分数，之后根据行为加分或扣分。低于阈值直接封号。回分很难
影响分数的因素:
注册
> 干净IP是最重要的因素。不一定要家宽，但必须干净
> Gmail已经不是最优选，有权重更高的邮箱服务
> 注册时直接弹KYC的号可以扔了
> 用手机App注册会加分
支付
> 刚注册就订阅会扣分
> 直接上Max会大幅扣分。最好等两天先订Pro
> 支付时弹KYC说明账号在考察期，但不一定会封
> 国外实体银行卡加分。Google Play也行。虚拟卡扣分
使用
> 不要一次把限额用完。宁可两个号轮换也不要一个号撸到底
> Desktop客户端有少量加分。尽量少用网页端
> 手机端也有少量加分
> 开启记忆功能加分。记忆文件越多分越高
IP和设备
> 稳定性是关键。不要跳IP，尽量一直用同一个
> 代理必须全局模式并开启TUN
> 多设备登录大幅扣分。理想状态是一台电脑一个客户端
> 频繁换IP、频繁登录、高并发都会大幅扣分
账号年龄
> 老号有巨大的容错空间。2023年的号明显更高
> 分数随时间增长，但很慢
其他
> Windows和macOS没区别。Linux会扣分
> 时区和语言基本不影响。不会因为北京时间就封号
> 跟Claude说自己是中国人没问题，记忆不会触发封号
> 大量使用Fable会扣分
> 升级Max大概率进入观察期，除非是高权重老号
观察期和封号
> 接近阈值时账号可能进入观察期。典型特征是掉登录
> 观察期继续扣分就会封号
> 高分号可以扛过多次观察期
关注我，拆解你每天在用的服务背后到底怎么运作的
Quentin Machu retweeted
Spent the day at Shenzhen RoboTech 2026. Biggest takeaway: the US and China are building completely different layers of robotics.
1/ In the US, everyone's on data collection, world models, sim, teleop software. In Shenzhen, it's all hardware: actuators, motors, sensors, components.
2/ Data collection hardware was everywhere: gloves, head rigs, camera arrays. But I didn't meet anyone actually collecting the data. They build the rigs, others use them.
3/ Lots of humanoid companies, but the serious ones are industrial. The robot boxing drew the biggest crowd and was honestly the least impressive thing there.
4/ Ask any booth "can you make this?" and the answer is always "Give me the CAD, we'll get it done." Lead times run 3 weeks to 3 months.
5/ Small sample runs are welcome, and so are factory visits. Most companies are domestic for now, and nearly all want overseas customers.
6/ Go-to-market couldn't be more different. US hardware sells through LinkedIn, X and events. China sells through Amazon China, Taobao and WeChat.
If you're building robots in the US, the hardware layer you need is sitting here, looking for customers.
Quentin Machu retweeted
I had the same thing, it showed up in 200+ sessions.
Didn't switch shells though. The agents write bash and zsh doesn't split unquoted vars. One line in ~/.zshenv fixed it:
[[ ! -o interactive && ( -n $CLAUDECODE || -n $CODEX_THREAD_ID ) ]] && setopt sh_word_split no_nomatch no_equals
Interactive zsh stays exactly the same.
Quentin Machu retweeted
Most of these buildings in the Shenzhen science park were built in the last couple years. The park itself is massive.
woke models are the enemy of progress. thankfully I’m happy to sell my soul to the motherland and run deepseek abliterated at 1500 tok/sec
