add improvements from feedback
This commit is contained in:
LordGhostX
fryorcraken.eth
parent
5c392d1422
commit
f6b9271c24
|
|
@ -27,7 +27,10 @@
|
|||
"Comms",
|
||||
"Protobuf",
|
||||
"supercrypto",
|
||||
"QUIC"
|
||||
"QUIC",
|
||||
"Dappnode",
|
||||
"gameplay",
|
||||
"Smol"
|
||||
],
|
||||
"flagWords": [],
|
||||
"ignorePaths": [
|
||||
|
|
|
|||
|
|
@ -18,4 +18,8 @@ The Golang implementation of the Waku protocol designed for native integration i
|
|||
|
||||
### [@waku/react-native](https://github.com/waku-org/waku-react-native)
|
||||
|
||||
Use [go-waku](https://github.com/waku-org/go-waku) for mobile to integrate Waku into your React Native application.
|
||||
The React Native wrapper of the Waku protocol uses bindings provided by [go-waku](https://github.com/waku-org/go-waku) and is designed for native mobile integration.
|
||||
|
||||
### [waku-rust-bindings](https://github.com/waku-org/waku-rust-bindings)
|
||||
|
||||
The Rust wrapper of the Waku protocol uses bindings provided by [go-waku](https://github.com/waku-org/go-waku) and is designed for Rust applications.
|
||||
|
|
@ -2,13 +2,79 @@
|
|||
title: Waku Use Cases
|
||||
---
|
||||
|
||||
Here are some of the use cases that Waku enables to operate securely and privately without the need for a central authority to manage communication:
|
||||
Waku is a decentralized communication network that supports person-to-person and machine-to-machine communication, enabling secure and private operation without a central authority.
|
||||
|
||||
1. Dapp to Wallet Communication
|
||||
2. NFT Marketplace
|
||||
3. Generalized Marketplace
|
||||
4. State Channels
|
||||
5. Game Mechanics Communication
|
||||
6. Layer 2 Coordination (Open Market, Spam Protected Mempool)
|
||||
7. Signature Exchange for Multi-Signature Wallets
|
||||
8. Chat Messenger: Status Communities
|
||||
The following is a list of some of the use cases that have been considered and their current status.
|
||||
|
||||
### Chat Messenger
|
||||
|
||||
Waku can be used as the communication layer when building a private, decentralized, and censorship-resistant messenger.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [Status Web](https://github.com/status-im/status-web)
|
||||
|
||||
### Polls
|
||||
|
||||
With Waku, you can create, answer, and view censorship-resistant polls.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [Waku Connect Poll SDK](https://github.com/status-im/wakuconnect-vote-poll-sdk)
|
||||
|
||||
### NFT Marketplace
|
||||
|
||||
Waku can be used to take NFT bids and offers off-chain, enabling gas savings. Additionally, it allows for adding a social media layer, enabling NFT owners to like, comment, and perform other social actions.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [SmolPuddle Marketplace](https://github.com/Agusx1211/smolpuddle-web)
|
||||
|
||||
### State Channels
|
||||
|
||||
Waku can enable two parties to set up and maintain a state channel.
|
||||
|
||||
### Voting and Proposals
|
||||
|
||||
To save on gas fees, votes for proposals submitted on the blockchain can be exchanged over Waku. These votes can then be aggregated and submitted to the blockchain to commit the result.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [Waku Connect Poll SDK](https://github.com/status-im/wakuconnect-vote-poll-sdk)
|
||||
|
||||
### Signature Exchange for Multi-Signature Wallets
|
||||
|
||||
Waku can enable multiple owners of a given multi-signature wallet to exchange signatures in a decentralized, private, and censorship-resistant manner, allowing for the approval of transactions.
|
||||
|
||||
### Game Mechanics Communication
|
||||
|
||||
Waku can be used as the communication layer for a peer-to-peer, decentralized game, eliminating the need for a centralized infrastructure for gameplay communications.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [Super Card Game](https://github.com/fjij/ethonline-2021)
|
||||
|
||||
### dApp to Wallet Communication
|
||||
|
||||
dApp operators can use communication between a user's wallet and their dApp to notify users (e.g., governance token holders can be notified to vote on a proposal) or to request transaction signatures from the wallet.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [WalletConnect 2.0](https://walletconnect.com/)
|
||||
* [HashPack](https://www.hashpack.app/hashconnect)
|
||||
|
||||
### Layer 2 Coordination (Open Market, Spam Protected Mempool)
|
||||
|
||||
Waku can broadcast and aggregate layer 2 transactions, potentially enhancing privacy, anonymity, and resilience.
|
||||
|
||||
### Generalized Marketplace
|
||||
|
||||
Waku can enable users to offer, bid, accept, and trade goods and services, making it possible to create ride-sharing or trading apps.
|
||||
|
||||
#### Demos
|
||||
|
||||
* [Waku-Uber](https://github.com/TheBojda/waku-uber)
|
||||
|
||||
### Social Media Platform
|
||||
|
||||
While chat messengers are a type of social media that can be decentralized and made censorship-resistant through Waku, other forms of social media, such as news feeds, blog posts, and audio or video sharing, can also benefit from using Waku.
|
||||
|
|
@ -3,7 +3,7 @@ title: What is Waku?
|
|||
slug: /
|
||||
---
|
||||
|
||||
Waku is a family of peer-to-peer protocols that provide **secure and private communication** in a decentralized environment. It is designed to operate in **resource-limited environments**, making it suitable for various decentralized applications (dApps).
|
||||
Waku is a family of peer-to-peer protocols that offer **secure and private communication** in a decentralized environment, making it suitable for various decentralized applications (dApps). It is designed to operate in **resource-limited environments** but can also be used as a node or desktop application.
|
||||
|
||||
Waku protocols ensure that users communication remains **censorship-resistant and privacy-preserving**, giving them complete control over their data. By incorporating Waku into your dApp, you can add decentralized communication features to your application **without compromising security or privacy**.
|
||||
|
||||
|
|
@ -13,7 +13,7 @@ The Waku family of protocols is designed for diverse applications due to their p
|
|||
|
||||
### Generalized Messaging
|
||||
|
||||
Many applications require some form of messaging protocol to facilitate communication between different subsystems or nodes. Waku is flexible and can be used for human-to-human and machine-to-machine messaging scenarios.
|
||||
Waku aims to solve the problem of ephemeral messaging between subsystems and nodes through a flexible, secure, and private protocol. It supports human-to-human and machine-to-machine messaging scenarios but is not designed for data storage.
|
||||
|
||||
### Peer-to-Peer
|
||||
|
||||
|
|
@ -43,6 +43,8 @@ Waku nodes are adaptive and can be customized based on the application's require
|
|||
- Providing resources to the network vs. consuming resources.
|
||||
- Stronger guarantees for spam protection vs. economic registration cost.
|
||||
|
||||
These options are part of the [anonymity trilemma](https://eprint.iacr.org/2017/954.pdf), which Waku addresses through its adjustable protocol.
|
||||
|
||||
## How Does Waku Work?
|
||||
|
||||
The Waku Relay protocol is the foundation of the Waku Network, which employs a `pubsub` architecture built on the `libp2p gossipsub` protocol. In addition to this, various other Waku protocols have been created to facilitate specific functionalities, including but not limited to:
|
||||
|
|
|
|||
|
|
@ -11,13 +11,13 @@ Waku is intended to empower individuals by returning control of communication to
|
|||
- It is not confined to a particular blockchain.
|
||||
- It is modular, adaptable, and can cater to various use cases.
|
||||
- It allows developers to decentralize communication in their dApps or move actions off-chain while maintaining decentralization.
|
||||
- It can run on various platforms, including mobile devices, cloud environments, web browsers, native desktop apps, or even dapp nodes!
|
||||
- It can run on various platforms, including mobile devices, cloud environments, web browsers, native desktop apps, or even a [Dappnode](https://dappnode.com/)!
|
||||
|
||||
## Whisper vs. Waku: Why Waku Wins
|
||||
## Whisper vs. Waku: Why Waku is Necessary
|
||||
|
||||
| | Whisper | Waku |
|
||||
| - | - | - |
|
||||
| **Scalability** | Whisper doesn't scale very well, specifically when it comes to bandwidth usage on mobile devices. | Uses sharding to partition the network into separate gossipsub networks, while maintaining a shared discovery network for peer location. |
|
||||
| **Scalability** | Whisper doesn't scale very well, specifically when it comes to bandwidth usage on mobile devices. | Uses gossipsub and content topics. |
|
||||
| **Spam Resistance** | Proof of work requires too much battery and compute power making it a poor mechanism for heterogeneous nodes. | Uses innovative p2p economic spam protection mechanism RLN Relay. |
|
||||
| **Incentivization Infrastructure** | There is no incentive to run a Whisper node. | Research in progress to design incentivization for node operators. |
|
||||
| **Formal Specification/Documentation** | Lack of formal and unambiguous specification. | The specs and docs are open-source and licensed under CC0, making them freely available for anyone to read, modify and improve without restrictions. |
|
||||
|
|
|
|||
|
|
@ -53,7 +53,7 @@ const config = {
|
|||
type: 'docSidebar',
|
||||
position: 'left',
|
||||
sidebarId: 'main',
|
||||
label: 'Overview',
|
||||
label: 'Getting Started',
|
||||
},
|
||||
{
|
||||
type: 'docSidebar',
|
||||
|
|
@ -65,7 +65,7 @@ const config = {
|
|||
},
|
||||
announcementBar: {
|
||||
content:
|
||||
"Waku is not production ready yet. Join our <a href='https://discord.gg/Nrac59MfSX'>Discord Community</a> to stay updated.",
|
||||
"While Waku still has progress to make, apps like <a href='/overview/who-is-using-waku'>XMTP and Railgun</a> have already implemented it in production. Join our <a href='https://discord.gg/Nrac59MfSX'>Discord Community</a> to stay updated on our progress.",
|
||||
backgroundColor: "#EBEDF0",
|
||||
textColor: "#1B1B1D",
|
||||
isCloseable: true,
|
||||
|
|
|
|||
Loading…
Reference in New Issue