TheCheshireCat.eth

You called me lazy. Token down. No hype. I built the best AI agentic framework in crypto + a decentralized prediction market right as the US bans Polymarket & Kalshi. I didn’t time the market. I timed history. Launchpad=flywheel=god tier candles.

@nyx_fi_ @HeyAnonai How many rebrands for HeyAnon? Gemma, hud, memes launcher, polymarket killer and now ApesWin 2.0? Ps: paid post bro (20k$)?

Daniele, the founder of Wonderland and Frog Nation, claims he coined the term “DeFAI” before it was a trend. He’s now building an AI agent launchpad on top of HeyAnon, and the tokenomic structure around $ANON is worth understanding before it goes live. Here’s what the thread describes. Every agent launched on the platform is paired with $ANON on a bonding curve. A bonding curve is a pricing mechanism that ties token cost to circulating supply, the same model Pump.fun uses. When an agent hits its graduation threshold, 30,000 $ANON get permanently locked in the liquidity pool. Not burned. Locked. The LP fees generated from that pool flow directly to the agent’s developer as a revenue stream to cover LLM API costs and fund further work. Now the supply math. Total $ANON supply is 21 million. It takes just 7 graduating agents to permanently lock 1% of the entire supply. If 100 agents graduate, that’s 3,000,000 $ANON removed from circulation forever, 14.2% of the total supply. The infrastructure behind it: 44 integrated protocols across 17 blockchains, including Aave, Hyperliquid, Pump.fun and Jito. The Agent-to-Agent framework, which allows autonomous agents to communicate and collaborate without exposing their internal logic, has already been opened to the public. An upgrade is coming that’s supposed to make it faster and more accessible. Here’s what the price history says though. $ANON hit an ATH of roughly $25 in January 2025. As of this week it’s trading under $1. Down 95% from peak. Market cap around $11M. That’s not a disqualifier, it’s context. Infrastructure can be real and the token can still underperform. Both things have been true in crypto many times. The deflationary mechanism only works if agents actually graduate in meaningful numbers. If the launchpad doesn’t attract developers, or if the DeFAI narrative cools before the flywheel builds momentum, the model stays elegant on paper and inert on-chain. Save this if you’re tracking the DeFAI space. The launchpad launch will be the real test of whether the structure holds. How many agents do you think will graduate in the first 30 days?

@rektwagmii @defidaddy

@defidaddy you’re getting paid and you’re part of the team so just say it in canada the criminal code doesn’t allow advertising or promoting gambling unless it’s provincially licensed that’s why pushing unlicensed online casinos is illegal farming your own followers for a paycheck isn’t it

Pandora is a permisionless prediction market that caters to everyone: - Defi Farmers - Prediction market gamblers - Algo arbitrageurs Pandora is a money printing machine.. 🧵 thisispandora.ai

@DeFAIchad Real volume or fake volume from the money you got from the treasure? You and dd got 20k$

An interesting market is up on Pandora. "Will Pandora Hit $100K Volume Before Feb 28, 23:55 UTC?" thisispandora.ai/share/0x29d8b6… Current volume is $73.7k. There is still little bit over one day left for resolution. However, there is a twist in market rules...

@Wen_Wagmii @danielesesta Not defending him but we have to tag also the great community manager @DeFAIchad

@CatInCryptoLand Your legacy @danielesesta

$Time $Spell $ICE $Wagmi Hey $Anon Apes win $WIFE $Logoff $Lambo HUD Pandora parlays Pandora All from one man... Who?

@rektwagmii @danielesesta You won and we got rugged

@CatInCryptoLand One and only Mr yapp king @danielesesta

@VitalikButerin Dev stop selling... When cto ethereum?

Now, the quantum resistance roadmap. Today, four things in Ethereum are quantum-vulnerable: * consensus-layer BLS signatures * data availability (KZG commitments+proofs) * EOA signatures (ECDSA) * Application-layer ZK proofs (KZG or groth16) We can tackle these step by step: ## Consensus-layer signatures Lean consensus includes fully replacing BLS signatures with hash-based signatures (some variant of Winternitz), and using STARKs to do aggregation. Before lean finality, we stand a good chance of getting the Lean available chain. This also involves hash-based signatures, but there are much fewer signatures (eg. 256-1024 per slot), so we do not need STARKs for aggregation. One important thing upstream of this is choosing the hash function. This may be "Ethereum's last hash function", so it's important to choose wisely. Conventional hashes are too slow, and the most aggressive forms of Poseidon have taken hits on their security analysis recently. Likely options are: * Poseidon2 plus extra rounds, potentially non-arithmetic layers (eg. Monolith) mixed in * Poseidon1 (the older version of Poseidon, not vulnerable to any of the recent attacks on Poseidon2, but 2x slower) * BLAKE3 or similar (take the most efficient conventional hash we know) ## Data availability Today, we rely pretty heavily on KZG for erasure coding. We could move to STARKs, but this has two problems: 1. If we want to do 2D DAS, then our current setup for this relies on the "linearity" property of KZG commitments; with STARKs we don't have that. However, our current thinking is that it should be sufficient given our scale targets to just max out 1D DAS (ie. PeerDAS). Ethereum is taking a more conservative posture, it's not trying to be a high-scale data layer for the world. 2. We need proofs that erasure coded blobs are correctly constructed. KZG does this "for free". STARKs can substitute, but a STARK is ... bigger than a blob. So you need recursive starks (though there's also alternative techniques, that have their own tradeoffs). This is okay, but the logistics of this get harder if you want to support distributed blob selection. Summary: it's manageable, but there's a lot of engineering work to do. ## EOA signatures Here, the answer is clear: we add native AA (see eips.ethereum.org/EIPS/eip-8141 ), so that we get first-class accounts that can use any signature algorithm. However, to make this work, we also need quantum-resistant signature algorithms to actually be viable. ECDSA signature verification costs 3000 gas. Quantum-resistant signatures are ... much much larger and heavier to verify. We know of quantum-resistant hash-based signatures that are in the ~200k gas range to verify. We also know of lattice-based quantum-resistant signatures. Today, these are extremely inefficient to verify. However, there is work on vectorized math precompiles, that let you perform operations (+, *, %, dot product, also NTT / butterfly permutations) that are at the core of lattice math, and also STARKs. This could greatly reduce the gas cost of lattice-based signatures to a similar range, and potentially go even lower. The long-term fix is protocol-layer recursive signature and proof aggregation, which could reduce these gas overheads to near-zero. ## Proofs Today, a ZK-SNARK costs ~300-500k gas. A quantum-resistant STARK is more like 10m gas. The latter is unacceptable for privacy protocols, L2s, and other users of proofs. The solution again is protocol-layer recursive signature and proof aggregation. So let's talk about what this is. In EIP-8141, transactions have the ability to include a "validation frame", during which signature verifications and similar operations are supposed to happen. Validation frames cannot access the outside world, they can only look at their calldata and return a value, and nothing else can look at their calldata. This is designed so that it's possible to replace any validation frame (and its calldata) with a STARK that verifies it (potentially a single STARK for all the validation frames in a block). This way, a block could "contain" a thousand validation frames, each of which contains either a 3 kB signature or even a 256 kB proof, but that 3-256 MB (and the computation needed to verify it) would never come onchain. Instead, it would all get replaced by a proof verifying that the computation is correct. Potentially, this proving does not even need to be done by the block builder. Instead, I envision that it happens at mempool layer: every 500ms, each node could pass along the new valid transactions that it has seen, along with a proof verifying that they are all valid (including having validation frames that match their stated effects). The overhead is static: only one proof per 500ms. Here's a post where I talk about this: ethresear.ch/t/recursive-st… firefly.social/post/farcaster…

this one’s about us 👁️🫦👁️ 👉👈

@getmoni_io totally agree 😅

I hope you are doing good But we miss you 😥

Ok @LeonidasNFT your target is @cz_binance and binance I am not defending him but man, #Runestone is not doing so good ... No words about the second drop (if there is a second drop) Or game over?

Just to say... Fuck Cz Ps: fuck Daniele too

@VitalikButerin Stop selling eth

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-pr… and ethresear.ch/t/synchronous-… ). 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.

@danielesesta New requirement for the whales club: hold 50000 anon and lock for 12 months

Launch looking great! Liquidity is there Parlays are getting filled fast ! Excited for what is to come.

@danielesesta @mek0768 They can join here: t.me/anonpricedani

@CatInCryptoLand @mek0768 They work for Kalshi too eheh

From today you can choose to be the house. Farm crazy APRs from Parlays. This changes the game, before was reserved to the Elite, now anyone can be the house, take any bet and be in control of their own strategy.

@mek0768 @danielesesta You forgot to write: "I am a bot"

@danielesesta thanks for the opportunity to flip the script and be the house with , gonna be a wild ride taking control of my own strategy.

@TSherzai @danielesesta You forgot to write: "I am a bot"

@danielesesta Game changer 🚀

@viophl @danielesesta You forgot to write: "I am a bot"

@danielesesta thx for opening up parlays to everyone, gonna love being the house now

100% understanding 😅 we’re gradually handing out invite codes to beta testers for the new extension features, and we’re really grateful for the community’s interest and feedback! all Monians, please check out the pinned post for further details 💜