The problem TradeTalk solves

Problems

1. Lack of Verifiable Proof in P2P Deals
2. Screenshot Evidence is Easily Manipulated
3. No Onchain Record of Peer Agreements
4. Identity Switching & Pseudonymity are Needed

Solution

1. Verified, Secure Conversations with Onchain Proof
2. Agent-Powered Deal Finalization and Metadata Handling
3. Multi-Identity and Role Switching for Flexible Participation
4. Fully Integrated with XMTP

Description

Online marketplaces today rely on scattered conversations across insecure platforms like Telegram or Discord, where deals are often informal and vulnerable to disputes. Buyers and sellers negotiate in private chats, but there’s no reliable proof that an agreement was actually made. TradeTalk solves this by making every deal happen inside a secure, encrypted conversation, powered by XMTP.

Using an onchain agent, buyers and sellers can negotiate confidently, knowing that when they’re ready, they can trigger the /finalize command.
This command is used to cryptographically sign the agreement, generating an immutable Proof of Conversation onchain.

This ensures that no one can later deny or alter the agreement, eliminating disputes and establishing trust by default. With TradeTalk, informal chats become formal, verifiable transactions, protected by cryptography.

Future Enhancements

1. Escrow Payment Layer
   Integrate optional onchain escrow for high-value transactions, providing additional assurance for buyers and sellers.

2. Automated Dispute Resolution
   Build DAO-governed or agent-assisted dispute resolution systems leveraging Proof of Conversation for fair settlements.

3. Cross-Chain Messaging & Payments
   Enable interaction across multiple chains (e.g Base, Ethereum, Polygon),allowing users to transact in their preferred ecosystems.

4. Referral & Affiliate Rewards
   Introduce onchain referral systems to incentivize network growth, with programmable commission splits.

Challenges I ran into

One of the major challenges in building TradeTalk was designing a smooth and secure wallet connection experience for users who may need to operate under multiple identities or roles (buyer, seller etc.) within the same interface. Managing multiple wallet connections while avoiding confusion in the user experience required careful planning .

Another significant challenge was that since these conversations happen offchain for privacy reasons, we needed to architect a flow where only the cryptographic hash of selected chat content was stored onchain. Coordinating this securely between both parties via the /finalize command introduced complexities around user authentication, signature collection, and race conditions in execution.

We also had to ensure that the proof-of-conversation mechanism balanced privacy with verification. Users don’t want their entire chats exposed, but they do want strong, immutable proof in case of disputes. Creating a flow that clearly communicated what was being hashed, how signatures worked, and how to present that onchain required several iterations in both technical logic and user interface design.

Lastly, since this concept is relatively new for typical crypto traders or marketplace users, a key challenge was user education: making it clear why /finalize matters, why users should bother generating a proof before disputes happen, and how this builds trust in decentralized commerce.We created a proper documentation for it.

See our architecture diagram for the solution to first 3 challenges