What Monad has so far: - High quality open-source C++/rust codebase with many HFT-style optimizations and architectural changes - Public audits and clear docs that put the technology first. Transparency -- no hand-waving, no unsubstantiated claims - High-performance system focused on true decentralization, running continuously in testnet with 186 globally distributed validators at 5000-10000 tps - MonadBFT, a frontier consensus mechanism featuring 400ms block times, 800ms finality, large globally-distributed validator set, and tail-fork resistance - Async Execution (while supporting EIP-7702 through the Reserve Balance mechanism) - MonadDb for efficient merkle trie storage - Native code compiler for frequently used contracts - Interconnected community of smart, thoughtful crypto-natives who will grow in influence over the next few years - Ecosystem of promising young startup founders, ready to take their shot - Over $100m in ecosystem funding pre-mainnet - Founder support through DeltaV, the Monad Founder Residency, Monad Madness, and more - Monad Momentum, an incentives program focused on efficient UA and repeatable growth loops to help decentralized apps acquire normie users - A north star of making open-source, decentralized systems more powerful But there's still so much more to do. Are you excited?

A team of humble experts, running faster and faster each day, building what's needed to deliver on the dream of self-sovereign middleman-free money

It’s time to bust the MEV cartel

Welcome @tori_finance and @sharpbytexyz to Monad mainnet!

中文感觉是需要学学了

It's been super interesting to watch OpenAI and Anthropic bounce from hyped to trashed to hyped and back again. It feels like every tech product goes from insanely hyped, to beaten down, to hyped again, to beaten down again, and so on. As crypto folks will be well-aware, it is the nature of social media: people want to be smart, and the best way to do that is to be a little contrarian (while pointing out something that has a kernel of truth). But then other people keep piling on, motivated not by inherent belief but rather by observing that this opinion gets engagement. These voices become extremely loud and ultimately take things way too far in that direction relative to how things really are. Eventually that take becomes extremely consensus, and the loudness of consensus dies off because now it is just a boring old opinion. If the product is good and keeps improving though, then this cycle will get revisited again later; if not it will just fade out. And for the best products, the sine wave is upward-sloping, as the best builders make more hay than average when the sun is shining, and weather the storm of negative contrarianism better than average too. This dynamic is exacerbated in OpenAI/Anthropic because they release new models leapfrogging each other, but I think there is something fundamental about social consensus going on here too. For builders, the answer is obviously just to keep building. It's never as good as it seems, and it's never as bad as it seems. For observers and future historians, maybe the takeaway is to try to be a little earlier to the inflection point. :)

Crypto gives developers superpowers - seamless payment acceptance and instant network effects. And while AI has made crypto development easier, one of the pain points is still at the data layer - fundamentally, your agent still needs data from transactions, logs, etc. Right now the query patterns are messy and incur a ton of waste. As one simple example, you might need data from logs, but you need one field from the transaction itself, so you pull a lot of data for both, filter them client-side, and join them. MIP-16 is @category_xyz and @monad 's attempt to address longstanding problems in the RPC data interface by adding a new `eth_query` family of methods that allow for - Filtering - Relations (joins) - Field selection (only request what you need) - Better pagination Filtering: The eth_getLogs method supports log filtering, but there is no way to filter transactions or traces. To query all transactions sent to a specific address, the user must fetch entire blocks and filter client-side Relations: There is no way to join related objects in a single request. To fetch a set of logs and related transaction inputs, the user must make N+1 RPC requests (one to fetch logs, then one per unique transaction) Field selection: Every RPC method returns a fixed object schema. Users that only need block number and timestamp have no choice but to fetch large unrelated fields like logsBloom, only to immediately discard them Pagination: The eth_getLogs pagination design causes frequent timeouts and client-side workarounds. The RPC methods for blocks, transactions, and traces don't support range queries at all We're excited to propose and ship this. We believe in repeatedly and iteratively giving developers better tools. Excellent effort from @typedarray @kyscott18 @andrthesnek and Jay Miller to make this happen

Herd is covering the Monad ecosystem! The Herd team is doing a nice job of automatically disentangling chained dependencies across DeFi. I believe that with better information, we can all make better decisions. Now on Monad

Core Development You have to work on your core

Record high for tps (82) on 2026-09-21 But just getting started. Built to scale!

Excited for this! The Dirol team has built a really fun experience, and I admire their tenacity and speed of iteration. App keeps getting better every day

I’m a big fan of Ethereum moving from 12 second blocks to 10 second blocks. Who knows what could be after that, maybe 8 seconds or maybe even 7.5

Gas benchmark here, on Monad 🔥

Tomorrow is the metropolis hacker house in nyc and our team, as usual, is cooking. Keep building!

A top NFT project needs to be capable of pitching the lore to a major art collector

🔥

NFTs, on Monad

Starting to see lots of questions coming in for Metropolis mentors - keep 'em coming! If you are building for Metropolis and need help navigating the mentor portal or just want feedback on your product, my dms are open

Trade at Monad speed

Since its publication, the proposal for a Post-Quantum Monad via flexible auth has gotten a ton of good discussion @KushalBabel and @JanCamenisch have done great work figuring out the scheme and transition plan. Meanwhile the Quantum Doom Clock is ticking: currently March 8, 2028 Check out the proposal here: forum.monad.xyz/t/flexible-a…