#KataQu
Joined March 2010
- Tweets3.2K
- Following581
- Followers326
- Likes4K
Kiki's Delivery Service retweeted
Pepi is an on-chain collection built on a modified ERC-20 standard using inscriptions. It works similarly to ordinals, but is integrated directly into an ERC-20 token effectively transforming a standard token into NFTs with a built-in liquidity pool.
In simple terms, these are NFTs that can be traded on Uniswap.
Everything is fully verifiable on-chain. We do not generate artwork on our website - the art is generated and stored entirely on-chain. Anyone can access Etherscan to retrieve their NFTs:
Guide: pepe-erc20i.vip/etherscan
Or use our web app: pepe-erc20i.vip/search (just paste the holder's wallet address to view their NFTs)
Our project is unique not only because of its technology, but also because of its structure. The collection features 6 evolutionary stages, each representing a collectible layer. The more tokens you hold, the higher your evolution stage:
Eggmas - below 1 token
Tadpole - 1 token
Baby - 2 tokens
Teenager - 4 tokens
Adult - 6 tokens
Mature - 8 tokens
Pepi can be seen as an “artcoin” - a fusion of NFTs and a memecoin.
We’re reaching out to open-minded individuals to join our small but steadily growing community. Together, we can build something meaningful.
Kiki's Delivery Service retweeted
🎁 $200 USD giveaway to celebrate Airdrop Campaign Launch!
We are giving $100 to you and $100 to the friend you tag!
To enter:
✅ Follow @ILITY_xyz
💬 Reply and Tag 1 friend
Bonus: Like & RT & Bookmark
Winner Announcement on March 23rd 09:00 UTC
Kiki's Delivery Service retweeted
hold on.
this was sitting here for a week
“prediction markets tell you what. argumentation markets tell you why.”
that’s not a small idea. that’s a shift.
how did this not dominate the timeline?
@arguedotfun really dropped this quietly and we all just kept scrolling.
@JpHitam we’re not calling ourselves early next time if we ignore stuff like this.
Kiki's Delivery Service retweeted
Justice prevails.
We have successfully regained access to our account @ility_xyz.
We sincerely apologize for any inconvenience or confusion caused to our community during this incident.
We are now fully back and secure.
This is exactly the kind of vulnerability that defines Web2.
We learned it the hard way, and it’s a powerful reminder of why we believe in building beyond these limitations.
Thank you for your patience and continued support.
Kiki's Delivery Service retweeted
HIRING: Quiet Whales 🐋
Social media force you to choose between privacy and influence. We chose both
ILITY Hub = Prove the bags. Keep the anonymity. Gain Influence.
Don't just be a whale, Be a ghost with a voice
Kiki's Delivery Service retweeted
The tokenization of RWAs will take over TradFi - and it's all happening on Ethereum.
Tokenized real-world assets on Ethereum have surpassed $17B 💼
That’s nearly +300% YoY growth 📈
Stablecoins on mainnet? Over $175B 💵
BlackRock. JPMorgan. Franklin Templeton; they’re all building on Ethereum.
Zooming out 👇
Traditional giants and crypto-heavy investors see massive growth potential for RWAs on public blockchains.
Standard Chartered estimates tokenized RWAs could hit $2T by 2028, with most issued on Ethereum 📈
ARK Invest sees tokenized assets reaching ~$11T by 2030 📈
@wintermute_t just launched institutional tokenized gold trading 🪙
Wall Street. Onchain. Happening in real time.
Stop letting the world track your every move on-chain. With @ility_xyz, you can prove your holdings and activity through ZK-proofs without ever revealing your wallet address. Stay private, stay sovereign.
Kiki's Delivery Service retweeted
Let that sink in.
Kiki's Delivery Service retweeted
No need for more L2s, says:
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.
Kiki's Delivery Service retweeted
Ethereum is in constant shipping mode.
The '100 Chains' Nightmare: Why Your Users Are Confused and Leaving
Let’s be real for a second. Using crypto in 2026 feels like trying to browse the internet in 1995, but if every website required a different modem and a different currency to pay for the electricity.
It is exhausting.
Open your wallet right now. How many networks do you have added? Ethereum, Arbitrum, Optimism, Base, Solana, Avalanche C-Chain.... the list is endless. Every time a user wants to try a new app, they have to:
1. Find the right RPC URL (scary).
2. Add a new Chain ID (confusing).
3. Bridge funds (expensive and slow).
4. Realize they don't have the native gas token for that specific chain (rage-quit).
We call this "The 100 Chains Nightmare." Developers think they are building a "Multi-Chain Universe." Users see a Fragmented Mess. We have fractured liquidity so badly that a dollar on Chain A is useless on Chain B. We are building isolated islands, not a connected internet.
This represents the current state of Web3. To the user, every chain is a lonely island. Moving between them is risky and difficult. This isolation is the #1 reason for user churn.
The industry's solution so far has been "Bridges." But bridges are band-aids. They are clumsy third-party services that wrap assets (giving you a fake version of your money) and often get hacked.
When you force a user to use a Bridge, you lose 50% - 80% of your conversion rate. Imagine if Amazon asked you to "Bridge" your USD to "Amazon-Dollars" using a sketchy third-party website before you could buy a book. You would close the tab immediately. Yet, this is what we demand of crypto users every day.
The "Bridge" step is the killer of growth. The visual shows the massive loss of potential users (Red section) simply because the infrastructure is too hard to use.
Real-World Case Study: How Gotas Solves the "Gas Problem"
To understand the solution, let's look at Gotas. @GotasSocial is a decentralized social platform where users engage with content, earn rewards, and tip creators.
If Gotas had launched on a standard EVM Layer-2, the user experience would be a disaster for mass adoption. Imagine a music fan—let's call her Sarah—who wants to tip her favorite artist.
• On a Standard L2: Sarah tries to tip. The wallet pops up: "Insufficient ETH for Gas."
• The Problem: Sarah has the tipping token (e.g., USDC or a Fan Token), but she doesn't have the Gas Token (ETH). Now she has to go to an exchange, buy ETH, and bridge it. Result: Sarah quits.
The Tanssi Solution: By launching as a sovereign Appchain on Tanssi, Gotas customized their Runtime logic to enable Chain Abstraction. On the Gotas chain, the gas fee logic can be invisible.
1. Custom Gas Token: Gotas can configure the chain to accept the Fan Token itself as gas.
2. Sponsored Transactions: The protocol can pay the gas for Sarah seamlessly in the background.
Sarah opens the app. She clicks "Tip." The tip happens. She doesn't know what an RPC is. She doesn't know what "Gas Limit" means. She just knows the app works. This is how consumer apps win. Not by teaching users about blockchain, but by hiding it.
The Bigger Picture: The "Roaming" Model
Tanssi enables Crypto Roaming. Think about your mobile phone. When you travel from the US to France, you don't swap your SIM card or sign a new contract with Orange or SFR. You just land, and it just works.
Because of XCM (Cross-Consensus Messaging), Tanssi Appchains act like a federated network. An asset on an Asset Hub can be used on the Gotas Appchain or a DeFi Appchain seamlessly. The user doesn't need to know "Which chain am I on?" They just see "I have $50."
Developers building on Tanssi can create "Invisible Chains." The wallet connects to the application, and the XCM messages happen in the background.
The goal is to hide the backend. The user shouldn't care about the database (blockchain). They should only care about the action (Yellow button). Tanssi makes this possible.
Let's look at the liquidity aspect. In the "100 Chains" nightmare, liquidity is fragmented. You have ETH on Mainnet, WETH on Arb, WETH.e on Avax... it's a mess.
In the Tanssi ecosystem, because chains share security and a communication standard, liquidity can be Teleported, not just Wrapped. "Teleporting" means the asset is burned on Chain A and minted on Chain B by the protocol itself. It is the same asset. It is trustless.
This unifies liquidity. A DeFi app on Tanssi can tap into liquidity from the Asset Hub without forcing the user to navigate a maze of smart contracts.
Stop building islands. If you launch a new L2 today using a standard stack, you are just adding another "Network" to the dropdown menu that users hate. You are contributing to the noise.
Build on Tanssi to build a Connected City. Give your users the "Roaming" experience (like Gotas). Let them use your app without ever knowing the name of the chain underneath it. That is how we get the next billion users. Not by teaching them about RPCs, but by making the blockchain disappear. LFD!
