oskarth
commented
1 year ago One alternative simplification (because we've been very delayed with this work, for a myriad of reasons) is to really KISS and start of with public transfers. E.g. just using normal ETH/ERC20 transfer from consumer to provider. Possibly with some basic form of staking mechanism.
This would allow us to get the ball rolling and start to work on all the other integration/testing needed here and could be useful for Waku Product sooner rather than later.
Specifically, this would not be privacy-preserving. In the spec this would mention this, and encourage avoiding e.g. address re-use.
In parallel / separately, we can deal with making it privacy-preserving (this could even be enabled through something like ZK-VM effort, or leveraging existing private transfer solutions).
cc @fryorcraken for Waku Product POV, @s1fr0 re previous conversations and @rymnc as a FYI
(Obviously this is lower priority than scaling work, but thought I'd mention it here as it might not be an obvious possibility to everyone).
fryorcraken
kaiserd
Background / Motivation
The protocol incentivization track covers research on incentives for nodes to offer specific services and/or resources.
Part of this is research on services credentials. The goal is allowing service consumers to purchase service credentials (or tokens) that can be used to obtain services from Waku nodes. Service providers will be able to claim funds associated with received credentials.
Issues
(This roadmap is WIP. Items on the roadmap, especially ones farther in the future, might change.)