Content
@
0 reply
0 recast
0 reaction
Stephan
@stephancill
Something that concerns me about the fc signer architecture is how it increases the attack surface area for your account the more apps you allow to sign on your behalf This limits the propensity for users to try new apps especially if they have a large audience Solutions: portable signers? Permissions? Sessions?
14 replies
7 recasts
55 reactions
vrypan |--o--|
@vrypan.eth
Rough idea, may not be feasible: Right now, a signer can either be approved or removed. There could be an intermediate state, something like "stoped". If a signer is stoped: - New messages signed with it are not valid (but old ones are not pruned) - It can only be removed (not approved again).
3 replies
0 recast
5 reactions
Dean Pierce 👨💻🌎🌍
@deanpierce.eth
Point of clarification here, did you mean "stopped", like "stop", as in "not moving anymore", or did you really mean "stope", like carving out something with multiple layers?
1 reply
0 recast
1 reaction
Stephan
@stephancill
Good question I assumed there was a typo for stopped
1 reply
0 recast
2 reactions
vrypan |--o--|
@vrypan.eth
Sorry guys, yes, stopped :-)
1 reply
0 recast
1 reaction
Dean Pierce 👨💻🌎🌍
@deanpierce.eth
Thanks, makes sense 😁 My brain is weird and went off on a wild tangent trying to make "stoped" work, and it *almost* does. Mining analogies etc. Words are hard, but specs are forever. Remember what happend with "REFERER" 😆 https://en.wikipedia.org/wiki/HTTP_referer
0 reply
0 recast
1 reaction
