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] 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: