Content
@
0 reply
5 recasts
5 reactions
David Furlong
@df
That was a quick copy https://reflect.site/g/yoginth/hey-portal-open-graph-spec/cd7225f128274da382f1f516e7e63f15
4 replies
0 recast
8 reactions
Gabriel Ayuso ⌁
@gabrielayuso.eth
Frames in their current form are extremely simple and built on OpenGraph so it'll be easy for anyone to implement them. The main issue Lens clients like Hey will have is that they all work with external wallets so they'll require users to sign a msg. Big problem with Lens UX in general.
1 reply
0 recast
4 reactions
defispartan
@defispartan
Not necessarily, a Lens profile can set a dispatcher address (most commonly Lens API) so authentication can be handled external to the wallet (access tokens). I personally don’t set a dispatcher because I want complete self-custody, but it’s an option.
1 reply
0 recast
0 reaction
Gabriel Ayuso ⌁
@gabrielayuso.eth
Right but this is part of the Lens API. So the client can just exchange a signed message for an API token that can then be used by the Lens API to do the dispatching, etc. Any action outside the Lens API, such as signing a message for a Frame/Portal, has to be performed by the client which doesn't have the key.
1 reply
0 recast
0 reaction
defispartan
@defispartan
The Portal verifier could recognise the dispatcher as a valid signer: Use access token to request signed message from dispatcher -> verifier checks if message is signed by user or user’s dispatcher
1 reply
0 recast
1 reaction
Gabriel Ayuso ⌁
@gabrielayuso.eth
Are there alternatives to the Lens API yet?
1 reply
0 recast
0 reaction
defispartan
@defispartan
Not that I’m aware of, but there are apps like this Hello World open action with no API dependency (all on-chain) and I hope to expand on this in the near future https://github.com/defispartan/lens-hello-world-open-action
0 reply
0 recast
0 reaction
