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

ProtoRev adjustments [Proposal 709/710] #7320

Closed
JohnnyWyles opened this issue Jan 15, 2024 · 0 comments · Fixed by #7509
Closed

ProtoRev adjustments [Proposal 709/710] #7320

JohnnyWyles opened this issue Jan 15, 2024 · 0 comments · Fixed by #7509

Comments

@JohnnyWyles
Copy link
Collaborator

Background

This issue asks for the implementation of Proposals 709and 710.

These allocate ProtoRev by:

  • Sending any OSMO revenue to the null address
  • Sending any non-OSMO revenue to the community pool.

Suggested Design

This would need three main changes

Revenue deposit location

The locations at which the assets are deposited once obtained, after Skip's share of revenue is taken.

Existing assets move

Existing assets in the module account would need to be moved to the above locations, ensuring that none are left behind. This can take place as part of the initial software upgrade, a routine sweep at epoch, or a further spend proposal.

Exclusion of null address from supply to form the burn mechanic

Detailed in #5606

Acceptance Criteria

No assets remain in the protorev module account.
Community pool accumulates all non-OSMO revenue from Protorev
Null address accumulates all OSMO revenue from Protorev

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant