Skip to content

Latest commit

 

History

History
26 lines (19 loc) · 1.29 KB

ovip-0016.md

File metadata and controls

26 lines (19 loc) · 1.29 KB
OVIP: 16
Title: Waku as Message Layer
Author: Felix Laufenberg <[email protected]>
Discussions-To: https://community.openvasp.org/#narrow/stream/21-protocol-.2F.20ovip
Status: Accepted
Replaces: OVIP-0009
Type: Standard
Created: 2020-09-18

Abstract

This Ovip proposes to replace the usage of the obsolete Whisper messaging protocol for the OpenVASP messaging layer with the Waku messaging protocol implemented by Status.

Specification

The Waku network client API is backwards compatible with the Whisper client API. Thus, changing the messaging Layer is as easy as connecting to a url which is pointing to a Waku client.

Motivation

Whisper has officially been deprecated and is not maintained any further: ethereum/go-ethereum#21487. The Status team has forked the project and is maintaining and developing the network as Waku. We expect higher stability, ongoing development and a technically brigher future by switching messaging protocols.

Backwards Compatibility

As the Whisper and Waku networks are not connected per default, this is to be considered a backwards incompatible change. In terms of development, implementing this ovip is as easy as changing the Whisper url config entry to a Waku client url.