Now we have made a crucial step towards solving the communication problems in Web3. By integrating XMTP with CyberConnect, we enable secure & private peer-to-peer messaging across nodes in a decentralized social graph.
A collectible version of this article is available on Link3. You will also be able to comment, like, and subscribe to the author on Link3.
In the current state of Web3, communication between identities is extremely difficult. A stark example of this was when Solend (Solana-based lending platform) attempted to communicate with a whale whose imminent liquidation risked crashing the entire protocol, and
... attempted to communicate with the wallet owner numerous times over the past few days. The DeFi platform put a message on Twitter as well as sent an on-chain transaction with a memo (source)
There are two components required to build this kind of service in Web3. The first is a widely adopted DID system for discovering & resolving identities. The second is a secure & private way to message between those identities.
While CyberConnect offers a decentralized social graph protocol that includes a DID system (built around the ERC-721 compliant ccProfile), it currently lacks a peer-to-peer communication system. Likewise, XMTP offers a decentralized messaging protocol for secure & private peer-to-peer messaging between Web3 identities, yet it lacks a widely adopted DID system. This is where the integration of CyberConnect & XMTP comes in.
One of the key benefits of XMTP is its extensible design, which enables a diverse set of use cases for sending message data between Web3 identities. XMTP also provides a high degree of security and privacy by using encryption and authentication mechanisms to protect message data from unauthorized access.
Integrating XMTP with CyberConnect has several benefits. Firstly, it enables secure, peer-to-peer messaging over a decentralized network of nodes. This means that messages are not stored on a central server, and there is no need for a third party to handle messages. Secondly, it ensures that messages are delivered securely to the intended recipient, as the ccProfile handle is used to resolve EVM addresses to identities. Finally, it ensures that messages are tamper-proof, as XMTP uses encryption to ensure that messages are only readable by the intended recipient.
Putting the two together, and modifying the CyberConnect protocol to include XMTP private messaging, we can ensure that messages are securely delivered to the intended recipient, without any third-party involvement.
Enabling secure & private peer-to-peer messaging across nodes in a decentralized social graph is a crucial step towards solving the communication problems in Web3.
If you’re a developer, you can right away with our Integrating XMTP with CyberConnect dev doc here.
About XMTP
XMTP (Extensible Message Transport Protocol) is an open protocol and network for secure, private messaging & notifications between EVM accounts. With the XMTP SDK, developers can enhance their applications with a universal inbox for direct messages, notifications, and announcements, or build new tools for dApps, DAOs, creators, and protocols to re-engage users via Web3 messaging.
About CyberConnect
CyberConnect is a decentralized social graph protocol with identity sovereignty for mass adoption and network effects. It enables users to create profiles as the anchor of users’ decentralized identities. With CyberConnect, users own their social graph, content, monetization channels, and social data allowing them to travel across several dApps seamlessly without having to recreate their network on every new platform.
CyberConnect protocol was launched in November 2021, as the first social graph protocol published. As of Mar 13th, 2023, CyberConnect has 350k user profiles and 290k monthly active users who have done more than 2.8M transactions.
Website | Docs | Twitter | Medium | Mirror | Discord | Telegram | Newsletter
A collectible version of this article is available on Link3. You will also be able to comment, like, and subscribe to the author on Link3.