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

Governance gated chains for bridging credits #1119

Closed
4 tasks
Tracked by #1310 ...
ryanchristo opened this issue May 20, 2022 · 0 comments · Fixed by #1462
Closed
4 tasks
Tracked by #1310 ...

Governance gated chains for bridging credits #1119

ryanchristo opened this issue May 20, 2022 · 0 comments · Fixed by #1462
Assignees
Labels
Scope: x/ecocredit Issues that update the x/ecocredit module

Comments

@ryanchristo
Copy link
Member

Summary

In #1101, we introduced a validation check for target in MsgBridge currently restricted to "polygon". In the future, allowed chains should be managed by governance, same as we do with allowed denoms and allowed credit class creators.

Problem Definition

In the future, we plan to support bridging assets to and from multiple chains. We need to validate the source and target chain to prevent any undesired behavior and the allowed chains should ultimately be decided through a governance process.

Proposal

  • Add allowed chains to state using an ORM table
  • Add transaction messages for adding and removing an allowed chain
  • Add events for adding and removing an allowed chain
  • Add a query for querying allowed chains
  • Add corresponding CLI commands

For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Scope: x/ecocredit Issues that update the x/ecocredit module
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants