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

Track total amount in collateral #1089

Closed
3 of 17 tasks
abitmore opened this issue Jun 24, 2018 · 2 comments
Closed
3 of 17 tasks

Track total amount in collateral #1089

abitmore opened this issue Jun 24, 2018 · 2 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) 3b Feature Classification indicating the addition of novel functionality to the design 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 API Impact flag identifying the application programing interface (API) 6 Plugin Impact flag identifying at least one plugin 6 UX Impact flag identifying the User Interface (UX) 9b Small Effort estimation indicating TBD
Milestone
3.3.0 - Feature R...

Comments

@abitmore
Copy link
Member

User Story
Quoting bitshares/bitshares-ui#890 (comment):

I'm looking for a tracker to be added to the reference wallet explorer that keeps track of the actual circulating supply of BTS that aren't locked up as collateral for MPAs.

Right now, the explorer only shows the "Current Supply" but doesn't not take into account the amount of BTS that's locked up in smart contracts. I think this information is extremely important because as the amount of MPAs increase, the amount of circulating BTS should decrease which means that BTS becomes more scarce and should apply some upward pressure on the value of BTS.

I know the market value of each MPA is tracked individually, but it takes a long time to add up the total market caps for all MPAs and then do the math to guesstimate the amount of BTS locked up as collateral.

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)
I think we need a new API or a new data field in asset dynamic data object to implement this feature. Can name the new data field "total_amount_in_collateral" or so.

Note: tracking this new data will negatively impact node performance, so best make it 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 mentioned this issue Jun 24, 2018
Open
@abitmore abitmore added 1b User Story The User Story details a requirement. It may reference a parent Epic. It may reference child Task(s) 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements 3b Feature Classification indicating the addition of novel functionality to the design 4b Normal Priority Priority indicating the moderate impact to system/user -OR- existing workaround is costly to perform 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 API Impact flag identifying the application programing interface (API) 9b Small Effort estimation indicating TBD 6 UX Impact flag identifying the User Interface (UX) 6 Plugin Impact flag identifying at least one plugin labels Jun 24, 2018
@abitmore abitmore mentioned this issue May 28, 2019
Closed
17 tasks
@pmconrad pmconrad added 2d Developing Status indicating currently designing and developing a solution and removed 2b Gathering Requirements Status indicating currently refining User Stories and defining Requirements labels Jun 27, 2019
@pmconrad pmconrad self-assigned this Jun 27, 2019
@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.

@abitmore abitmore removed 2d Developing Status indicating currently designing and developing a solution 4b Normal Priority Priority indicating the moderate impact to system/user -OR- existing workaround is costly to perform labels Aug 7, 2019
@MichelSantos MichelSantos mentioned this issue Aug 9, 2019
Closed
@pmconrad
Copy link
Contributor

Upgrade instructions are now mentioned in the release notes.

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) 3b Feature Classification indicating the addition of novel functionality to the design 5a Docs Needed Status specific to Documentation indicating the need for proper documentation to be added 6 API Impact flag identifying the application programing interface (API) 6 Plugin Impact flag identifying at least one plugin 6 UX Impact flag identifying the User Interface (UX) 9b Small Effort estimation indicating TBD
Projects
None yet
Milestone
3.3.0 - Feature Release
Development

No branches or pull requests
2 participants
@pmconrad @abitmore