Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

12/WAKU2-FILTER: Failed Nodes and the filter protocol #253

Closed
decanus opened this issue Nov 18, 2020 · 2 comments
Closed

12/WAKU2-FILTER: Failed Nodes and the filter protocol #253

decanus opened this issue Nov 18, 2020 · 2 comments

Comments

@decanus
Copy link
Contributor

decanus commented Nov 18, 2020

Problem

Currently when a fullnode fails, a light node is not aware of this. This means that it may no longer receive messages from the filter protocol and believe that it is just not receiving messages.

Possible Solutions

There are currently 2 scenarios that I see working, we may even need to make these both work together assuming that we think certain fullnodes could be byzantine.

  1. A lightnode should ping a fullnode every epoch to ensure that it still stores the filter they had passed initially, this could be ensured by making the fullnode return the full set of filters from the sending subscriber.

  2. Additionally we could spec peristence for fullnode filter protocols, this would ensure that fullnodes save the filters in a database meaning if they crash and restart they could read these filters from the database.

@oskarth
Copy link
Contributor

oskarth commented Feb 2, 2021

@jm-clius if you feel differently about this feel free to activate it again, otherwise seems unlikely we'll get to in Feb

@oskarth oskarth changed the title Failed Nodes and the filter protocol 12/WAKU2-FILTER: Failed Nodes and the filter protocol Mar 31, 2021
@jm-clius jm-clius removed their assignment Jul 19, 2021
@jimstir
Copy link
Contributor

jimstir commented Jun 13, 2024

Closing, seems like discussion is complete.

@jimstir jimstir closed this as completed Jun 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants