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.

Sign up for GitHub

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

Jump to bottom

Total backing asset for Backed Assets #1781

Closed
2 of 17 tasks
startailcoon opened this issue May 28, 2019 · 6 comments
Closed
2 of 17 tasks

Total backing asset for Backed Assets #1781

startailcoon opened this issue May 28, 2019 · 6 comments
Assignees
@pmconrad
Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2d Developing Status indicating currently designing and developing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 API Impact flag identifying the application programing interface (API) 6 Plugin Impact flag identifying at least one plugin 9a Tiny Effort estimation indicating TBD
Milestone
3.3.0 - Feature R...

Comments

@startailcoon
Copy link

A backed asset, like bitUSD, is backed by another asset, in this case BTS.
At the moment it's not an easy task to calculate the amount of total backing asset for the backed asset.

The UI requests a calculation of this for easy usage without having to do all the calculations manually.

See issue bitshares/bitshares-ui#2715 for more details.

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)

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 the Future Feature Release milestone May 28, 2019
@abitmore
Copy link
Member

#1089 is related.

@abitmore
Copy link
Member

My idea for this feature is to add a secondary index to call_order_index in a plugin, just like grouped_orders plugin.

Pros:

  • it won't affect performance of nodes which doesn't enable the plugin

Cons:

  • change of data in secondary index doesn't trigger notifications with current subscription-notification mechanism.

@pmconrad
Copy link
Contributor

#1089 is related.

IMO it's more than related, it's a duplicate. Can close either this or the other one. Or did I miss something?

@abitmore
Copy link
Member

#1089 and this issue are slightly different. This issue is for debt asset info page, #1089 is for collateral asset info page.

@pmconrad pmconrad self-assigned this Jun 27, 2019
@pmconrad pmconrad added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2d Developing Status indicating currently designing and developing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 API Impact flag identifying the application programing interface (API) 6 Plugin Impact flag identifying at least one plugin 9a Tiny Effort estimation indicating TBD labels Jun 27, 2019
pmconrad added a commit to pmconrad/bitshares-core that referenced this issue Jun 29, 2019
@pmconrad
Resolve bitshares#1781
6bb8213
@pmconrad pmconrad mentioned this issue Jun 29, 2019
Merged
@pmconrad
Copy link
Contributor

Merged #1836 - please keep this open until release notes are created. Public API nodes should activate the new plugin when upgrading.

@MichelSantos MichelSantos mentioned this issue Aug 9, 2019
Closed
manikey123 pushed a commit to manikey123/bitshares-core that referenced this issue Aug 12, 2019
@pmconrad @manikey123
Resolve bitshares#1781
07e665c
@pmconrad
Copy link
Contributor

Upgrade instructions are now mentioned in the release notes.

jmjatlanta pushed a commit that referenced this issue Sep 3, 2019
@pmconrad @jmjatlanta
Resolve #1781
aed7982
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pmconrad pmconrad

Labels
1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2d Developing Status indicating currently designing and developing a solution 3c Enhancement Classification indicating a change to the functionality of the existing imlementation 6 API Impact flag identifying the application programing interface (API) 6 Plugin Impact flag identifying at least one plugin 9a Tiny Effort estimation indicating TBD
Projects
None yet
Milestone
3.3.0 - Feature Release
Development

No branches or pull requests
3 participants
@pmconrad @abitmore @startailcoon