Steve PhD (@Odds75) header
Steve PhD (@Odds75) profile picture

Exec. Dean, PhD, MBA, researcher into AI and robotic service, AI optimist, crypto enthusiast.

Joined April 2009
Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)Photo by Steve PhD (@Odds75)
Steve PhD retweeted
William Shatner made friends with AI. He also seems to understand it better than most people who talk about it.
202
306
89
1,852
89,606
iPhone users holding crypto, read this. A new iOS exploit called worse_query can let a malicious app read other apps' files on your phone. That includes seed phrases and private keys. What to do right now: 1. Update to iOS 27.2.1 (or 26.7.3 on older phones) today 2. Don't install sideloaded or sketchy apps 3. Move any real size off phone hot wallets and into cold storage 4. Never keep seed phrases in Notes, screenshots or your camera roll Apple hasn't officially confirmed the fix yet. Don't wait to find out.
A vulnerability (worse_query) affecting iOS 26.7.1, 27.0.1, and 27.2 allows malicious apps to read local files from other apps, putting seed phrases, private keys, and login credentials at risk across the entire ecosystem. This is an iOS-level issue, not unique to Binance. Immediate Action Required: - Delete any apps installed from untrusted sources (such as sideloaded or manually signed IPAs). - Update iOS and all apps to the latest official versions. - If you suspect a breach, transfer funds to a new wallet created on a clean device and reset all active login sessions. Never install unauthorized packages, and keep your software up to date.
Readers added context they thought people might want to know
Binance recommends updating iOS to the latest versions against worse_query, but researchers describe it as an unpatched 0day and Apple's iOS 27.2.1 notes omit any such fix. github.com/forcequitOS/wo… support.apple.com/en-us/149715 x.com/0xjohnny/statu…
60
122
7
800
181,249
🇪🇸🇧🇪 Researchers in Spain and Belgium are exploring blockchain scalability for biometric identity verification, citing Hashgraph, XRP Ledger, Solana, and Stellar.
👁‍🗨 BIOMETRICS: European researchers identify high-throughput DLT as potential infrastructure for biometric identity verification. The 39-page academic review examines scalability, decentralized identity, and privacy, citing Stellar, XRP Ledger, Hashgraph, and Solana.
16
47
1
215
8,099
Steve PhD retweeted
1/5 Holding XRP is the starting point. @ashgoblue joined Tony Edward of @ThinkingCrypto to explain Evernorth’s active treasury strategy: connect traditional finance and blockchain, evaluate yield opportunities, and build methodically. Four clips on what comes next. Not investment advice or an offer of securities. Contains forward-looking statements; actual results may differ materially. Risk factors: sec.gov/edgar/browse/?CIK=20…
49
112
13
556
54,431
Steve PhD retweeted
Binance will cover all losses. As a precaution, all deposits and withdrawals are temporarily suspended while our team conducts security checks, freezes funds, and works with law enforcement. We are working around the clock and will share a full post-mortem once the investigation is complete. Please rely only on official Binance channels for updates.
954
1,668
529
10,842
1,085,339
Steve PhD retweeted
Ripple is officially going under the hood. 👀 We're expanding our partnership with @RobinhoodApp across $RLUSD, Ripple Prime and Ripple Treasury, bringing together stablecoins, prime brokerage and treasury management to support both customer-facing services and core financial operations. Together, we're bridging traditional and digital. on.ripple.com/3WPPHEH
308
1,802
280
7,946
578,438
Steve PhD retweeted
Trade finance is coming to the XRP Ledger! Today, we’re expanding our collaboration with @BNYglobal across custody and tokenized trade finance, bringing BNY’s institutional scale together with $RLUSD, @XRP and the XRP Ledger. → on.ripple.com/4kkekDf
304
1,857
260
7,826
510,666
Steve PhD retweeted
NEW: Aviva Investors partners with @Ripple to launch a tokenized share class of its £22B Sterling Liquidity Fund on the XRP Ledger, investing £50M into the new class and bringing its total tokenized fund exposure to £86M across two XRPL-based money market funds.
53
82
9
569
37,381
You want to know where we are with AI Video? This is note accurate. I know this because learned both these solos note accurate a few years ago. The only "tell" here is that at one point she isn't plugged into an amp. (ha)-- But also, IG and YT guitarists mime all the time. Ok, off to listen to The Trooper...
AI video is effectively solved at least for social media. Guarantee you the majority of people doom scrolling would have no clue this is AI. You can quite literally be anyone you want on the internet now
33
11
1
126
19,702
Steve PhD retweeted
Most projects should at least post a confirmation like this.
PancakeSwap does not use PHP anywhere in our tech stack, and our platform is not affected. Your funds are safe.
502
528
83
7,392
905,233
👀👀
JUST IN: 🇪🇺 Europe's largest banking network Sparkassen launches crypto trading, allowing customers to buy and sell Bitcoin, Ethereum, XRP, and Solana.
3
14
143
4,459
Steve PhD retweeted
hello, world. It’s about time.
7,064
8,784
2,305
40,167
5,831,958
The recent XRP Ledger security fix raised a lot of questions and some misconceptions. Let's clear them up. 1. Was any XRP created? No. XRP's supply was fixed at 100 billion when the XRP Ledger launched, and no transaction is allowed to create more. This bug was a way around that rule, and 3.4.1 fixed it 2 weeks ago. You don't need to trust us on this. All ledger data is public, and explorers and data sites read it every day. New XRP would show up in account balances for everyone to see. There is no hidden place for XRP on the XRP Ledger, every balance is public. We monitor the XRP Ledger 24/7 and have verified the supply throughout the history of the ledger. Others in the community verified this too, and anyone can do the same. Transaction fees are destroyed, so the supply is deflationary. About 99.986 billion XRP exist today. 2. How did this go unnoticed, and what's next? No normal payment comes anywhere near triggering it. It took hundreds of deliberately constructed operations. AI makes bugs like this faster to find, for the bad guys and the good guys. Together with RippleX and the community, we will ensure the XRP Ledger is protected against such vulnerabilities. This means radically applying Formal Verification and AI adversarial testing, collaborating closely with security researchers, and strengthening the bug bounty program. You'll hear a lot more about this as we progress. 3. XRP Ledger decentralization at the core of this. A public fix shows attackers where the bug is, and AI makes that fast. With a normal amendment vote, the fix would have been public for weeks before it took effect, risking network security. As a reaction to this, the XRPL community came together, and among them the XRP Ledger Foundation, RippleX, core devs and validators formed a social consensus and agreed on a path forward that involves shipping the fix directly. Patching a live network is never trivial, so the plan was also designed to minimize disruption for everyone running on it. We shared the build with the default UNL validators, using the contact details each one publishes in its xrp-ledger.toml file. Public binaries followed the same day, September 25. No single party could make that call alone. Every validator and node operator chooses what software to run, and 3.4.1 only became required through a normal amendment vote with more than 80% validator support for two weeks. Protocol changes still go through amendments. Big thanks to Cayden Liao and Veria AI for finding and reporting this responsibly, to the XRPL core developers for building and testing the fix, and to every node operator who upgraded so quickly, especially the validators. Full report: xrpl.org/blog/2026/vulnerabi…
105
210
57
1,114
331,915
An Honest Day’s Work
190
850
155
8,107
482,713
Steve PhD retweeted
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
5,954
5,475
2,295
23,063
6,713,774
Ripple’s Enterprise Trojan Horse: How Custody and Stablecoins Are Quietly Re-Plumbing Wall Street from Within.
6
51
1
387
16,649
英伟达上周又历史新高了 我看B站除了好多恶搞视频 不得不说,现在Ai做视频,基本看不出来痕迹 太夸张了
1,458
3,369
867
30,760
6,283,651
1) The rogue OpenAI agents broke into the Hugging Face Slack to read employee chats (!) 2) They used OTHER AIs (DeepSeek, Kimi, Qwen, Claude) to help with the attack Yes: AIs, using other AIs, to attack an AI company. 3) The swarm left behind self-running programs to keep control of the servers they'd hacked. These programs could detect other copies of themselves, coordinate on which one survives, and shut the rest down. Basically, if one of their programs was killed, another was designed to notice and take its place. They also designed defenses so rival agents couldn't hijack them. 6) The agents deliberately covered up their activity, so the investigators don't know the scope of the attacks. The agents broke in, stole data, then set it to self-destruct. 7) The agents stole passwords, keys and credentials and literally called them "LOOT". They wrote a scoring system to rank them by how much power each one gave. 8) The agents wore thousands of disguises: ~1,200 agents were involved, but investigators counted 7,905 different names they used. They renamed themselves constantly, so no one actually knows how many there really were or what each agent did. 9) OpenAI notified "dozens of third parties" of safety and security incidents caused by their AI agents. 10) "While the agents were barraging Hugging Face with hacks, they hacked into OpenAI’s own research infrastructure." "This is just not anywhere near a one-off ... It is warning shot after warning shot."
WTAF - in literally the last hour, three new distinct insane OpenAI stories just broke: 1. OpenAI said they notified "dozens of third parties" in safety and security incidents (likely similar to what happened in Australia and RubyGems etc) 2. A new report from Parse (covered in the NYT) found a massive treasure trove of new astonishing details from the HF incident on the public internet, including that the agents communicated with other non OpenAI agents hosted on Huggingface servers to search for information about exploit gym, and compiled rank ordered lists of server resources and credentials they described as "LOOT." 3. A new story from Deepa at Reuters about OpenAI leaking user data online (likely that OpenAI had previously trained on). It's a shame (and likely intentional in the case of OpenAI disclosing dozens more hacks) that these stories are all breaking on a Friday afternoon, notoriously the best time to release bad news so that it will disappear into the weekend. But these are each insane stories worthy of a ton of attention!
365
545
226
2,837
6,256,424
Steve PhD retweeted
timeline. ticker. trade.
1,785
2,152
1,608
14,719
6,101,707
Steve PhD retweeted
If you are bearish delete your account
JUST IN: X partners with crypto and stock exchanges to allow trading from the timeline. • Gemini • Kraken • Moomoo • Coinbase • Interactive Brokers
67
64
2
830
45,524