Skip to content

Commit f42a00b

Browse files
authored
Update formatting
1 parent 2545e79 commit f42a00b

File tree

1 file changed

+28
-27
lines changed

1 file changed

+28
-27
lines changed

src/pages/identity.mdx

+28-27
Original file line numberDiff line numberDiff line change
@@ -1,10 +1,13 @@
1-
<aside>
1+
# Identity
2+
3+
::: caution
24
**Key Takeaways**
35

46
- **Why it matters:** XMTP unifies messaging for all your web3 names in one inbox, making it easy to manage communication across apps.
57
- **How it works:** Wallets and names link to a single identity using secure operations verified by wallet signatures.
68
- **Future-proof:** Ephemera will seamlessly transition identity to the XMTP appchain in 2025 for enhanced security and censorship resistance.
7-
</aside>
9+
10+
:::
811

912
Web3 users maintain different names across their communities - a .base.eth name for Base, Lens and Farcaster handles for social, a .eth name for general use. These names become truly valuable when people can use them to communicate. But apps that support only one name system fragment the messaging potential of web3 names.
1013

@@ -57,11 +60,10 @@ SDKs will maintain the same simple operations, allowing identity association his
5760
- Watching chain events and building their own state tracking
5861
- Using third-party APIs to retrieve the latest state
5962
- Accessing state permissionlessly via a community-provided subgraph
60-
63+
6164
Messaging app developers can also verify the SDK using these methods.
62-
6365

64-
**Privacy considerations for onchain identity**
66+
### Privacy considerations for onchain identity
6567

6668
Users concerned about linking public and private wallets onchain can create separate XMTP identities for sensitive communications. However, apps catering to these users can merge their identities locally into a single inbox. Future updates may introduce privacy-preserving features for unlinkable identity associations to address these concerns while maintaining a unified inbox.
6769

@@ -94,55 +96,54 @@ List all wallet addresses and names that can message from a given XMTP inbox:
9496
## Frequently Asked Questions (FAQ)
9597

9698
1. **What differentiates XMTP’s approach to identity? What are its benefits?**
97-
99+
98100
Unlike traditional systems that bind user identity to a proprietary namespace, XMTP's identity model leverages existing namespaces. Users can consolidate all their names into a single messaging inbox managed by one wallet key, using different names for different contexts.
99-
101+
100102
Benefits for users:
101-
103+
102104
- Receive all your messages without switching apps.
103105
- Communicate using any name you own.
104-
106+
105107
Benefits for apps and services:
106-
108+
107109
- No need to build and maintain your own messaging system.
108110
- No need to integrate a new namespace.
109111
- If you have a namespace, XMTP makes it more valuable by extending its reach to more apps.
110112
- Users can communicate using all their names without switching to other apps.
111113
- Users can access existing agents and mini-apps developed by the XMTP community.
112114
2. **How secure is this system? What happens if one of my linked wallets gets compromised?**
113-
115+
114116
XMTP requires a signature for every identity operation. The SDKs automatically verify and replay identity updates, ensuring all changes are authorized. If a wallet linked to an identity is compromised, the recovery wallet can unlink it to protect the inbox. By default, the recovery walelt is the wallet that created the identity.
115-
117+
116118
3. **How do I recover my identity? What if I lose access to my recovery wallet?**
117-
119+
118120
The first wallet associated with an identity becomes the recovery wallet. This recovery wallet is the only one that can remove other wallet associations. It can also change the recovery address to a different wallet address. If access to the recovery wallet is lost, you can continue using your inbox with other linked wallets, but you won't be able to revoke other wallet associations in case of compromise.
119-
121+
120122
As a last resort, you can create a new inbox and associate your wallet addresses to it. This ensures continued messaging access, though previous messages tied to the original inbox will remain inaccessible.
121-
123+
122124
4. **Can smart wallets or other smart contracts have XMTP identities?**
123-
125+
124126
Any EIP-4337 smart wallet can create or link to an XMTP identity and send or receive messages. Other smart contracts can also do this if they support EIP-1271.
125-
127+
126128
5. **How does wallet linking work across chains?**
127-
129+
128130
Messages sent to any address are delivered to its associated inbox, regardless of the wallet app or blockchain used. Currently, XMTP supports only EVM chains. However, XMTP aims to extend support to wallets on non-EVM ecosystems by late 2025. This expansion will further enhance cross-chain messaging and broaden accessibility.
129-
131+
130132
6. **What is the maximum number of wallets that can be linked to an identity?**
131-
133+
132134
The XMTP identity system has a maximum limit of 256 wallets that can be linked to a single identity. Revocations and recovery address changes count towards this limit.
133-
135+
134136
7. **Are there any rate limits for identity operations?**
135-
137+
136138
Yes, Ephemera’s centralized service has rate limits in place to ensure system stability under heavy usage. When the system transitions to the XMTP appchain in 2025, rate limiting will be managed through gas fees for each operation.
137-
139+
138140
8. **What happens during the 2025 appchain transition?**
139-
141+
140142
The transition to the XMTP appchain will be seamless for users and developers. Existing identities will automatically migrate without disrupting functionality. The SDK interface will remain unchanged, and detailed migration guides will be provided to ensure smooth adoption.
141-
143+
142144
9. **What costs will be associated with identity operations?**
143-
145+
144146
Currently, wallet linking and unlinking operations are free. However, when the system transitions to the XMTP appchain, these operations will incur small gas fees, likely fractions of a cent. To ease user onboarding, applications can register on-chain as fee payers, covering these costs for new users during sign-up.
145-
146147

147148
**10. How public is my identity association history?**
148149

0 commit comments

Comments
 (0)