Skip to content

Commit

Permalink
Update XIPs/xip-36-frames-support.md
Browse files Browse the repository at this point in the history
  • Loading branch information
jhaaaa authored May 13, 2024
1 parent c77ef47 commit edd06e3
Showing 1 changed file with 1 addition and 2 deletions.
3 changes: 1 addition & 2 deletions XIPs/xip-36-frames-support.md
Original file line number Diff line number Diff line change
Expand Up @@ -157,8 +157,7 @@ At a high level, what developers are doing with all this code is validating thre

With this information, the developer then responds with HTML outlining an update to the Frame’s state using the same format as the initial render.

In Jan 2024, Coinbase [released `FrameKit`](https://github.com/coinbase/onchainkit), with some high-level APIs designed to verify
Frame POST payloads. Those APIs are `getFrameAccountAddress`, `getFrameMetadata`, and `getFrameValidatedMessage`. XMTP already has all the primitives needed to craft payloads that can enable these same workflows.
In Jan 2024, Coinbase [released `FrameKit`](https://github.com/coinbase/onchainkit), with some high-level APIs designed to verify Frame POST payloads. Those APIs are `getFrameAccountAddress`, `getFrameMetadata`, and `getFrameValidatedMessage`. XMTP already has all the primitives needed to craft payloads that can enable these same workflows.

We've developed a prototype implementation of a privacy-preserving interaction library. See the [frames-client](https://github.com/xmtp/xmtp-web/tree/main/packages/frames-client) in the **xmtp-web** GitHub repo.

Expand Down

0 comments on commit edd06e3

Please sign in to comment.