bitshares / bitshares-core

BitShares Blockchain node and command-line wallet

Home Page:https://bitshares.github.io/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

The `extended-history-by-registrar` option in account history plugin does not track LTM correctly

abitmore opened this issue · comments

commented

User Story

Background:

  • We added the extended-history-by-registrar option to the account history plugin via #2259 to track accounts with extended parameters.

Issue:

  • If an account is registered by a registrar we track and then it upgraded to LTM, the plugin no longer tracks it with extended parameters.

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)
    • account history plugin

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