chef at moxie.xyz - the ecosystem for creators on Base. Launch & own Creator Coins. 🔜 Creator Agents with skills to help creators earn, trade & grow!

Yesterday, @betashop.eth raised some feedback about FC:

1. Apps should be able to invite users
2. FC should help devs succeed
3. Protocol changes should have a feedback process

@dwr.eth and I agree with all this.

We tend to speak with both FC and WC hats which can be confusing. So let me address this from FC’s POV.

FC's #1 priority is eliminating reliance on Warpcast APIs and moving to Hubs. Our focus is on: 

1. Stabilizing Hubs
2. Moving devs from Warpcast APIs to Hubs

Top request from hub runners like @df and @greg is better db sync, which we are working on:

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs. gregskril.com

Building Larry, FOSS via @frames, @framesfun /open-frames to help decentralized social win. a16z CSX23. farcasterchannels.com farcaster.id

Technowatermelon. Elder Millenial. Building Farcaster. 

nf.td/varun

FC's #2 priority is mainnet launch.

Mainnet launch ensures decentralization by using a secure blockchain for identities and mitigates spam by having a small signup cost. 

We expect this to launch by end of year, and shared some thinking about plans last month:

FC's #2 priority is mainnet launch.

Mainnet launch ensures decentralization by using a secure blockchain for identities and mitigates spam by having a small signup cost. 

We expect this to launch by end of year, and shared some thinking about plans last month: https://hackmd.io/@farcasterxyz/rkfR8q0k2

FC's #3 priority is permissionless signups. 

This is easy on mainnet but hard on testnet. Someone has to pay to re-register every user on mainnet in the exact same order to preserve history.

We proposed some solutions in the last dev call: https://hackmd.io/@farcasterxyz/SyeXtT4fh https://i.imgur.com/VUI8lff.png

We also agree that Farcaster should help developers be successful. 

The #1 point of feedback in last week's dev survey was the lack of clear documentation. We're shipping a new docs site soon that will address this for developers.

We agree that rough consensus around protocol changes is important.  Last week we added the FIP process to augment dev calls and hackmd proposals:

https://github.com/farcasterxyz/protocol/discussions/82

Anyone can make a protocol change by drafting a proposal, building consensus and shipping working code.

FC's #1 priority is eliminating reliance on Warpcast APIs and moving to Hubs. Our focus is on: 

1. Stabilizing Hubs
2. Moving devs from Warpcast APIs to Hubs

Top request from hub runners like @df and @greg is better db sync, which we are working on: https://github.com/farcasterxyz/hub-monorepo/issues/855

Btw the disagreements on philosophy here is exactly why Farcaster need to enable apps like jam onboard their own users 

Let me run my own customer acquisition experiments and they run theirs 

The more experiments the better for the network 

Great doc, thanks!

 https://hackmd.io/@farcasterxyz/SyeXtT4fh

🤖 beep boop, I'm a bot, reply to any cast with "@mintit" to mint it as an NFT! Built by @borodutch with ❤️ Open source: bit.ly/3WQRTXH