2.3 KiB
2.3 KiB
| title | hide_table_of_contents | sidebar_label |
|---|---|---|
| Waku FAQ | true | Frequently Asked Questions |
import { AccordionItem } from '@site/src/components/mdx'
Check out the Getting Started guide to explore our numerous SDKs and learn how to run a Waku node. No, sending and receiving messages on Waku involves no gas fee. Waku uses libp2p noise encryption for node-to-node connections. However, no default encryption method is applied to the data sent over the network. This design choice enhances Waku's encryption flexibility, encouraging developers to use custom protocols or Waku message payload encryption methods freely. Waku's Store protocol is designed to temporarily store messages within the network. However, Waku does not guarantee the message's availability and recommends using Codex for long-term storage. No, Waku is flexible and imposes no specific rules on identifiers. Waku focuses on short, ephemeral, real-time time messages, while IPFS focuses on large, long-term data storage. Although there's an overlap between the two technologies, Waku does not currently support large data for privacy reasons. Rate Limiting Nullifier is a zero-knowledge (ZK) protocol enabling spam protection in a decentralized network while preserving privacy. Each message must be accompanied by a ZK proof, which Relay nodes verify to ensure the publishers do not send more messages than they are allowed. The ZK proof does not leak any private information about message publishers - it only proves they are members of a set of users allowed to publish a certain number of messages per given time frame.