Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Roadmap(SeM): Protocol Incentivization #171

Closed
1 task
kaiserd opened this issue Jan 27, 2023 · 3 comments
Closed
1 task

Roadmap(SeM): Protocol Incentivization #171

kaiserd opened this issue Jan 27, 2023 · 3 comments
Assignees
Labels
track:protocol-incentivization Protocol Incentivization track (Secure Messaging), e.g. service credentials

Comments

@kaiserd
Copy link
Contributor

kaiserd commented Jan 27, 2023

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.)

@kaiserd kaiserd added the track:protocol-incentivization Protocol Incentivization track (Secure Messaging), e.g. service credentials label Jan 27, 2023
@kaiserd kaiserd self-assigned this Jan 27, 2023
@kaiserd kaiserd removed this from Vac Research Feb 1, 2023
@oskarth
Copy link
Contributor

oskarth commented Feb 2, 2023

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
Copy link

Relevant to the discussion: https://forum.vac.dev/t/waku-payment-models/166/3

I think platforms are likely to want to be the one to pay for the infra as they are extracted value from their users in some other form.

While "user paying" is also a viable model, I think we could almost see it as a "2nd" option.

@kaiserd
Copy link
Contributor Author

kaiserd commented Nov 23, 2023

Ownership of this issue has been moved to Waku: waku-org/pm#101

@kaiserd kaiserd closed this as completed Nov 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
track:protocol-incentivization Protocol Incentivization track (Secure Messaging), e.g. service credentials
Projects
Status: No status
Development

No branches or pull requests

3 participants