SendingNetwork
  • OVERVIEW
    • Getting Started
    • FAQs
  • Network Instructional Articles
    • Basics
      • Introducing the Edge, WatchDog, and Guardian Nodes
      • Overview
      • Messaging Solution
      • Privacy Solution
      • Rich Communication Solution
      • Multi-Platform Solution
      • Decentralized Identity
      • Multiple Chat Modes
      • How It Works
      • Token Utility
      • The Team
    • Key Concepts
      • Decentralized Identity
      • Social Graphs
      • Edge Node
  • SDK Documentation
    • Glossary
    • JavaScript client SDK
      • DID
      • User
      • Message
      • Room
      • Contact
      • Social Graph
    • iOS client SDK
      • Push
      • DID
      • User
      • Message
      • Room
      • Contact
    • Android client SDK
      • User
      • Room
    • Java SDK
      • DID
      • Room
      • Message
    • Node.js SDK
      • DID
      • Room
      • Message
    • Unreal SDK
      • DID
      • User
      • Message
      • Room
    • Unity SDK
      • DID
      • Room
      • Message
    • Website chat widget SDK
      • Customization
      • DID
      • User
      • Room
      • Message
      • Other
    • Bot SDKs
      • Golang Bot SDK
        • DID
        • User
        • Room
        • Message
    • Extensible Message Interface
    • Push Notifications
    • Flutter SDK
      • DID
      • User
      • Message
      • Room
    • PHP SDK
      • DID
      • Room
      • User
    • Developer Key
  • Acquisition Kit
    • Social Boost Development Instructions
  • WatchDog Agent
    • WatchDog Agent Guide
    • WatchDog Agent Deployment Tutorial
      • Linux Deployment Tutorial
    • One-Click Deployment
  • Edge Node
    • Edge Node Deployment Tutorial
    • VPS Setup Guide
      • Google Cloud Platform (GCP)
      • Amazon Web Services (AWS)
      • Contabo
    • Check Node Stats with Auto-Reply Bot in SendingMe App
    • Alpha-3 Testnet FAQs
  • delegation node
    • Delegation Node Deployment Tutorial
  • Private Delegation Node
  • Use Cases
    • Wallet-to-Wallet Messaging
    • Dapp Notifications
    • Identity Verification
    • Gamer Acquisition
    • Cross-platform Trading
Powered by GitBook
On this page
  • Use Case Name
  • Actors
  • Preconditions
  • Basic Flow of Events
  • Post-conditions
  1. Use Cases

Wallet-to-Wallet Messaging

PreviousPrivate Delegation NodeNextDapp Notifications

Last updated 10 months ago

Built as a crypto native protocol, Sending.Network’s wallet-based Decentralized ID, which is inherently public, supports an assets negotiation and exchange environment that no centralized chat solution can accomplish.

In the Web3 world, chat is not just about sending and receiving messages but a means to facilitate asset trading, e.g., in-game NFTs. Imagine your dream NFT is right in front of you, sitting in a wallet address, and you are ready to make a generous offer. But how can you contact the owner? There is no email or cell phone number to use. Wallet-to-wallet messaging enables you to start negotiating with the NFT owner at once.

Below we provide a specific use case describing how the user contacts an unknown wallet address.

Use Case Name

Send NFT inquiry message to an unknown wallet address.

Actors

  1. Wallet app

  2. Wallet user

  3. NFT holder

  4. Sending.Network protocol

Preconditions

  1. The wallet app has integrated the Sending.Network protocol.

  2. The NFT holder has an Sending.Network account.

Basic Flow of Events

  1. The use case begins when the user sees an unknown wallet address with the desired NFT.

  2. The user searches for the wallet address inside the messaging window of the wallet.

  3. The wallet calls the Sending.Network peer discovery API.

  4. Sending.Network broadcast the peer ID of the NFT holder's wallet address and locates its client.

  5. Sending.Network creates a topic for the wallet user and the NFT holder and establishes communication.

  6. User enters the messaging window inside the wallet.

  7. User sends an inquiry message.

  8. The wallet fully encrypts the message and calls Sending.Network message sending API.

  9. Sending.Network forwards the message to the receiver.

  10. The NFT holder receives the message and responds.

  11. The user receives the response and starts the negotiation.

  12. The use case ends successfully.

Post-conditions

The user successfully receives the response from the NFT holder.

Overview
Flow Chart