Getting Started

Programmable TCP/IP for Web3 Communication

In the digital landscape dominated by internet giants, users are trapped in walled-gardens, where their data is monopolized and monetized without control. This power imbalance hinders innovation and compromises user privacy and autonomy, piling up data costs and fostering dependency on trust.

Sending Labs is a product studio dedicated to developing decentralized internet and encrypted real-time communication (RTC) infrastructure for Web3 projects. Games, wallets, DEXs, dApps, and communities harness Sending Labs’ product family to enhance chat, trade, and payment functionalities, ensuring users maintain ownership of their data. Cost-effective data solutions are also provided, leveraging idle bandwidth for both developers and users.

Our infrastructure integrates application layer, protocol layer, and DePIN layer.

Application Layer:

Our application features SendingMe, an all-in-one app for everything web3. As the next-generation decentralized and encrypted instant messenger, SendingMe is the first demonstration app built on SendingNetwork.

SendingMe offers a seamless solution for chat, payments, and transfers with a single blockchain account, surpassing Web2 capabilities by embracing both blockchains and CEX. With a $150 billion Web2 RTC market, our decentralized communication solution has immense potential.

It ensures anonymity through wallet addresses, ideal for high-privacy scenarios like Web2 voice rooms, and uses the same account for tipping and payments. End-to-end encryption guarantees absolute communication privacy. This innovative business model has billions of dollars in potential. It also features a unique social mining system, allowing KOLs, communities, and users to interact, earn rewards, and migrate their social graphs through airdrops.

Protocol Layer:

At the protocol layer, SendingNetwork is the core RTC protocol, widely used for communication. It supports games, wallets, DEXs, dApps, and communities, enhancing chat, trade, and payment functionalities while ensuring data ownership. This layer is highly extensible, including VPN, DNS, HTTP, and other protocols. We optimize secure communication protocols like SSL/TLS with on-chain verification, gradually replacing IP addressing with a decentralized, wallet-based protocol.

DePIN Layer:

At the DePIN layer, our Edge Router, a web3 hardware miner, is designed to replace household routers, optimizing idle bandwidth and reducing data costs, creating long-term value for both users and the developer ecosystem. This hardware enhances unused bandwidth, incentivizing sharing and enabling hosting of websites and applications without IP address limitations. SendingNetwork uses a blend of PoW and PoS, where staking engages common users and enhances token utility, creating a robust tokenomics system.

The growing popularity of IoT, cheaper hardware, and increasing smart home devices make DePIN a practical solution. Capturing just 1% of the market represents a $1.5 billion opportunity. Beyond communication, this hardware can expand to include computation and storage modules, offering versatile functionality for the decentralized web.

SendingNetwork client SDK

Web3 application developers can add chat and other communication facilities into their apps using SendingNetwork’s SDK and APIs. Take a look at our SDK quickstarts and explore the source code on GitHub.

JavaScript client SDKiOS client SDKAndroid client SDK

We also provide a customizable website chat widget that you can easily integrate into your website and enjoy the experience of Web3 messaging in a couple of lines of code.

Website chat widget SDK

GitHub

Join the GitHub Discussion to get technical help and share best practices and tips. Follow the project, file bug reports, submit feature requests, or contribute code. If you are excited about SendingNetwork, help us grow the community by starring the Projects.

Twitter

Follow @Sending_Network to stay up-to-date on all news and updates.

Telegram

Join our official Telegram group to discuss any questions about the protocol, SDKs, etc.

Last updated