The cryptographic world computer:
My attempt to express in somewhat concise terms the true meaning of basically everything planned to happen to Ethereum starting from the fork after Hegota. It's really not just a blockchain anymore. It's a hybrid architecture that combines together blockchains and modern cryptography, to enable much more powerful properties.
FOCIL, EIP-8288, Lean consensus, state management, formal verification, advanced mempool improvements (including privacy), and the longer-term specter of obfuscation all mentioned.
显示更多
I have to say - for me it started 2 years ago. I remember the moment so well.
I was on vacation in Montenegro. Early night. Everyone is asleep and I am on the balcony watching the cruise ships in Kotor bay as the horizon faded to dark. And I think it was Sonet 3.5 (don't quote me).
I had just setup a plugin in NeoVim called Avante by
@yetone . And it was magic.
Coding with AI at the time wasn't the same - I was going function by function. I was accepting diffs one hunk at a time. But I remember that night - from 10 to like 2 in the morning - I built what I thought would have taken me a week (I was rusty and learning the stack). It was an internal tool - a partial JSON parser / repair tool - so you can take half finished JSON and safely turn it into something that would parse. It is more complicated than it sounds.
Anyway. I was hooked that day.
At the time I was an executive at a Fortune 50, so coding was not in my job description as such. I had hundreds of engineers... but I have to say - it relit my passions, and now as I am (hopefully) building another startup - I still love it. And I still yell at it. And constantly hunt where it is messing up the architecture and adding bloat and.... well you know how it is.
显示更多
[SECURITY NOTICE] Bitget Hot Wallet Incident — September 24, 2026
At 18:31 UTC on September 24, 2026, Bitget's security systems detected unauthorized transfers from some of our hot wallets. Our security team activated emergency response protocols immediately.
What we have confirmed:
-Estimated funds affected: approximately $351.6 million
-Cold wallets remain fully secure. Bitget operates a three-tier wallet architecture — the breach contained only a portion of the hot wallet and warm wallet layers.
-User funds are safe. The full amount of this loss falls within the coverage of Bitget's User Protection Fund, which currently holds over $464 million
Actions we have taken:
-Emergency response team activated within minutes of detection
-Abnormal transfer addresses identified, flagged, and reported
-Withdrawals temporarily suspended as a precautionary measure, pending security review
-Law enforcement and on-chain security firms have been formally notified and are engaged
What this means for you:
-Your account balances are accurate and your assets are protected
-Deposits and trading remain fully operational
Withdrawals are temporarily paused and will be restored as soon as the security review is complete
-What comes next: We will provide updates on an hourly basis across this channel and all official platforms. A full incident report — including root cause analysis and corrective actions — will be published within 24 hours. We will not speculate on the attack vector until the investigation is complete.
Bitget has navigated multiple market cycles. We will not run from this. Every dollar and every decision will be accounted for, transparently and in full.
Updates will be posted here and across all official Bitget channels as they become available.
— Gracy Chen, CEO, Bitget
显示更多
I’ve seen a couple of posts about this so wanted to demystify. Today, every Muse user gets a free computer in the cloud. It's a real computer, and we’ve designed the security architecture of the Muse Secure VM carefully so you and your Muse can do almost anything you could with a computer sitting under your desk while keeping you and the system safe from threats like prompt injection. We wrote about this at length in our security blog post – Activity in the “runtime cell”, which you share with your Muse is unfettered, but sensitive actions are all overseen by the Sentinel, which runs outside of that cell. Similarly, all sensitive secrets - like the passwords you enter into Muse’s secure credential storage - are also stored outside the runtime cell.
The runtime cell gets its own root filesystem (including a full Ubuntu linux image) separate from the host filesystem where your other more sensitive data lives. Because it is isolated from the sensitive stuff that runs on the same box, this means that we can, and do, offer users full visibility and control over the files in the runtime cell. Just as you can when you install Linux on your home computer, you can poke around and see all the files that make the system work - both debian system files and the binaries and data files that implement the parts of Muse which run in the runtime cell.
This was a very deliberate choice - your Muse Secure VM truly is your own computer in the cloud. You can install software in it, write and compile code, use the browser to surf the web: it is your own Linux box that you can operate as you choose with your Muse. Poking around in this computer doesn't give you any privileged access to Meta infrastructure, or to other people's data
If I may geek out a little here for a second… As a kid I loved to take things apart to see how they worked. As a teenager I got into computers and soon found myself drawn to C:\WINDOWS\SYSTEM and the system registry, later Slackware’s /dev/, /proc/ etc – I could see how the system was laid out and as I explored what DLL files and .so files actually did, I gradually became able to meld the computer to my own will.
We’re really proud to be able to put a real computer in millions of people’s hands with a similar level of transparency. We built a file explorer right into the Library tab of the UI. We want you to be able to see the markdown files Muse writes while it thinks about how to serve you better, and explore the internals of the system if you’d like to.
So, when you ask your Muse to show you its entire filesystem, and receive gigabytes of files you’re seeing the full contents of the runtime cell. It’s yours to explore and enjoy!
If you’re not a geek like me, or simply want to download the data that you personally have created directly with your Muse, we added a feature for that too in Settings > Data controls > Download your agent data.
显示更多
MiMo-V3 is getting a new architecture. The core of it, HySparse2, is out today.
Less prefill, a smaller KV cache, better long-context retrieval—and we got all three at once.
Compared with MiMo-V2.6's Hybrid SWA architecture:
• 5.02× lower prefill FLOPs at 1M tokens
• 4.5× smaller KV cache at 1M tokens
• Better MRCRv2 and RULER-v2 scores, plus lower AgentPPL and LongPPL
Why build a new architecture?
Agentic inference is a very different workload. Each round, a short action can return a long observation that needs to be prefilled, while the context keeps growing. That puts prefill cost, KV-cache size, and retrieval accuracy on the critical path at the same time.
HySparse2 tackles all three with two levels of KV sharing:
• KV Bridging: Following YOCO, full-attention layers in the cross-decoder build their K/V from self-decoder hidden states.
• KV Reuse: Within each hybrid block, sparse layers reuse the preceding full-attention layer's KV cache and selection indices.
Two more changes: token-level selection replaces block-level selection, and a forced window of recent tokens replaces the separate SWA branch, so local and global tokens share one KV cache. Since all cross-decoder KV caches now come from the self-decoder, prefill can stop once the self-decoder finishes.
Paper:
显示更多
📢 Xiaomi MiMo-V2.6 Series Models Are Now Live on
Developed by Xiaomi MiMo, the newly released V2.6 series features open-weights native multimodal reasoning models with a 1M context window and full text/image/video/audio understanding:
🔸 MiMo-V2.6-Pro: Flagship 1.02T total / 42B active parameter sparse MoE architecture, engineered for repository-level software engineering, long-horizon agent workflows, and complex multimodal reasoning.
🔸 MiMo-V2.6-Flash: High-efficiency 309B total / 15B active parameter architecture, optimized for high-frequency office automation, fast agent execution, and cost-sensitive workloads.
Now available on both API and Web Chat!
👉 Try now:
显示更多
From sketch to home, built in 3D with Claude Opus 5.5 using Three.js + TSL. The architecture evolves through four stages: first lines, massing, detail, and finished home.
Yep. Except:
1. This was about important internal tools. The team was stuck in some architecture nightmare of their own doing (writing it in rails but headless, with graphql api, and a SPA react app, constantly needing frontend engineers for changes). I call this kind of thing 'cosplaying an enterprise production app'. All that complexity was in the way and using straight rails was perfect in that case.
2. I make calls like this all the time. Usually someone on the team asks me to. They see what needs to happen but don’t want to be the bad guy. I’m happy to just make the call if I agree with the premise. Saves enormous amounts of meetings and change management etc. Sometimes this is jokingly referred to as Founder-mode-as-a-service here.
3. For ten years I’ve also run an internal podcast called Context, where I revisit decisions like these and explain the reasoning so everyone can learn from them. This is helpful to give people all the variables that were considered and why this was the choice made given the information available at the time. I want to teach how to make such decisions effectively without needing me. Sunk cost fallacy is a problem.
4. Any notions that Shopify is succcessful despite of me doing this, instead of because of it, will have a hard time making their argument come together I think 😄
the part of 'two weeks later tobi learns about...' is nonsese and the pivot of that project up there happens one of the more successful examples of interventions. But getting the company to work effectively with great architecture and low technical debt baggage into the right direction is literally the job, so guilty as charged I suppose.
But there are always cope stories floating around like this because they are more fun, than saying 'somehow we needed tobi to stop doing silly architecture astronautics'. I can totally see that.
显示更多
With
@Cybertruck, we introduced & scaled many automotive firsts
48V architecture: 4x lower current that enables thinner, lighter wiring
True Steer-by-Wire with no mechanical steering link, enabling variable steering response
Combined with rear-wheel steering, this also brought coordinated front + rear steering for greater low speed maneuverability & high speed stability
Structural stainless-steel exoskeleton: allows exterior panels to carry structural loads, resulting in far higher torsional stiffness
Full-hard stainless air bending: forms ultra-hard exterior panels without damaging the visible surface
Etherloop: gigabit vehicle network that eliminates ~70% of cross-vehicle wiring
显示更多
📢 DeepSeek-V4.1-Flash Is Now Live on
DeepSeek’s newly released native multimodal MoE model, DeepSeek-V4.1-Flash, features a 552B parameter backbone and a pioneering Causal Encoder-Decoder architecture. Supporting a 1M context window and up to 384K output, it is engineered for long-horizon coding agents, multimodal software workflows, and high-concurrency agentic systems.
Web Chat and API access are now live. Stay tuned, even bigger perks are coming soon!
👉 Try now:
🔗 Learn more:
显示更多