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

bug: walletdir not scoped properly for testnet #5423

Open
coolaj86 opened this issue Jun 9, 2023 · 0 comments
Open

bug: walletdir not scoped properly for testnet #5423

coolaj86 opened this issue Jun 9, 2023 · 0 comments

Comments

@coolaj86
Copy link

coolaj86 commented Jun 9, 2023

I was testing running both mainnet and testnet on the same system and found that -walletdir is being handled improperly in conjunction with -testnet.

dashd -testnet -walletdir=/home/app/.dashcore/wallets/ # ...

Expected

~/.dashcore/wallets/testnet3/

Actual

/mnt/100gb/dashcore/_data/testnet3/wallets/

How to

/home/app/.local/opt/dashcore/bin/dashd \
    -testnet \
    -usehd \
    -conf=/home/app/.dashcore/dash.conf \
    -settings=/home/app/.dashcore/settings.json \
    -walletdir=/home/app/.dashcore/wallets/ \
    -datadir=/mnt/100gb/dashcore/_data \
    -blocksdir=/mnt/100gb/dashcore/_caches

The legacy behavior causes -datadir and -blocksdir to create a testnet3 namespace under each.

/mnt/100gb/dashcore/_data/testnet3/
/mnt/100gb/dashcore/_caches/testnet3/

Although unusual and unintuitive, this is partially documented and can be worked around in a pinch with symlinks and such.

We should expect -walletdir to follow the same behavior, but it does not.

  # expected
+ /home/app/.dashcore/wallets/
  # actual
- /mnt/100gb/dashcore/_data/testnet3/wallets/
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

No branches or pull requests

1 participant