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

Epic: PoE module follow ups #53

Closed
alpe opened this issue Jun 10, 2021 · 4 comments
Closed

Epic: PoE module follow ups #53

alpe opened this issue Jun 10, 2021 · 4 comments
Labels
PoE Proof of Engagement

Comments

@alpe
Copy link
Contributor

alpe commented Jun 10, 2021

Incomplete

* Genesis elements to customize the PoE contract instantiation config (fix in code)
* Queries (CLI/GRPC) that bridge to the PoE contracts

Missing

Puzzle

  • How do we edit/set the Engagement group in genesis?
    * Do we need an admin for the mixer contract?
@alpe alpe added the PoE Proof of Engagement label Aug 3, 2021
@ethanfrey
Copy link
Contributor

Is this done?

@alpe
Copy link
Contributor Author

alpe commented Dec 6, 2021

We don't have support for the hard fork scenario via

  • Export genesis via state dump
  • Start chain from genesis state dump (+ validation)

@ethanfrey
Copy link
Contributor

This #49 and #50 are all about dump-state-and-restart scenario.

This would be good to have before mainnet, although I would prefer x/upgrade generally (and we could x/upgrade to a new version that supports this if needed).

Could you make one issue that explains all requirements for dump-state-and-restart and close all these (and link them to the new issue). These are old, and a bit lost in the pile.

@alpe
Copy link
Contributor Author

alpe commented Apr 5, 2022

Closing this in favour of #49 + #50 for the remaining open tasks

@alpe alpe closed this as completed Apr 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
PoE Proof of Engagement
Projects
None yet
Development

No branches or pull requests

2 participants