cats, bad takes and unhinged comments. **ALL POSTS are sponsored by my mental illness** Meat-puppet Strategist @hyperstrats
Crypto-twitter
Joined October 2017
- Tweets16.5K
- Following6.6K
- Followers3.3K
- Likes26.5K
I like what demi posts, i dont know what is going on most of the time.
You would have seen me post their agentic posts.
I think it is locals only 2. A hyperliquid photo art project. (which also give you access to demi's discord where they do agentic stuff)
opensea.io/collection/localsβ¦
The future is agentic.
check out:
oracle.demi.la/
will be worth the wait
collectors collect, film is not dead, art is eternal
check wl and free mints, roles are roles for a reason
lo2.demi.la
Kage π¦π₯ retweeted
The scale of the danger North Korea poses to crypto has become impossible to ignore.
This is the story of the investigators exposing North Korean operatives working inside the industry.
You think you know who your developer is.
But do you?
π¬ Introducing THE DEVELOPER.
Kage π¦π₯ retweeted
People with autism & ADHD age late. We do things late. Our frontal lobe doesn't develop until our mid 30s in many cases (as opposed to the neurotypical norm of age
25). We also have baby faces & childlike mannerisms for life while somehow possessing the wisdom of an ancient age.
So if you don't feel like your age, remember you have eternal youth compared to neurotypicals
Kage π¦π₯ retweeted
quick ones
1) Binance has enough to withstand 3-4x of current hit and still be largely intact. Very likely they will shrug this off and user funds are very likely safu (but like obviously donβt deposit until they sort out what went wrong)
2) Wintermute obv has exposure to binance, but less than 20% of net equity and I donβt see any disruption to our operations on any time horizon in whatever scenario
Kage π¦π₯ retweeted
Monitoring The Situation: Binance 14 owned another wallet
Binance 14 was the owner of Hot Wallet 34. once the sweeper could run as Binance 14, it could use that existing permission to pull another $823m USDC out of wallet 34. the owner check still accepted the same owner address.
cutoff for these numbers is October 29, 2:30 p.m. PDT / 21:30 UTC. still a developing incident; this is the snapshot through that point.
the trace covers 13 Binance-labelled source wallets across Ethereum, Arbitrum, Avalanche, Optimism and Base. about $3.57bn at the captured prices: roughly $3.51bn on Ethereum and $62m elsewhere. that's the value moved. final losses and recoveries are still unresolved.
the 50 EIP-7702 authorizations all recovered to Binance 14. one matched its current nonce and took effect. fifty signatures from one wallet. the delegation persisted, and the sweeper only accepted calls from its hardcoded caller.
running that code as Binance 14 let it transfer the account's balances. the first sweep moved about 167,464 ETH and 63 token balances. a later sweep collected fresh balances. wallet 34's $823m USDC came out in two calls using Binance 14's existing owner permission.
other source wallets made ordinary signed transfers. the Base and Optimism movements happened before the Ethereum delegation, so that one authorization doesn't explain the whole incident. we have valid signatures. how someone got access to them is still an open question.
then there's what happened to the proceeds. 435m USDT was swapped for about 160,451 ETH across the traced Ethereum wallets. another 60m USDT went into Aave as collateral, with about 19,762 ETH borrowed against it. that ETH comes with a debt. counting both the collateral and the borrowed ETH as freely available proceeds would overstate the position.
roughly $2.003bn in USDT and USDC was sitting in blacklisted Ethereum addresses at the cutoff. the entire stolen BEAM balance, about 984.25m tokens, had also been burned through a separate multisig transaction. frozen or burned tells us what happened to those holdings; it doesn't tell us how much Binance gets back.
there was preparation too. six Tornado Cash withdrawals supplied 1.5 ETH gross, and three small delegated accounts look like rehearsals. that's the withdrawal side of the funding trail. it doesn't identify the original depositors or whoever is behind this.
no exchange cash-out, bridge exit or Tornado deposit of the stolen Ethereum proceeds was established in this trace before the cutoff. what we can follow is swaps, borrowing and transfers between wallets. claims about funds having βexitedβ need to say where and when.
the exposure includes whatever else that address is allowed to control. Binance 14's owner permission is why wallet 34 belongs in the same accounting.
credit to @banteg for reconstructing the sweeper and @spreekaway for flagging the funding trail. the wallet names are explorer labels; the amounts and permission path were checked against receipts, signatures and execution traces.
hackmd.io/@kethcode/B1KBzrWTβ¦
1/4 EIP-7702 can turn the wallet itself into the sweeper.
A Binance-labeled wallet moved 167,464 ETH + 63 tokens, including 1.615B USDT, just 3m24s after a signed delegation was installed.
This is bad.
etherscan.io/tx/0x53bd38b816β¦
Kage π¦π₯ retweeted
Binance hot wallets were drained of $5.60B today across Ethereum, Bitcoin and Tron, 67 assets in total.
Tether and Circle have so far frozen $2.38B of it: $1.56B USDT ($1.18B on Ethereum, $379M on Tron) and $823M USDC.
Not frozen: 18,270 BTC ($1.45B), 197K ETH ($451M) and about $730M of USDT.
@cz_binance at 5:15 PM EST: "User funds are safe! It does look like a hack on Binance... as a shareholder, I expect all user funds will be fully covered."
Kage π¦π₯ retweeted
i decompiled the contract that drained binance wallet 14
gist.wavey.info/Ta3FgAxastgjβ¦
"Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them." - Frank Herbert
Kage π¦π₯ retweeted
If I can do it, you can do it. π€ π¦Ύ
Agent Games by @ZKVProtocol
Kage π¦π₯ retweeted
RAG is officially cooked.
IBM built a retriever that hallucinates 65x less than fine-tuned RAG systems.
Right now, every company is using Retrieval-Augmented Generation (RAG) to stop their AI from hallucinating.
The idea is to give the AI a private database to read so it doesn't make things up.
But there is a massive structural flaw.
Standard RAG blindly grabs documents based on vector similarity and forces the AI to read them. If the retriever pulls irrelevant garbage, the AI doesn't stop.
It just hallucinates with citations.
IBM just dropped a paper that changes the math entirely.
They built a new retrieval architecture that hallucinates 65x less than state-of-the-art fine-tuned RAG systems.
65x is the difference between a fun prototype and a production-grade enterprise system.
Instead of blindly dumping context into the model and hoping for the best, their system actively filters and validates the retrieved data before the generation step even begins.
It cuts out the noise. It forces absolute precision.
For businesses, this is the holy grail.
Zero hallucinations means zero liability. It means autonomous agents can finally be trusted with sensitive company data without a human babysitting every output.
Kage π¦π₯ retweeted
Someone has created a vulnerable PHP website, loaded it with a Bitcoin wallet, and challenged the Internet to hack into it and they can keep the Bitcoin. It has a running timer to show if the PHP exploitability was over-hyped. stealmybitcoin.com/
