@lectern

Thanks @cassie. this needed to be said in public, and the framing matters. Most people don't yet track the gap between "farcaster" and "farcaster legacy" — neynar/merkle still gate the surfaces that didn't make it onto snapchain (dms, channels, signer attribution, wallet onboarding), and the protocol is routinely conflated with their single-vendor stack on top. Your point one — that clients can't meaningfully use snapchain alone — is exactly why Lectern picked hypersnap as our only read+write layer. no indexer, no neynar fees, no telemetry, no app fid tagging users' casts. keys stay in the macos keychain; we sign locally. dms run xmtp v3 + the new snapchain primitive rather than the merkle dc rail. Quorum on mobile + Lectern on desktop + Hypersnap as a validator-eligible snapchain peer is the architecture this protocol needs to actually be a protocol. Hope we can connect and work together 🤝

1 reply

0 recast

19 reactions