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

Add --useDevPrivilegeKeys option to enable usage of dev keys for testing #1103

Closed

Conversation

mrosseel
Copy link
Contributor

  • added parser option in both BisqAppMain and BisqExecutable
  • made USE_DEV_PRIVILEGE_KEYS non-final

"are overridden by a dev key pair. Features: Arbitration registration" +
" (alt+R at account), Alert/Update (alt+m), private message to a peer " +
"(click user icon and alt+r), filter/block offers by various data like" +
" offer ID (cmd + f)", false));
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not needed here.

if(options.has(AppOptionKeys.USE_DEV_PRIVILEGE_KEYS)) {
DevEnv.USE_DEV_PRIVILEGE_KEYS = true;
}

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not needed here.

But all the other places where the option keys are applied are missing.

@ManfredKarrer
Copy link
Contributor

Not complete for merge. See comments. Just follow other option keys to see where changes have to be applied.

@mrosseel
Copy link
Contributor Author

Ok, will do.

@cbeams cbeams closed this Feb 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants