25 KiB
2021-03-31 v0.9
Release highlights:
- Support for Peer Exchange (PX) when a peer prunes a
11/WAKU2-RELAY
mesh due to oversubscription. This can significantly increase mesh stability. - Improved start-up times through managing the size of the underlying persistent message storage.
- New websocket connections are no longer blocked due to parsing failures in other connections.
The full list of changes is below.
Features
- Support for bootstrapping
33/WAKU-DISCV5
via DNS discovery - Support for GossipSub Peer Exchange
- Support for TOML config files via
--config-file=<path/to/config.toml>
Changes
- Waku v1 <> v2 bridge now supports DNS
multiaddrs
- Waku v1 <> v2 bridge now validates content topics before attempting to bridge a message from Waku v2 to Waku v1
- Persistent message storage now auto deletes messages once over specified
--store-capacity
. This can significantly improve node start-up times. - Renamed Waku v1 <> v2 bridge
make
target and binary towakubridge
- Increased
store
logging to assist with debugging - Increased
rln-relay
logging to assist with debugging - Message metrics no longer include the content topic as a dimension to keep Prometheus metric cardinality under control
- Waku v2
toy-chat
application now sets the sender timestamp when creating messages - The type of the
proof
field of theWakuMessage
is changed toRateLimitProof
- Added method to the JSON-RPC API that returns the git tag and commit hash of the binary
- The node's ENR is now included in the JSON-RPC API response when requesting node info
Fixes
- Fixed incorrect conversion of seconds to nanosecond timestamps
- Fixed store queries blocking due to failure in resource clean up
- Fixed underlying issue where new websocket connections are blocked due to parsing failures in other connections
- Fixed failure to log the ENR necessary for a discv5 connection to the node
Docs
- Added RAM requirements to
wakunode2
build instructions - Added tutorial on communicating with waku2 test fleets via the chat2
toy-chat
application in spam-protected mode using17/WAKU-RLN-RELAY
. - Added a section on bug reporting to
wakunode2
README - Fixed broken links in the JSON-RPC API Tutorial
This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
11/WAKU2-RELAY |
stable |
/vac/waku/relay/2.0.0 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta4 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-03-03 v0.8
Release highlights:
- Working demonstration and integration of
17/WAKU-RLN-RELAY
in the Waku v2toy-chat
application - Beta support for ambient peer discovery using a version of Discovery v5
- A fix for the issue that caused a
store
node to run out of memory after serving a number of historical queries - Ability to configure a
dns4
domain name for a node and resolve other dns-basedmultiaddrs
The full list of changes is below.
Features
17/WAKU-RLN-RELAY
implementation now supports spam-protection for a specific combination ofpubsubTopic
andcontentTopic
(available under therln
compiler flag).17/WAKU-RLN-RELAY
integrated into chat2toy-chat
(available under therln
compiler flag)- Added support for resolving dns-based
multiaddrs
- A Waku v2 node can now be configured with a domain name and
dns4
multiaddr
- Support for ambient peer discovery using
33/WAKU-DISCV5
Changes
- Metrics: now monitoring content topics and the sources of new connections
- Metrics: improved default fleet monitoring dashboard
- Introduced a
Timestamp
type (currently an alias for int64). - All timestamps changed to nanosecond resolution.
timestamp
field number in WakuMessage object changed from4
to10
13/WAKU2-STORE
identifier updated to/vac/waku/store/2.0.0-beta4
toy-chat
application now uses DNS discovery to connect to existing fleets
Fixes
- Fixed underlying bug that caused occasional failures when reading the certificate for secure websockets
- Fixed
store
memory usage issues when responding to history queries
Docs
- Documented use of domain certificates for secure websockets
- Documented how to configure a
dns4
domain name for a node - Clarified use of DNS discovery and provided current URLs for discoverable fleet nodes
- Added tutorial on using
17/WAKU-RLN-RELAY
with the chat2toy-chat
application - Added tutorial on how to configure and a use a
15/WAKU-BRIDGE
This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
11/WAKU2-RELAY |
stable |
/vac/waku/relay/2.0.0 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta4 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-01-19 v0.7
Release highlights:
- Support for secure websockets.
- Ability to remove unreachable clients in a
filter
node. - Several fixes to improve
store
performance and decrease query times. Query time for large stores decreased from longer than 8 min to under 100 ms. - Fix for a long-standing bug that prevented proper database migration in some deployed Docker containers.
The full list of changes is below.
Features
- Support for secure websocket transport
Changes
- Filter nodes can now remove unreachable clients
- The WakuInfo
listenStr
is deprecated and replaced with a sequence oflistenAddresses
to accommodate multiple transports - Removed cached
peerInfo
on local node. Rely on underlying libp2p switch instead - Metrics: added counters for protocol messages
- Waku v2 node discovery now supports
31/WAKU2-ENR
- resuming the history via
resume
now takes the answers of all peers inpeerList
into consideration and consolidates them into one deduplicated list
Fixes
- Fixed database migration failure in the Docker image
- All
HistoryResponse
messages are now auto-paginated to a maximum of 100 messages per response - Increased maximum length for reading from a libp2p input stream to allow largest possible protocol messages, including
HistoryResponse
messages at max size - Significantly improved
store
node query performance - Implemented a GossipSub
MessageIdProvider
for11/WAKU2-RELAY
messages instead of relying on the unstable default - Receiver timestamps for message indexing in the
store
now have consistent millisecond resolution
This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
17/WAKU-RLN-RELAY |
raw |
/vac/waku/waku-rln-relay/2.0.0-alpha1 |
11/WAKU2-RELAY |
stable |
/vac/waku/relay/2.0.0 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta3 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-11-05 v0.6
Some useful features and fixes in this release, include:
- two methods for Waku v2 node discovery
- support for unsecure websockets, which paves the way for native browser usage
- a fix for
nim-waku
store nodes running out of memory due to store size: the number of stored messages can now easily be configured - a fix for densely connected nodes refusing new connections: the maximum number of allowed connections can now easily be configured
- support for larger message sizes (up from 64kb to 1Mb per message)
The full list of changes is below.
Features
- Waku v2 node discovery via DNS following EIP-1459
- Waku v2 node discovery via Node Discovery v5
Changes
- Pagination of historical queries are now simplified
- GossipSub prune backoff period is now the recommended 1 minute
- Bridge now uses content topic format according to 23/WAKU2-TOPICS
- Better internal differentiation between local and remote peer info
- Maximum number of libp2p connections is now configurable
udp-port
CLI option has been removed for binaries where it's not used- Waku v2 now supports unsecure WebSockets
- Waku v2 now supports larger message sizes of up to 1 Mb by default
- Further experimental development of RLN for spam protection.
These changes are disabled by default under a compiler flag. Changes include:
- Per-message rate limit proof defined
- RLN proof generation and verification integrated into Waku v2
- RLN tree depth changed from 32 to 20
- Support added for static membership group formation
Docs
- Added contributor guidelines on Waku v2 fleet monitoring and management
- Added basic tutorial on using Waku v2 DNS-based discovery
Fixes
- Bridge between
toy-chat
and matterbridge now shows correct announced addresses - Bridge no longer re-encodes already encoded payloads when publishing to V1
- Bridge now populates WakuMessage timestamps when publishing to V2
- Store now has a configurable maximum number of stored messages
- Network simulations for Waku v1 and Waku v2 are runnable again
This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
17/WAKU-RLN |
raw |
/vac/waku/waku-rln-relay/2.0.0-alpha1 |
11/WAKU2-RELAY |
stable |
/vac/waku/relay/2.0.0 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta3 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-07-26 v0.5.1
This patch release contains the following fix:
- Support for multiple protocol IDs when reconnecting to previously connected peers:
A bug in
v0.5
caused clients using persistent peer storage to only support the mounted protocol ID.
This is a patch release that is fully backwards-compatible with release v0.5
.
It supports the same libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
17/WAKU-RLN |
raw |
/vac/waku/waku-rln-relay/2.0.0-alpha1 |
11/WAKU2-RELAY |
stable |
/vac/waku/relay/2.0.0 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta3 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-07-23 v0.5
This release contains the following:
Features
- Support for keep-alives using libp2p ping protocol.
- DB migration for the message and peer stores.
- Support for multiple protocol IDs. Mounted protocols now match versions of the same protocol that adds a postfix to the stable protocol ID.
Changes
- Bridge topics are now configurable.
- The
resume
Nim API now eliminates duplicates messages before storing them. - The
resume
Nim API now fetches historical messages in page sequence. - Added support for stable version of
relay
protocol, with protocol ID/vac/waku/relay/2.0.0
. - Added optional
timestamp
toWakuRelayMessage
. - Removed
PCRE
as a prerequisite for building Waku v1 and Waku v2. - Improved
swap
metrics.
General refactoring
- Refactored modules according to Nim best practices.
- Simplified the way protocols get notified of new messages.
- Refactored
wakunode2
setup into 6 distinct phases with improved logging and error handling. - Moved
Whisper
types and protocol from thenim-eth
module tonim-waku
.
Docs
- Added database migration tutorial.
- Added tutorial to setup
websockify
.
Schema
- Updated the
Message
table of the persistent message store:- Added
senderTimestamp
column. - Renamed the
timestamp
column toreceiverTimestamp
and changes its type toREAL
.
- Added
API
- Added optional
timestamp
toWakuRelayMessage
on JSON-RPC API.
Fixes
- Conversion between topics for the Waku v1 <-> v2 bridge now follows the RFC recommendation.
- Fixed field order of
HistoryResponse
protobuf message: the field numbers of theHistoryResponse
are shifted up by one to match up the 13/WAKU2-STORE specs.
This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
17/WAKU-RLN |
raw |
/vac/waku/waku-rln-relay/2.0.0-alpha1 |
11/WAKU2-RELAY |
stable |
/vac/waku/relay/2.0.0 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta3 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-06-03 v0.4
This release contains the following:
Features
- Initial
toy-chat
implementation
Changes
- The toy-chat application can now perform
lightpush
and request content-filtered messages from remote peers. - The toy-chat application now uses default content topic
/toy-chat/2/huilong/proto
- Improve
toy-chat
briding to matterbridge - Improve
swap
logging and enable soft mode by default - Content topics are no longer in a redundant nested structure
- Improve error handling
API
- JSON-RPC Store API: Added an optional time-based query to filter historical messages.
- Nim API: Added
resume
method.
Fixes
- Connections between nodes no longer become unstable due to keep-alive errors if mesh grows large
- Re-enable
lightpush
tests and fix Windows CI failure
The Waku v2 suite of protocols are still in a raw/draft state. This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
17/WAKU-RLN |
raw |
/vac/waku/waku-rln-relay/2.0.0-alpha1 |
11/WAKU2-RELAY |
draft |
/vac/waku/relay/2.0.0-beta2 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta3 |
18/WAKU2-SWAP |
draft |
/vac/waku/swap/2.0.0-beta1 |
19/WAKU2-LIGHTPUSH |
draft |
/vac/waku/lightpush/2.0.0-beta1 |
The Waku v1 implementation is stable but not under active development.
2021-05-11 v0.3
This release contains the following:
Features
- Start of
RLN relay
implementation - Start of
swap
implementation - Start of fault-tolerant
store
implementation - Initial
bridge
implementation between Waku v1 and v2 protocols - Initial
lightpush
implementation - A peer manager for
relay
,filter
,store
andswap
peers - Persistent storage for peers: A node with this feature enabled will now attempt to reconnect to
relay
peers after a restart. It will respect the gossipsub PRUNE backoff period before attempting to do so. --persist-peers
CLI option to persist peers in local storage--persist-messages
CLI option to store historical messages locally--keep-alive
CLI option to maintain a stable connection torelay
peers on idle topics- A CLI chat application (
chat2
) over Waku v2 with bridging to matterbridge
Changes
- Enable
swap
protocol by default and improve logging
General refactoring
- Split out
waku_types
types into the right place; createutils
folder. - Change type of
contentTopic
inContentFilter
tostring
. - Replace sequence of
contentTopics
inContentFilter
with a singlecontentTopic
. - Add
timestamp
field toWakuMessage
. - Ensure CLI config parameters use a consistent naming scheme. Summary of changes here.
Docs
Several clarifications and additions aimed at contributors, including
- information on how to query Status test fleet for node addresses,
- how to view logs, and
- how to update submodules.
Schema
- Add
Message
table to the persistent message store. This table replaces the oldmessages
table. It has two additional columns, namelypubsubTopic
, andversion
.
- Add
Peer
table for persistent peer storage.
API
- JSON-RPC Admin API: Added a
post
method to connect to peers on an ad-hoc basis. - Nim API: PubSub topic
subscribe
andunsubscribe
no longer returns a future (removedasync
designation). HistoryQuery
: AddedpubsubTopic
field. Message history can now be filtered and queried based on thepubsubTopic
.HistoryQuery
: Added support for querying a time window by specifying start and end times.
Fixes
- Running nodes can now be shut down gracefully
- Content filtering now works on any PubSub topic and not just the
waku
default. - Nodes can now mount protocols without supporting
relay
as a capability
The Waku v2 suite of protocols are still in a raw/draft state. This release supports the following libp2p protocols:
Protocol | Spec status | Protocol id |
---|---|---|
17/WAKU-RLN |
raw |
/vac/waku/waku-rln-relay/2.0.0-alpha1 |
18/WAKU2-SWAP |
raw |
/vac/waku/swap/2.0.0-alpha1 |
19/WAKU2-LIGHTPUSH |
raw |
/vac/waku/lightpush/2.0.0-alpha1 |
11/WAKU2-RELAY |
draft |
/vac/waku/relay/2.0.0-beta2 |
12/WAKU2-FILTER |
draft |
/vac/waku/filter/2.0.0-beta1 |
13/WAKU2-STORE |
draft |
/vac/waku/store/2.0.0-beta3 |
The Waku v1 implementation is stable but not under active development.
2021-01-05 v0.2
This release contains the following changes:
- Calls to
publish
a message onwakunode2
nowawait
instead ofdiscard
dispatchedWakuRelay
procedures. StrictNoSign
enabled.- Add JSON-RPC API for external access to
wakunode2
functionality:- Admin API retrieves information about peers registered on the
wakunode2
. - Debug API exposes debug information about a
wakunode2
. - Filter API saves bandwidth by allowing light nodes to filter for specific content.
- Private API enables symmetric or asymmetric cryptography to encrypt/decrypt message payloads.
- Relay API allows basic pub/sub functionality.
- Store API retrieves historical messages.
- Admin API retrieves information about peers registered on the
- Add tutorial on how to use JSON-RPC API.
- Refactor: Move
waku_filter
protocol into its own module.
The Waku v2 implementation, and most protocols it consist of, are still in a draft/beta state. The Waku v1 implementation is stable but not under active development.
2020-11-30 v0.1
Initial beta release.
This release contains:
- A Nim implementation of the Waku v1 protocol.
- A Nim implementation of the Waku v2 protocol.
- CLI applications
wakunode
andwakunode2
that allows you to run a Waku v1 or v2 node. - Examples of Waku v1 and v2 usage.
- Various tests of above.
Currenty the Waku v2 implementation, and most protocols it consist of, are in a draft/beta state. The Waku v1 implementation is stable but not under active development.
Feedback welcome!