KMac🍌 ⏩
@kmacb.eth
Been thinking about the Warpcast ↔ Farcaster naming debate. If you don’t love the Warpcast brand, change it — that’s an app-level decision. But I don’t think this is a market problem. Feels more like an internal team identity crisis than anything external. The confusion isn’t from users — it’s from how the Merkle Manufactory team talks about what they’re building. The framing is nearly always protocol-first, never app-first. That works for devs, but it’s disorienting for regular users trying to make sense of what they’re using. If the concern is app adoption or brand clarity, the answer isn’t to rename the protocol. It’s to embrace the app. Let Warpcast be Warpcast — and speak to people like it’s an OS for the crypto social internet. Let Farcaster be the rulebook underneath (verify / store / forward… oh snap! consensus). It’s still early. There are wrong moves. Let’s not collapse layers just because they’re currently close. Growth will pull them apart anyway.
5 replies
0 recast
12 reactions
Dan Romero
@dwr.eth
> The confusion isn’t from users — it’s from how the Merkle Manufactory team talks about what they’re building. The framing is nearly always protocol-first, never app-first. That works for devs, but it’s disorienting for regular users trying to make sense of what they’re using. The challenge is 4 years of brand equity only talking about Farcaster. Seems silly to throw away when the top request from developers is overwhelmingly grow users. This helps that.
1 reply
0 recast
0 reaction
KMac🍌 ⏩
@kmacb.eth
Sounds like you've decided.
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
I have an opinion and I'm free to debate it?
1 reply
0 recast
1 reaction
KMac🍌 ⏩
@kmacb.eth
oc you are free to debate it I'm glad to see you're reaching out for help here & do hope you seek it from pros the people will tell you they want faster horses
0 reply
0 recast
0 reaction
