Content
@
https://warpcast.com/~/channel/fc-devs
0 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Can the miniapp sdk provide a proof to the miniapp that the context is provided by a specific client? I think it's trivial to fake that you are a "legit" client sending data to a miniapp. This may not be critical in the onchain-tx way, but it can spam, overload, or fake data that are important for a miniapp. It would be nice if frameContext was signed by frameContext.client.clientFid, to allow a miniapp verify that the context can be trusted IF they trust clientFid.
4 replies
0 recast
2 reactions
cashlessman ๐ฉ
@cashlessman.eth
this?
1 reply
0 recast
0 reaction
vrypan |--o--|
@vrypan.eth
Yes. But anyone can say they are fid 9152. I can make a web app that allows you to enter a mini app URL, and opens it with random fids, and says it is 9152 (warpcast). See? You paid me $200 through amps but it was worth it, you got 20k opens for your app.
2 replies
0 recast
1 reaction
Steve
@stevedylandev.eth
Yeah at the moment SIWF is the only way to verify who someone is, and from there you can define some of that context, but itโs not the same as having a signed payload like v1 frames. Definitely sorting I missed the most.
0 reply
0 recast
0 reaction
barabazs
@barabazs.eth
Hey @apoorvlathey can you vibe ship a Warpcast impersonator.xyz? ๐๏ธ
0 reply
0 recast
1 reaction