Content pfp
Content
@
0 reply
20 recasts
20 reactions
​woj ツ pfp
​woj ツ
@woj.eth
degen and ham chains were mistakes and they set the whole farcaster ecosystem back im posting this after reaching out to @jacek and @deployer privately, but since they both answered that they have no plans on sunsetting the chains, i want to give a heads up to all other teams building their economies on farcaster: don't launch you own chains 1. fc ecosystem only has a chance to work if there is a lot of liquidity in one place 2. separate chains fragment the liquidity and only benefit the passive token holders (less sell pressure) and mev bot operators (arbitrage between chains and pools). actual users pay in UX, mev and fees 3. devs who want to launch integrations with these projects are fucked because most infrastructure providers don't support these small chains im building supercast wallet and it's beyond frustrating to see how close we were to having something truly great and how much harder it is to build a good UX on top of these projects because they selfishly decided to launch their own chains
75 replies
35 recasts
257 reactions
Mark Carey 🎩🫂 pfp
Mark Carey 🎩🫂
@markcarey
As developer, I appreciate the argument of added complexity and UX challenges for multi-chain. The liquidity fragmentation argument is weaker since it is the main argument against the Ethereum's chosen scaling approach. Following this argument, everyone should use Ethereum Mainnet: we'd be able to minimize liquidity fragmentation and as developers, our lives would be easier and users would have better UX. But it would cost $50 to mint/claim anything and there would be about 10 users. You have omitted the benefits of these smaller L3 chains. Yes, there is a cost of less infra support, but there are benefits for both projects and users. It is a trade-off. As one example, my /pixelnouns project on Degen chain. I have paid the gas for 34,000+ transactions, providing a **better** UX for users by eliminating the need for wallet interactions -- they mint by hitting a button in frame. As an unfunded indie dev, the project would not be possible on /base. Multichain abstraction is the answer, not "one chain only".
0 reply
1 recast
9 reactions