From 7455b8f6f6fec0fdcf0aaad184c7ab61a335cc9c Mon Sep 17 00:00:00 2001 From: Nicholas Molnar <65710+neekolas@users.noreply.github.com> Date: Tue, 20 Feb 2024 18:05:00 -0800 Subject: [PATCH 1/3] Small docs update --- site/docs/pages/xmtpkit/introduction.mdx | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/site/docs/pages/xmtpkit/introduction.mdx b/site/docs/pages/xmtpkit/introduction.mdx index 61b4bb83af..0e8e187c40 100644 --- a/site/docs/pages/xmtpkit/introduction.mdx +++ b/site/docs/pages/xmtpkit/introduction.mdx @@ -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`. + ::: -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: From 2d013557b2e202fc5ff78ac82d1d308e779dbef0 Mon Sep 17 00:00:00 2001 From: Nicholas Molnar <65710+neekolas@users.noreply.github.com> Date: Tue, 20 Feb 2024 18:06:16 -0800 Subject: [PATCH 2/3] Add link to xmtp docs --- site/docs/pages/xmtpkit/introduction.mdx | 2 ++ 1 file changed, 2 insertions(+) diff --git a/site/docs/pages/xmtpkit/introduction.mdx b/site/docs/pages/xmtpkit/introduction.mdx index 0e8e187c40..9ab8875408 100644 --- a/site/docs/pages/xmtpkit/introduction.mdx +++ b/site/docs/pages/xmtpkit/introduction.mdx @@ -29,6 +29,8 @@ When a user interacts with a Frame inside an XMTP client application, you will n 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 handling interactions from XMTP, and extracting the `verifiedWalletAddress` from a POST payload, here is the XMTP Kit which includes: From ff73b44522be7d69f1e109001bfd22388c498963 Mon Sep 17 00:00:00 2001 From: Nicholas Molnar <65710+neekolas@users.noreply.github.com> Date: Tue, 20 Feb 2024 18:08:28 -0800 Subject: [PATCH 3/3] Make single paragraph --- site/docs/pages/xmtpkit/introduction.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/site/docs/pages/xmtpkit/introduction.mdx b/site/docs/pages/xmtpkit/introduction.mdx index 9ab8875408..a593ba875b 100644 --- a/site/docs/pages/xmtpkit/introduction.mdx +++ b/site/docs/pages/xmtpkit/introduction.mdx @@ -25,9 +25,7 @@ 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`. +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).