A long overdue apology. I’ve wanted to write this for a long time but never found the right moment. Many people have asked what happened to @MeowFi_ after the Monad Residency and where things went from there. The truth is, while we faced plenty of challenges preparing for launch, most of them had solutions. The one thing I could no longer ignore was my health. For the past two years, I’ve been dealing with health issues that were initially manageable. But instead of properly addressing them, I kept pushing harder and harder. I spent nearly two years working 16 hours a day, convinced I could outwork every problem. I couldn’t. My health gradually deteriorated to a point where even simple things like walking became difficult. Alongside that came lot of personal issues and eventually everything started piling up at once. As much as I wanted to continue building Meow Finance, I simply couldn’t keep going. It wasn’t an easy decision and it’s something I’ve carried with me for a long time. Maybe one day, if the circumstances are right, I’ll return to it. For now, I want to start fresh. I want to explore again, contribute to other projects, help founders and builders and give back to the community that has given me so much over the years. I’ll still be around. I’ll still be building, learning, helping and supporting this space in whatever way I can. My goal remains the same: to add even a little value to people’s lives. So here’s to a fresh start. Back to zero. Back to learning. Back to building. Thank you to everyone who supported Meow Finance, believed in me, and stuck around through the silence. ❤️

It’s already hard for DeFi to grow on Monad when LSTs are paying 15% Aave with $15M in incentives on top of that would seriously disrupt the rest of the DeFi ecosystem on Monad. We saw something similar play out with Plasma. That said, it might also turn out positive. Aave incentives could bring direct value to MON via LST yields, encouraging more staking for higher and safer yield (borrowing and looping). And incentives would likely have a much more direct impact on MON's PA. As a MON stakeholder builder, I'm neutral on this deal.

Today we are proposing the Aave Will Win Framework, a new alignment framework that directs 100% of product revenue to the Aave DAO treasury under a token-centric model.

One of the biggest reasons why it's hard to experiment in crypto is security audits and their costs. I've spoken to more than 10 teams in the last month who are all currently ready to launch on mainnet, but are held back by audits and their insane cost. A basic audit can cost up to 50k for a small codebase, which makes it hard for bootstrapped projects to launch and explore if they should even be spending their time on this. The industry did a terrible job of overpricing security audits and it has strongly held the space back.

There have recently been some discussions on the ongoing role of L2s in the Ethereum ecosystem, especially in the face of two facts: * L2s' progress to stage 2 (and, secondarily, on interop) has been far slower and more difficult than originally expected * L1 itself is scaling, fees are very low, and gaslimits are projected to increase greatly in 2026 Both of these facts, for their own separate reasons, mean that the original vision of L2s and their role in Ethereum no longer makes sense, and we need a new path. First, let us recap the original vision. Ethereum needs to scale. The definition of "Ethereum scaling" is the existence of large quantities of block space that is backed by the full faith and credit of Ethereum - that is, block space where, if you do things (including with ETH) inside that block space, your activities are guaranteed to be valid, uncensored, unreverted, untouched, as long as Ethereum itself functions. If you create a 10000 TPS EVM where its connection to L1 is mediated by a multisig bridge, then you are not scaling Ethereum. This vision no longer makes sense. L1 does not need L2s to be "branded shards", because L1 is itself scaling. And L2s are not able or willing to satisfy the properties that a true "branded shard" would require. I've even seen at least one explicitly saying that they may never want to go beyond stage 1, not just for technical reasons around ZK-EVM safety, but also because their customers' regulatory needs require them to have ultimate control. This may be doing the right thing for your customers. But it should be obvious that if you are doing this, then you are not "scaling Ethereum" in the sense meant by the rollup-centric roadmap. But that's fine! it's fine because Ethereum itself is now scaling directly on L1, with large planned increases to its gas limit this year and the years ahead. We should stop thinking about L2s as literally being "branded shards" of Ethereum, with the social status and responsibilities that this entails. Instead, we can think of L2s as being a full spectrum, which includes both chains backed by the full faith and credit of Ethereum with various unique properties (eg. not just EVM), as well as a whole array of options at different levels of connection to Ethereum, that each person (or bot) is free to care about or not care about depending on their needs. What would I do today if I were an L2? * Identify a value add other than "scaling". Examples: (i) non-EVM specialized features/VMs around privacy, (ii) efficiency specialized around a particular application, (iii) truly extreme levels of scaling that even a greatly expanded L1 will not do, (iv) a totally different design for non-financial applications, eg. social, identity, AI, (v) ultra-low-latency and other sequencing properties, (vi) maybe built-in oracles or decentralized dispute resolution or other "non-computationally-verifiable" features * Be stage 1 at the minimum (otherwise you really are just a separate L1 with a bridge, and you should just call yourself that) if you're doing things with ETH or other ethereum-issued assets * Support maximum interoperability with Ethereum, though this will differ for each one (eg. what if you're not EVM, or even not financial?) From Ethereum's side, over the past few months I've become more convinced of the value of the native rollup precompile, particuarly once we have enshrined ZK-EVM proofs that we need anyway to scale L1. This is a precompile that verifies a ZK-EVM proof, and it's "part of Ethereum", so (i) it auto-upgrades along with Ethereum, and (ii) if the precompile has a bug, Ethereum will hard-fork to fix the bug. The native rollup precompile would make full, security-council-free, EVM verification accessible. We should spend much more time working out how to design it in such a way that if your L2 is "EVM plus other stuff", then the native rollup precompile would verify the EVM, and you only have to bring your own prover for the "other stuff" (eg. Stylus). This might involve a canonical way of exposing a lookup table between contract call inputs and outputs, and letting you provide your own values to the lookup table (that you would prove separately). This would make it easy to have safe, strong, trustless interoperability with Ethereum. It also enables synchronous composability (see: ethresear.ch/t/combining-pre… and ethresear.ch/t/synchronous-c… ). And from there, it's each L2's choice exactly what they want to build. Don't just "extend L1", figure out something new to add. This of course means that some will add things that are trust-dependent, or backdoored, or otherwise insecure; this is unavoidable in a permissionless ecosystem where developers have freedom. Our job should make to make it clear to users what guarantees they have, and to build up the strongest Ethereum that we can.

International offramps for India are now LIVE 🇮🇳 (with FIRC included) You can now: > Raise invoices > Offramp contract payments > Convert USDC → INR > Get FIRC automatically Built for Indian freelancers & global contractors 💸

1 like = 1 prayer for $MON Happy another ATL to those who celebrate (fuck you)

The real flippening is here

Try to match my Monad DeFi farms. ✨ETH: 26% ✨MON: 110% ✨Stablecoin: 30% avg Was printing around 140% on my MON stack yesterday, it's all relatively safe, not risking at all.

Bearish on all these NFT founders fighting over nothing. Just build something instead of bullshitting with your NFTs, they’re living in their own bubble. Do something productive for once, you’re just looking like a clown at this point. I’m already bored of you guys. The good thing is actual apps are in peace and flourishing together on Monad.

1/ Fusaka is coming December 3rd. Ethereum’s next major upgrade shows that the network can grow to meet global demand, without compromising on decentralization or permissionlessness. Whether you’re a user, builder, institution, or operator, here’s how Fusaka will impact you.

it's easy to make people fool gmonad

143 is the community coin 💜

People will buy a memecoin and then start fudding and blaming random people when their coin doesn’t perform well. We’ve got so many crybabies here in the Monad trenches. I bought Chog and 143 myself, both can go to zero and I still wouldn’t blame anyone.

I took my money back from @bro_dot_fun plus a little extra today. Looking forward to never seeing you again (or maybe tomorrow night when I feel like betting again after dinner). Thank you.

Crime is happening as we speak. Someone just minted around 2B $DAK and is dumping nonstop, already made about $120K from it. Gmolandak!

Monad Farm 101 @SteakhouseFi x @Morpho x @withAUSD Earn 59,000% APY on your stablecoin (AUSD). The vault is relatively new, but the risk exposure isn’t huge so could be a solid farm. Yield is mainly coming from MON incentives added by Steakhouse since borrowing hasn’t picked up yet. Farm: Stable Yield: 59,000% (mostly MON incentives) ✨ Risk: Low (low liquidity) 🟢

We have 1.5B in population, don’t be surprised if you see Indians behind your army pages, government pages or even local football pages. 🇮🇳 or if your online gf turned out to be Indian. Thank you

Explorer @vgharshul has just claimed a BlockPermit. Solid W. Welcome to the Block. Nominate 2 fellow explorers on the website below and they could be next to claim a BlockPermit (Code in DMs) blockpermit.blocknads.art