status-go/waku/v1
Andrea Maria Piana 56c0142f16 Honor FullNode config in waku
previously FullNode would only result in setting a bloom filter to full.

This behavior caused issues as you effectively cannot install a filter
on a FullNode, as it would advertise the new topic/bloom filter and stop
receiving all the messages.

This caused an issue when running push notifications servers together
with mailservers, also the behavior is a bit counter-intuitive as I
would expect the FullNode config to be honored no matter of what filters
are installed.
2020-08-26 14:11:13 +02:00
..
README.md Implement waku/1 2020-05-01 10:14:04 +02:00
const.go Implement waku/1 2020-05-01 10:14:04 +02:00
init.go Create waku/1 namespace 2020-05-01 10:14:04 +02:00
message_response.go Minor Waku version subpackage message.go tidy (#1964) 2020-05-07 15:45:25 +01:00
message_response_test.go Minor Waku version subpackage message.go tidy (#1964) 2020-05-07 15:45:25 +01:00
peer.go Honor FullNode config in waku 2020-08-26 14:11:13 +02:00
peer_test.go Minor Waku version subpackage message.go tidy (#1964) 2020-05-07 15:45:25 +01:00
status_options.go Move bytes rate limits to a different rlp key 2020-06-15 19:46:23 +02:00
status_options_test.go Move bytes rate limits to a different rlp key 2020-06-15 19:46:23 +02:00

README.md

waku/1

This namespace implements waku 1.0 as described in https://github.com/vacp2p/specs/blob/master/specs/waku/waku-1.md