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

Implement v39 access list migration for markers to v40 #46

Closed
4 tasks done
iramiller opened this issue Feb 8, 2021 · 1 comment · Fixed by #97
Closed
4 tasks done

Implement v39 access list migration for markers to v40 #46

iramiller opened this issue Feb 8, 2021 · 1 comment · Fixed by #97
Assignees
Labels
marker Marker Module
Milestone

Comments

@iramiller
Copy link
Member

iramiller commented Feb 8, 2021

Summary

v39 marker export should be importable into v40. Currently the access list is not migrated see x/marker/legacy/v040/migrate.go#35 for details.

Problem Definition

Exports from a v39 chain should be importable into a v40 chain. Ensure that the access list is correctly transformed into a v40 genesis format including the accesslist. Check process with unit test coverage.

Note: testing should determine if markers that are imported using the account list in the auth module are correctly imported as well or if further work is required to move these accounts over. Verify the export from a v39 testchain imports into a v40 using the migration process.


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@jdfigure jdfigure added the marker Marker Module label Feb 17, 2021
@iramiller
Copy link
Member Author

See also #78 which will actually wire up the migration functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
marker Marker Module
Projects
Development

Successfully merging a pull request may close this issue.

2 participants