Skip to content

Bug&Enhance: CMD Database Init #665

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

Closed
andy-shi88 opened this issue Mar 17, 2020 · 0 comments · Fixed by #680
Closed

Bug&Enhance: CMD Database Init #665

andy-shi88 opened this issue Mar 17, 2020 · 0 comments · Fixed by #680
Labels
BUG Something isn't working CMD command line tool feature ENHANCE
Milestone

Comments

@andy-shi88
Copy link
Contributor

Description

CMD was started as core developers support tools, so that we can test the blockchain easily, including:

  • generating fake blocks
  • generate and post transaction
  • generate account, and etc.

Recently we started to adjust cmd tools so that the wallet or possibly other team can also use the binary of the cli tools to help development, for instance: [generate multisig account, validating the transaction bytes they've built without posting to node (this is usefull when dev nodes are down), etc].

Therefore the design of cmd need some tweaks, which is to avoid initiating database file when not needed.

Current design initialize database file whenever the binary is run, no matter what command we are running.

Breakdown

  • move database initialization only to where it's needed.
@andy-shi88 andy-shi88 added BUG Something isn't working ENHANCE CMD command line tool feature labels Mar 17, 2020
@andy-shi88 andy-shi88 added this to the Milestone 14 milestone Mar 17, 2020
@sukrawidhyawan sukrawidhyawan self-assigned this Mar 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BUG Something isn't working CMD command line tool feature ENHANCE
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants