@alitiknazoglu

today i spoke with my friends who are actively building here. two of them feel negative and disappointed. one believes that a real "blood change" could bring fresh hype. i asked my friends two questions: 1. "if you stopped building here today, do you have a solid alternative plan?" - two of them said farcaster is a side quest for them. for other one, this was main focus and he said: "i'm done. i’m tired of constant changes driven by an immature ecosystem. we adapted app to base app. then jesse says ‘trade-first’. now we’re here again. no one knows what comes next. activity is down. volumes are bad." 2. "what do you expect from rish?" - all three gave same answer: fair amplification and equal treatment. based on these conversations, here are some my suggestions to build a fair and sustainable builder network: a. ecosystem-level suggestions - builder spotlight: a weekly official livestream by team, amplifying one project at a time. first 20-30 minutes: official updates from host/team. remaining time, live product showcase with a selected builder/founder. selection can be manua in the beginningl / via an application form. - fair & transparent featured mini apps: there should be a clear application form and transparent selection criteria. - fair clanker presales: presales should require an application and proper review. first experience already showed this needs iteration -which is expected- but fairness and clarity are critical. - double down on weekly builder rewards: this is one of strongest levers to keep builders motivated. instead of top 100, top 50 but doubled - official communication channel + devrel: builders need a single, reliable channel and a devrel role to handle technical questions, edge cases and feedback. b. mini app specific improvements - add a smart_contracts field to farcaster.json. why it matters? right now farcaster team manually adds system contracts so apps automatically get the “via xxx app” attribution in wallet history. i flagged inflynce’s new payment contract three times but it still wasn’t added. this should be scalable and automated, not manual. it would help every builder maintain accurate attribution across ecosystem. base app could also read this info from farcaster.json and reflect it in base wallet history. that way it becomes protocol-level metadata instead of something handled app by app. - add token_contract and founder_fid fields to farcaster.json. this would help verify. official tokens, legit founders and significantly improve security and trust. - mini app trending algorithm. mini app trending algorithm should count transactions processed by apps, not only farcaster wallet-signed ones. why it matters? current ranking heavily favors transactions signed through farcaster wallet + unique dau (less than tx). transactions processing through an app’s own smart contracts are not counted, even when they create real onchain economic activity. if team maps app-related contracts and includes those transactions, trending algo becomes a far more accurate reflection of which apps generate real value, not just -empty- signature events. that's why everyone adds claim function to their mini app. - to support discovery, new mini apps (eg. manifest age < 45 days) could receive x2 visibility boost in trending. needs a balance between new apps <> og apps.

4 replies

5 recasts

20 reactions