Identity Verification

Background

With the development of web3, security issues have come to the fore. Phishing scams are increasing, and various attack techniques have emerged. A web2 platform does not relate the user’s account to the wallet address, leading to a possible risk of scams and a disjointed user experience. Scammers could impersonate popular personalities or project admins after a user publicly asks for community help, and trick the user into sending funds.

Sending.Network aims to solve this issue by combining messaging along with verification to authenticate wallets and contract owners.

Below we provide a specific use case describing how the user gets verified support from authenticated project customer service in a wallet app.

Use Case Name

Authenticate the official customer support.

Actors

1. Wallet app

2. Wallet user

3. Project customer support

4. Sending.Network protocol

Preconditions

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

Basic Flow of Events

1. The use case begins when the user searches for the official project support account, usually ENS, inside the wallet.

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

3. Sending.Network broadcasts the peer ID of the customer support account and locates its client.

4. Sending.Network creates a topic for the sender and receiver and establishes communication.

5. User enters the messaging window inside the wallet.

6. User sends a message for support.

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

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

9. Customer support gets the message and responds.

10. The user receives the response and starts chatting.

11. The use case ends successfully.

Flow Chart

Post-conditions

The user successfully receives the response from official customer support.