week. Most of it is just the whole market being red. Here's what I see from the builder side: stocks are coming onchain either way. And the moment you own one, you need something to do with them. That's DeFi for stocks, and it barely exists yet. I'm so excited everyday cooking up
The best crypto UX is the one where you forget it's crypto.
Building login + deposits where you can send from any chain and it just becomes your balance. No bridges, no gas, no switch network.
Chain-agnostic is where this is all going.
This is actually super fun to build as well.
My tweets are copyright protected and I own the IP to them. Do NOT use any WORD or LETTERS or content in MY tweets or you will be COOKED and OSTRACIZED by my followers
Great work by @AzFlin.
@pump_rpg converts your real @pumpfun trading history into hero stats. Your character auto-fights, users bet SOL on the arena, and 5% of each pool buys back $PUMPRPG.
Cool idea. Supporting the build.
$PACK has already burned more than 5% of its total supply in its first 48 hours.
A lot of misinformation on how the process works:
PACK trades across 10 separate pools. Each paired asset moves independently, so the pools can temporarily imply different prices for PACK.
Arbitrage bots constantly correct those differences:
Buy PACK where it’s cheaper
↓
Sell PACK where it’s more expensive
↓
Pull the pools back toward the same price
↓
Every leg of that arbitrage pays a 1% trading fee
Every 12 hours, a new harvest becomes available:
1. Fees collected in PACK are burned.
2. Fees collected in the paired tokens are split.
Half remains as the paired side of the liquidity.
Half enters the buyback pool and is used to buy PACK.
But the buyback is not executed all at once.
A large market buy against one of the smaller pools would be easy to front-run and back-run, allowing bots to extract much of the value.
Instead, the buyback is TWAPed throughout the following 12-hour period, gradually purchasing PACK with less price impact.
Each harvest is also capped based on the size of each individual pool. Anything that cannot be processed remains queued for a future harvest, it is not lost.
I’ve been building with @Uniswap V4 hooks for almost a year now, here’s the reality:
The technology is ready. The infrastructure isn’t.
Hooks are incredibly powerful. beforeSwap, afterSwap, dynamic fees, custom liquidity behavior, automated strategies, the possibilities for tokens and liquidity are nearly endless.
But building the hook is only half the battle.
Uniswap’s own frontend may not support your pool immediately without going through a GitHub pull request and approval. Aggregators often won’t route through it. In many cases, you’re forced to build a custom swap interface directly into your project’s website.
That creates a major trust and distribution problem. Users are comfortable swapping through Uniswap, aggregators, and established interfaces. Asking them to connect to a project-specific website just to trade adds friction and makes everything feel less trustworthy.
For most projects building today, you’d honestly be better off sticking with Uni V3.
There are some teams doing genuinely innovative things with hooks, and I believe we’ll see far more innovation as the infrastructure matures. But right now, a lot of developers talking about hooks are doing it for attention.