Farcaster Devs

Channel gating ideas

People are going to get very creative.

any future for gated channels where casts are private at the protocol level?

direct casts is one option, but has a number of ux drawbacks

andyjagoe.com // denim.vc // tokenizing real-world assets / onchain venture funds @fairmint

You could build a client that encrypts cast content and decrypts it within your client.

that’s an amazing idea

maybe we’ll build this at Fairmint for founders to communicate with investors and GPs to communicate with syndicates/LPs

anyone know what the most popular tools for this are today?

This is easier to say then it is to implement.

If you need it to scale encrypting a cast for many people runs into a lot of complexity.

encryptedchannel

tZpZ32KQfZ++/4VlB7qNA2KI2+FDqGpwpal3t1ru5YeJvJkzk56KUhPU9ZF3EFloMacWBwh3qyXGcNAGegAx0WEX2t4uKJx77b5E53I=

I feel like a static symmetric key per channel is fine. It means you can't remove people etc, but it works fine for certain use cases. I spent a bit of time working on something like that a few months ago.

Working on building zkTLS infra/products. A ruthless empiricist and meme connoisseur.

http://opacity.network

I can easily recast everything into a different channel where it’s decrypted and no one would know who’s leaking it.

I don’t know why you’d want to do that will a separate client

I feel like a static symmetric key per channel is fine. It means you can't remove people etc, but it works fine for certain use cases. I spent a bit of time working on something like that a few months ago.

https://warpcast.com/deanpierce.eth/0xc7bd00ec

https://github.com/Hmac512/broadcast-encryption-boneh

Requires a new key type