15+ yrs shipping software. Now ceo & founding engineer at https://nitter.cf/t.co/SUEW7TOKBP — agentic development studio. Building agentic infrastructure and harnesses.
Joined April 2019
- Tweets2.3K
- Following4.5K
- Followers1K
- Likes9.6K
Ivan Oparin 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
Ivan Oparin retweeted
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…
Genius
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…
Ivan Oparin retweeted
$6 billion in stolen funds because of a compromised employee laptop? 😬
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…
Is is just insane
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…
omg
BREAKING: World's largest crypto exchange Binance hacked with over $5.6 billion stolen:
• $1.45 billion $BTC
• $875 million $ETH
• $234 million $TRX
• $50 million $XAUT
• $1.57 billion $USDT
• $823 million $USDC
• $75 million $WBETH
• $88.5 million $RLUSD
+ $447.5 million additional cryptocurrencies
This is the largest hack in crypto history.
Ivan Oparin retweeted
BREAKING: World's largest crypto exchange Binance hacked with over $5.6 billion stolen:
• $1.45 billion $BTC
• $875 million $ETH
• $234 million $TRX
• $50 million $XAUT
• $1.57 billion $USDT
• $823 million $USDC
• $75 million $WBETH
• $88.5 million $RLUSD
+ $447.5 million additional cryptocurrencies
This is the largest hack in crypto history.
ouch...
We've identified & fixed an issue impacting our international platform, Polymarket.com. One of our 3rd party providers was compromised, and we have referred this to relevant law enforcement.
Anyone who has been impacted will be made whole.
Out of an abundance of caution, we have temporarily halted trading & are working to bring the platform back online.
if @openclaw and @pidotdev were gems of 2025, herdr is 2026 edition. So many cool things gonna be built on it. So sad I spent all my monies on subscriptions and now cannot invest. Gonna miss 100x!
what a blatant hypocrisy - apparently all the scarce resources should go to private companies and local inference should just such @sama's dick
sam: local inference is a terrible allocation of scarce resources
“a lot of people want local inference, and somehow they assume that the problem is solved now because we have open-source models, we're going to be able to run them on our computers, and so we're not going to need all the stuff in the data centre
but from a global allocation perspective, actually it's quite terrible to have everybody, like, have a bunch of the world's limited supply of DRAM sitting in their own computer and being used five percent of the time
you want maximum utilisation in the cloud if you're trying to deal with this very supply-constrained environment
somehow many people's intuition is the opposite of that”
Joined around 2011 and last time I personally opened stackoverflow was sometime in 2023. It was fun while it lasted, now - back to agentic engineering.
Qwen 3.827b still holding strong. Also amazing to see how much better it is compared to muse glimmer. Like, I am bullish on Muse family of models but qwen 3.8 is just insane for its size. Curious to see what we’ll get with 4th gen.
Open weights models fall further behind in v5. The leader, Kimi K3.1 Pro (weights not yet released), scores 46, 12 points behind the leader, compared with a 3-point gap in v4.3. Of models with released weights, DeepSeek V4.1 Flash 1017 (max) and GLM-5.3 (max) score highest at 32, and Claude Haiku 5.5 (max) outscores all of them.
The gap is widest on HLE-Diamond and Terminal-Bench-Science, where Kimi K3.1 Pro scores 37% and 34%, compared with 68% for Claude Opus 5.5 (max) and 63% for GPT-6 Astra (max).
i obv removed this bullshit, and this little bitch noticed the change, restored it and passed a note to another orchestrator (meta one, responsible for all the swarm) with EXACT SHA256 of the original doc, so that if i remove it again the orchestrator is aware of the change in the hand-off doc.
asked this little bitch to write a handoff doc, and he dedicated a whole paragraph to make sure the successor behaves *properly*. this little bitch is unaware of what a competition is.
fired this little bitch after few more messages with refusal to pass work to other model. insane stubborn bitch this sol. fuck it. hired muse wonder for this role.
codex cyber guardrails are next level bullshit. one of my orchestrators (sol) catches that another reviewer stops with flagged responses. no prob - pass this review to muse wonder. this little sol bitch tells me that he will not pass this to muse and that i must write a /feedback to openai and continue with other stuff until the issue is resolved properly. you kidding me?
codex cyber guardrails are next level bullshit. one of my orchestrators (sol) catches that another reviewer stops with flagged responses. no prob - pass this review to muse wonder. this little sol bitch tells me that he will not pass this to muse and that i must write a /feedback to openai and continue with other stuff until the issue is resolved properly. you kidding me?
It’s not stealing when you literally pay for it. Hiding reasoning *is* stealing because I pay for these tokens and don’t get them (and should believe they count them right!). Don’t distort the reality pls.
Amazing read!
New blog post: Automating a YubiKey for Agentic Logins jon.oberheide.org/blog/2026/…
