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
31 recasts
247 reactions

​woj pfp
​woj
@woj.eth
also doesn't serve me to say this because i have money in both projects, and it probably costs me some friendship points with jacek and deployer but i feel very strongly about this and i want others to avoid following this path just build on base, it's already hard enough
9 replies
6 recasts
111 reactions

sean 🔹 pfp
sean 🔹
@swabbie.eth
why is pushing the limits of current infra technology selfish? this is a weird take from someone building on new technology for early adopters. there will always be pain points when building at this forward end of the technology curve building many chains is the entire growth strategy that the ethereum foundation has chosen to pursue. it won't all magically happen with all the pieces working at the same time. someone has to build new things first. i'm glad those people are a part of farcaster ask alchemy or infura to support them, don't stop the builders
2 replies
1 recast
29 reactions

tldr (tim reilly) pfp
tldr (tim reilly)
@tldr
Still love degen of course, but from someone building on top of it I agree with this take. Degen chain has only caused us headaches, not upside. Would be curious what @kenny thinks as a builder who actually integrated degen chain into a working product.
1 reply
1 recast
36 reactions

Corbin Page pfp
Corbin Page
@corbin.eth
Respectfully disagree. You're feeling the same thing any wallet/app builder is dealing with wrt multiple chains right now. The FC ecosystem is a small subset of the annoyances of building across 10s of EVM chains and even the altVMs as well. Chain abstraction makes this A LOT easier (cc @decentxyz) but this is the market figuring out what works and what doesn't. It's decentralized coordination playing out.
2 replies
1 recast
27 reactions

Nick T pfp
Nick T
@nt
only cast on Warpcast guys, let's keep all the attention liquidity in one place instead of fragmented. sucks having to support multiple clients as a dev 😵
1 reply
0 recast
14 reactions

Rob Sanchez pfp
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

Stephan pfp
Stephan
@stephancill
Degen chain was so forced that the chain launched and was missing the only use case for degen (tips) Only use case for degen chain today is for bridging companies to make money from fees on every round of airdrops unfortunately Total distraction and waste of resources
0 reply
0 recast
12 reactions

Matthew Fox 🌐 pfp
Matthew Fox 🌐
@matthewfox
We did this from day 1 of DL3 w/jeeves Eh it's not pleasant sometimes (most bugs after were DL3 adjacent) but i dont think its reason for them to not exist Although infra not supporting ham was the only reason we didn't support ham It's definitely easier to handle with smart wallets than EOAs
1 reply
0 recast
11 reactions

Will Papper pfp
Will Papper
@will
I of course have a point of view here, but only because it comes from a deeply-held belief that communities should be able to own their chains. On the integrations side, people were saying the same thing about L2s being more difficult to integrate than ETH Mainnet. Ultimately, fee reductions and the subsequent user demand led the infrastructure providers to add multi-chain support, but it assumed a few large L2s. Now that we're seeing the proliferation of many L2s and L3s, infrastructure providers will need to evolve again. Just like how L1 -> a few big L2s required some work to operate smoothly, a few big L2s -> many L2s and L3s will require work as well. So where does the user demand come from? In my opinion, it's things that are impossible on large L2s. Ham putting FID data onchain is the perfect example. Only a tiny fraction of the world is onchain. If we don't pursue L2s and L3s, we will hold back the space in its onchain potential. Moving more communities onchain is why many L2s and L3s must exist.
1 reply
2 recasts
8 reactions

Jonny Mack pfp
Jonny Mack
@nonlinear.eth
same situation w/ embedded wallets. lots of incentives to launch your own chain. 0 incentives not to. tragedy of the commons
3 replies
0 recast
10 reactions

Kieran Daniels 🎩 pfp
Kieran Daniels 🎩
@kdaniels.eth
“Don’t innovate” 🙃
0 reply
0 recast
8 reactions

czar  pfp
czar
@czar
the more appropriate question in my opinion is - was it the right time to launch these chains? well intentioned ideas from smart people are generally good, it’s just the timing for most.
0 reply
0 recast
6 reactions

Jacob pfp
Jacob
@jrf
big crypto pain point is the high cost of sponsoring fees to improve ux, and provide seamless account abstraction the L3s seem to have solved that, but added developer work bc new infra base can solve this for apps with few txs, but sponsoring ~8 cents per user tx is not practical for most onchain apps why not both?
0 reply
0 recast
2 reactions

Brian Kim pfp
Brian Kim
@brianjckim
strongly agree
0 reply
0 recast
2 reactions

Connor McCormick ☀️ pfp
Connor McCormick ☀️
@nor
BUT MY BAGZZZ
0 reply
0 recast
1 reaction

Satoshi Tomatomoto pfp
Satoshi Tomatomoto
@tomato.eth
I don't really understand the reason to create your own L3 chain. What does it accomplish?
0 reply
0 recast
0 reaction

limone.eth 🍋 pfp
limone.eth 🍋
@limone.eth
agreed, chain abstraction is already hard within L2s, with also L3s in the game 🤯
0 reply
0 recast
0 reaction

petar.xyz pfp
petar.xyz
@petar
I’m glad you wrote this I completely agree with you The Degen chain is a big flop 🤷🏻‍♂️
0 reply
0 recast
0 reaction

albi is /nervous pfp
albi is /nervous
@albiverse
genuine question: where does it make building supercast more difficult?
0 reply
0 recast
0 reaction