0 reply
20 recasts
20 reactions
My 2c on Farcaster vs Warpcast & how it relates to building a multi-client protocol:
🤷♂️ Clients don’t always have to read all state or perform all writes. ETH has multiple client types, and FC protocol can too.
🌏 Under this framework, the protocol already has a much richer ecosystem of clients than it gets credit for. All mini-apps (FKA frames) are clients utilizing some combo of FC's social graph, content, associated wallets, DCs...etc.
🌐 I view Warpcast as a hub through which we view & interact with the FC protocol, not some global reference implementation every other clients has to emulate to give or get value. This has already been true for some time now, and rebranding the app to Farcaster just makes it more clear.
🫵 Permissionless data (and to some extent, writes) means anyone can still build any type of client they want, including one has the exact functionality as Warpcast, just like anyone can choose to run/write any ETH client they want.
Thx for coming to my TED talk. 1 reply
9 recasts
65 reactions
0 reply
0 recast
1 reaction
