-
Run:
```
#!/bin/bash
printf "\nAssuming you already have a docker network called waku\n"
# if not something like this should create it: docker network create --driver bridge --subnet 172.18.0.0/…
-
### Problem
When the payload is >= 300 kb the light push fails with some strange messages
1.
Payload ~= 300 KB
```
payload=$(head -c $((1024 * 225)) /dev/urandom | base64 -w 0) && \
echo "{\"…
-
# Bug Report
## Description
- Community links have a random tag encoded
## Steps to reproduce
- Right-click a Community in sidebar > Invite People > copy link
- Visit the link in remote b…
-
### Background
The DST team needs to keep track of the messages and this is done through log analysis and `msg_hash` track.
Given that DST spawns thousands of nodes we need to bring them docker imag…
-
### Problem
This is a simplification and restatement of https://github.com/waku-org/nwaku/issues/1961
The goal of this issue is to create a proof of concept branch in nwaku, with the following n…
-
After a first successful cycle of attact mode on the game, the loading screens will start to incorrectly being rendered, by double stripes.
You could see the issue by leaving the game alone running…
-
**To Reproduce**
Steps to reproduce the behavior:
1. Send a light push request with an incorrect payload or contentTopic (could be an empty string or with those fields missing)
Actual behaviour: …
-
This is a **change request**
## Problem
When setting up light node, users can specify both `pubsubTopics` and `shardInfo` which seems to result in unwanted behaviour
## Proposed Solutions
…
-
During hackathon I found myself drawing diagrams how Waku network works and how a message gets propagated in there.
I think we should include some schemes here https://docs.waku.org/#peer-to-peer
-
Here are a list of graphs that would help explain Waku's architecture:
- [x] (1) Message flow architecture diagram:
- Shows Waku Relay and pubsub topic message routing
- Shows Filter/Light Push…
D4nte updated
3 months ago