Content
@
0 reply
20 recasts
20 reactions
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
58 recasts
384 reactions
Rob Sanchez
@robrecht
have some similar annoyances - for paybot commands (e.g "@paybot 100 degen") we don't know if the user wants to send it on base or the L3, so we need to make assumptions based on their balances - supporting tokens on degen L3 in @swapbot is hard because it's not supported in 0x.org (which is a great product and we love) more complexity and worse ux in general
3 replies
1 recast
14 reactions
woj
@woj.eth
🎯🎯🎯
0 reply
0 recast
4 reactions
Jacek.degen.eth 🎩
@jacek
Just curious—when someone sends USDC, can they specify the chain? Thinking adding the chain to the command could make sense, and if none is specified, default it to Base?
1 reply
0 recast
4 reactions
Brock The Breadcat
@breadcat
they should make the L3 token $D3gen.
0 reply
0 recast
2 reactions
