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

Certain bitasset options should still be updatable after globally settled #2282

Closed
1 of 17 tasks
abitmore opened this issue Oct 5, 2020 · 1 comment · Fixed by #2506
Closed
1 of 17 tasks

Certain bitasset options should still be updatable after globally settled #2282

abitmore opened this issue Oct 5, 2020 · 1 comment · Fixed by #2506

Comments

@abitmore
Copy link
Member

abitmore commented Oct 5, 2020

User Story

As an MPA owner I'd like to be able to update the bitasset options when my MPA is globally settled.
IMHO all options except the short_backing_asset should be updatable.

Note: if implemented, this comment should be removed:

* No more asset updates may be issued.

Impacts
Describe which portion(s) of BitShares Core may be impacted by your request. Please tick at least one box.

  • API (the application programming interface)
  • Build (the build process or something prior to compiled code)
  • CLI (the command line wallet)
  • Deployment (the deployment process after building such as Docker, Travis, etc.)
  • DEX (the Decentralized EXchange, market engine, etc.)
  • P2P (the peer-to-peer network for transaction/block propagation)
  • Performance (system or user efficiency, etc.)
  • Protocol (the blockchain logic, consensus, validation, etc.)
  • Security (the security of system or user data, etc.)
  • UX (the User Experience)
  • Other (please add below)

Additional Context (optional)
Add any other context about your request here.

CORE TEAM TASK LIST

  • Evaluate / Prioritize Feature Request
  • Refine User Stories / Requirements
  • Define Test Cases
  • Design / Develop Solution
  • Perform QA/Testing
  • Update Documentation
@abitmore abitmore added this to To Do in Protocol Upgrade Release (6.0.0) via automation Oct 5, 2020
@abitmore abitmore self-assigned this Oct 7, 2021
@abitmore abitmore moved this from To Do to In Development in Protocol Upgrade Release (6.0.0) Oct 7, 2021
@abitmore abitmore linked a pull request Oct 8, 2021 that will close this issue
@abitmore abitmore moved this from In Development to In Testing in Protocol Upgrade Release (6.0.0) Oct 8, 2021
@abitmore
Copy link
Member Author

abitmore commented Oct 8, 2021

Done via #2506.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
No open projects
Development

Successfully merging a pull request may close this issue.

1 participant