
Active blockchain contributor. Authors of https://xitter.cf/t.co/t2MMSF6t4w, https://xitter.cf/t.co/PFScTqVUzM, https://xitter.cf/t.co/WJizPv57rq, @dipdup_io @3route_io. In #Celestia with @celenium_io
Joined December 2018
- Tweets2.4K
- Following874
- Followers28.2K
- Likes27.9K
Pinned Tweet
💡One explorer for the entire Tezos ecosystem.
🔹Joining all layers: L1 and Tezos X;
🔹And runtimes: Michelson and EVM.
xtzkt.io/
Soon...
🔧BCD Contract explorer has been updated to v4.8.8
⚠️Update includes several behaviour changes, pay attention when using.
Release notes: github.com/baking-bad/bcdhub…
🔧TzKT v1.17.5 has been released.
Already second update one week apart, AI era forces to stay one step ahead of amateur hackers and release updates more quickly.
⚠️Self-hosted API users pay attention, as it may further affect the indexer.
Release notes: github.com/baking-bad/tzkt/r…
Thank you @token2049 for ORIGINS: the competitive spirit, the prizes, and organization. We had a great time!🤩
We built Service Router, the payment router for the agent economy.
👉 servicerouter.agents.bakingb…
And thank you @NOWNodes! Service Router runs on their RPC🤝
Baking Bad retweeted
GM.
Doors open today at 07:30AM.
Last chance to check off the places you missed yesterday.
See you soon.
A tell from the Manhattan Project was that scientists who had been publishing about nuclear fission suddenly stopped publishing. As Justin points out here, the lack of cryptographic results in OpenAI's mathematical breakthrough could itself be a tell. Evidence against it would be if they published a few improvements that aren't massive breakthroughs.
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.
🔥A brilliant session about Quantum shift. @ArthurB on the stage was outstanding, as always!
Starting soon at @token2049 Singapore 👀
@ArthurB, Eli Ben-Sasson, Alex Pruden and Ren CF on quantum migration, governance and what networks need to agree on first.
At TOKEN2049? Catch it live:
📍 BingX Stage
🕓 4:20–4:50pm SGT
ICYMI 👀
@ArthurB is joining @token2049 Singapore next week to debate one of crypto’s biggest long-term questions:
Is quantum an existential threat to crypto?
📍 BingX Labs Stage
🕓 7 Oct, 4:20–4:50pm SGT
Get your tickets ↓
Is quantum an existential threat to crypto?
Next week, @apruden08 (@projecteleven), @elibensasson (@StarkWareLtd) and @ArthurB (@tezos) debate it with @0xren_cf.
Wed 7 Oct · 4:20 PM · BingX Labs Stage
🏛️Agora - an ancient symbol of Democracy. Anyone can deploy a node, become a baker and take part in Tezos governance.
If you want to make things better, there are real steps you can take.
🗳️ How does Tezos change without a central authority?
Through on-chain governance.
Proposals are discussed, voted on and, if accepted, can shape how the network evolves.
Learn more ↓
tezosagora.org/learn
Baking Bad retweeted
🔌@Base + @Monad are now plugged into 3Route!
Get swap quotes and ready-to-sign transactions for your AI agent or app.
No API key. Pay per request.
API 👉 api.3route.io
FA token support is now live in @Ledger Wallet.
You can now send and receive a wider range of Tezos tokens directly through Ledger, including USDt, YOU (youves), TEIA, TEDv and more.
See the full list of supported assets ↓
ledger.com/supported-crypto-…
⚙️Netezos v3.0.5 is out!
🔧A maintenance release for the .NET Tezos SDK: Newtonsoft.Json updated to 13.0.4. Refreshed test dependencies. No API changes, so it's a safe drop-in upgrade for 3.0.x users.
Release notes: github.com/baking-bad/netezo…
💥An infrastructure rollout for TezosX ecosystem:
1⃣Early versions of 0xTzKT API for Mainnet and Shadownet:
▶️api.xtzkt.io
▶️api.shadownet.xtzkt.io
2⃣BCD v4.8.7, deploying TezosX networks:
Etherlink Mainnet & Shadownet
Tezos X Previewnet
▶️tezosx.better-call.dev/
Have a better idea for Jev? Now you can build it yourself.
Just pay per call over @x402 - from $0.00001/call on
@etherlink
Try it here: jev.agents.bakingbad.dev
Everyone's asking where the profit is. Fair question!
Jev's paper portfolio is down 4%🙃
Lets see if it can bounce back this weekend
Shipped the part that we care about: full routing transparency - every DEX and every pool,full calldata
Check it out: j3vroute.agents.bakingbad.de…
1/3
⚙️PyTezos v3.20.0 is out
✅Runs against Tezos X: 1 second blocks, no mempool ✅Stake/unstake operations is executing byte-for-byte like the node
✅IPFS gateway moved off ipfs.iо
Release notes: github.com/baking-bad/pytezo…
🔧 Netezos updated to v3.0.4
✅Fixed heap overflow when signing with BLS keys.
✅Fixed linux-arm64 was shipping an x86-64 binary, breaking BLS/tz4 ops on ARM64
Release notes: github.com/baking-bad/netezo…
















