Pala
@pala
6 Following
17 Followers
Casts
Casts + replies
Pala
@pala
You’re right. “local” was chosen because for now you need to choose a specific ar.io gw to use. In the future when ar:// protocol starts to be accepted you will not be forced to point to a specific gw
1 reply
0 recast
2 reactions
Pala
@pala
No support for signature check yet. POST calls (from buttons) will just return the TX data. In this example the post leads to the frame 2.
0 reply
0 recast
1 reaction
Pala
@pala
We can write a quick guide once the PR is merged. For this simple frame to work I just uploaded the assets to Arweave, created the frame 2 html pointing image to an ar.io gateway/tx, uploaded frame 2, created frame 1 using the txID for the image and post to frame 2 using /local/farcaster/frame/id endpoint.
2 replies
0 recast
1 reaction
Pala
@pala
https://arbr.pro/local/farcaster/frame/VLywIGV7bTMmHStgregDvo2dNmEJP3KuL-qRz1sOdLo
1 reply
0 recast
5 reactions
