fc-updates

We're planning to move forward with rebranding the Warpcast mobile and web app to Farcaster.

1. Nothing is changing any time soon. We will take our time with this and have plenty of communication about it across multiple channels. The earliest the change will happen is mid-May, but a decent chance it happens in June.

2. We're going to work on a plan over the next 2 weeks and should have a plan by the next developer call on May 8, 2025. We will discuss on the call.

3. For developers: we're planning to open source the client monorepo— i.e. the mobile and web apps. Again, no timeline on this yet.

Co-Founder 

Contact: https://alice.chain.box

Working on Farcaster and Warpcast. Longer thoughts at https://dwr.email

As previously discussed, we're considering renaming the Warpcast app to Farcaster.

Why?
- Top priority is grow users on the protocol
- The name split is extremely confusing for new users
- So, we want to simplify

How we're thinking about it
- Rename Warpcast mobile app
- warpcast.com to farcaster.xyz for web app
- Open source both apps
- No change protocol name, i.e. similar to Uniswap with app / protocol

What we’re doing
- Seeking input and want to make sure we understand concerns 
- Ultimately Varun and I will make a decision; it won’t be a vote.
- Expect a decision in the next week or so; if yes, we will give plenty of notice and will take time to do this correctly / cleanly.

How you can provide input
- Developers: please reply here or feel free to reach out to me via direct message whether you agree or disagree.
- Everyone else: you're free to offer input, but we will be weighting developer input a bit more since it has a bigger near-term impact on what they are building

Nearly every active client developer agrees with the change? Look at the replies to this cast.

So the argument is theoretical?

Nearly every active client developer agrees with the change? Look at the replies to this cast.

So the argument is theoretical?

https://warpcast.com/dwr.eth/0xbb2ee1c4

Bad for new clients, because the name is associated with the protocol. Which means new clients have an even bigger uphill battle. Also I think the protocol should not share a name with a client