Content
@
0 reply
20 recasts
20 reactions
vrypan |--o--|
@vrypan.eth
Is there an app to manage signers? Like "these keys have permission to add/remove casts on your behalf"? It would be nice to have an independent way to manage/check/revoke signers.
1 reply
0 recast
1 reaction
Dan Romero
@dwr.eth
It’s built in to Warpcast mobile but easy enough to build outside of Warpcast since all the data is onchain.
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
I did not know it. Nice!
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
But, what does this mean? Are they actually invalidated at the protocol level? Does this mean that if an app gets compromised, and users have to disconnect, all activity created through the app will be gone?
3 replies
0 recast
0 reaction
Dan Romero
@dwr.eth
Yes you generate an OP Mainnet transaction and we (Warpcast) pay for it.
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Isn't this sort of an existential risk? Let's say I use an app that I trust and everything's fine. Later the app is sold to someone I don't trust. If I disconnect, all my activity will be gone. If I don't, someone I don't trust has full control over my farcaster activity. Is there a workaround?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
User-controlled and manual revocations or 3rd party controlled and automatic revocations. Pick your poison. OAuth has worked OK for web2 social media fwiw
4 replies
0 recast
1 reaction
vrypan |--o--|
@vrypan.eth
I'm trying to get the whole image. Based on the protocol docs how is this case handled? 1. CAST_ADD signed by warpcast 2. CAST_REMOVE signed by opencast 3. SIGNER_REMOVE opencast Is my cast visible now or not?
1 reply
0 recast
0 reaction
Dan Romero
@dwr.eth
Opencast is not a Farcaster wallet. You need your Farcaster recovery phrase (i.e. mnemonic) to perform the onchain actions. Signers allow writes to Hubs but not onchain.
1 reply
0 recast
0 reaction
