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

Allow metadata to be updated for open batches #1582

Closed
4 tasks
Tracked by #972
ryanchristo opened this issue Oct 31, 2022 · 1 comment · Fixed by #1623
Closed
4 tasks
Tracked by #972

Allow metadata to be updated for open batches #1582

ryanchristo opened this issue Oct 31, 2022 · 1 comment · Fixed by #1623
Assignees
Labels
Type: Feature New feature or request

Comments

@ryanchristo
Copy link
Member

ryanchristo commented Oct 31, 2022

Summary

When bridging credits from Polygon to Regen, we check the project reference id and the batch contract address to determine whether a new project or a new credit batch needs to be created. The metadata for projects and vintages in the Toucan contracts are expected to change (adding more information). When this occurs, the metadata fields will not be updated on Regen.

When project metadata is updated, the admin of the project will be able to manually update the project metadata field, but with credit batches, the metadata cannot be manually updated. Should we allow metadata to be updated for "open" credit batches?

Problem Definition

The metadata for credit batches bridged from Polygon to Regen is expected to change.

Proposal

Allow metadata to be updated for "open" credit batches (i.e. add MsgUpdateBatchMetadata).


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@ryanchristo ryanchristo added this to the v5.0 - Titicaca Upgrade milestone Oct 31, 2022
@ryanchristo ryanchristo mentioned this issue Nov 3, 2022
34 tasks
@ryanchristo
Copy link
Member Author

@clevinson @aaronc curious if you have any thoughts here and if we should include in v5.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Feature New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant