Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docs update for XMTP Frames #165

Merged
merged 3 commits into from
Feb 21, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion site/docs/pages/xmtpkit/introduction.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,15 @@ yarn add @coinbase/onchainkit @xmtp/frames-validator
pnpm add @coinbase/onchainkit @xmtp/frames-validator
```

[XMTP](https://xmtp.org/) is a wallet to wallet messaging protocol, and many XMTP client applications are adding Frames support.

When a user interacts with a Frame inside an XMTP client application, you will need to handle the payload slightly differently from an interaction coming from Farcaster. The primary identifier for a user on Farcaster is the `fid`, while in XMTP it is the `verifiedWalletAddress`.

You can learn more about how XMTP works with frames in [their documentation here](https://xmtp.org/docs/build/frames).

:::

To assist you in engaging with XMTP, here is the XMTP Kit which includes:
To assist you in handling interactions from XMTP, and extracting the `verifiedWalletAddress` from a POST payload, here is the XMTP Kit which includes:

- [XMTP Kit](/xmtpkit/introduction)
- Utilities:
Expand Down
Loading