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

rusk-wallet: Inconsistent address handling #2607

Closed
Rikkie82 opened this issue Oct 6, 2024 · 1 comment · Fixed by #2594
Closed

rusk-wallet: Inconsistent address handling #2607

Rikkie82 opened this issue Oct 6, 2024 · 1 comment · Fixed by #2594
Assignees
Labels
fix:bug Something isn't working

Comments

@Rikkie82
Copy link

Rikkie82 commented Oct 6, 2024

Describe the bug
if you have a cli wallet with two addresses you need to use command line to process transactions from 2nd address.
To stake on moonlight I needed to use phoenix address (tx shows moonlight stake). using moonlight address failed.

also to unstake I was unable to do so. Using moonlight address I get the error "address does not belong to this wallet", using phoenix address states "this is not a valid bls address"

also to do a moonlight transfer with 2nd address I get "address does not belong to this wallet"

To Reproduce

  • have a cli-wallet with two addresses
  • have funds only on 2nd address
  • try to stake / transfer / unstake using command-lines

Expected behaviour
consistent behaviour between command options (either accept phoenix address for all or enforce moonlight address)
ensure 2nd wallet is recognized as valid address

Logs/Screenshot
transfer attempt
moonlight address on 2nd wallet address
addresses

Platform
Vultr node according to specs of provisioner node from documents

Additional context

@Rikkie82 Rikkie82 added the fix:bug Something isn't working label Oct 6, 2024
@moCello moCello changed the title CLI wallet inconsistent address handling rusk-wallet: Inconsistent address handling Oct 7, 2024
@moCello
Copy link
Member

moCello commented Oct 7, 2024

Thanks for reporting this @Rikkie82. The issue should be fixed by #2594

@moCello moCello linked a pull request Oct 7, 2024 that will close this issue
@moCello moCello self-assigned this Oct 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix:bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants