Pinned
Prince
1,925 posts
onchain
Joined December 2018
- I was testing @HyperliquidX EVM testnet yesterday & noticed there’s no token faucet. The process was: - Get Arbitrum Sepolia ETH - Claim mock USDC - Deposit to HL - Trade USDC for TESTH - Transfer to HyperEVM Too much work, right? So I made a faucet: 🔗 hyperliquid-faucet.vercel.app
- Why are web3 people addicted to calls? Most things can be done in chat. Faster. Less friction. Just say “gm” and drop two messages. Instead, we: – Ask for Calendly – Schedule a call – Check if mic works – Find a quiet place Why?
- Still don’t get why apps force users to connect the wallet before showing anything. Just wanna check a price or rate — why the extra step? Terrible UX. Let people explore first.
- I was playing around on @HyperliquidX EVM testnet and deployed first smart contract for testing. Couldn’t find an explorer or UI to visualize transactions or blocks, and using the CLI was cumbersome. So I built a basic interface with RPC methods: 🔗 hyperevm-explorer.vercel.app
- High DeFi yields aren’t just about better tech—sometimes they depend on collateral reuse. This simulation shows how two lending models impact rates: → Rehypothecated Pools: Higher yields, lower borrowing costs. But: More risk, cascading failures in stress scenarios. →
00:00Replying to @serayushBottom line: rehypothecation is a trade-off b/w capital efficiency & minimizing risk. Protocols pick their poison, and knowing the game helps you play it smart. - We didn’t choose AMMs because they were better. We chose them because there was no other choice. Back in 2020, every DeFi primitive like spot trading, perps, lending relied on one simple mechanism: deterministic curves like xy=k. Not because it was the best design — but becauseWhy AMMs can’t replicate CLOBs: → No competition: AMMs use deterministic pricing curves, not real-time quotes, so there’s no market-driven price discovery. → No order intent or strategy: In AMMs, all liquidity is passive. Traders can’t set limit orders or express intents. →
- OEV recapture methods like @chainlink's SVR are redistributing liquidation value back to protocols. This visualization shows how protocols benefit during liquidation events: → Traditional Model: MEV searchers capture 100% of the liquidation value. → SVR Model: Protocols
00:00OEV (Oracle Extractable Value) recapture is one of DeFi's most underrated innovations of 2024. While many remain unaware, millions in MEV have silently leaked from lending protocols for years. OEV occurs when oracle price updates trigger liquidations, creating profit that flows - This visualization explores how block structures impact performance. MegaETH's dual-block architecture includes: → Mini-Blocks (10ms): Fast updates, low latency, same inclusion guarantees. → Full Metadata Blocks (1s): Complete data, EVM compatibility, higher latency. Both
00:00 - I’ve heard people say MegaETH doesn’t have a ton of apps. They’re right, and that’s a good thing. You don’t need 100 apps doing the same thing. You need a few solid ones building the right primitives. Get the base right and everything else follows.
- In @yangl1996's simulation, we see how block time affects real-time applications. Now, let’s look at more crypto-native example of a red-black tree, commonly used to manage orders in an order book. On the left, orders are added with a 10ms block time, and on the right, with
00:00
00:29And this is how 10ms block time looks like (bottom), even when the user is 100ms away from the server. code for the simulation: github.com/yangl1996/bloc…












