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

Issue with constructTransaction endpoint for a wallet created from xpub #4872

Open
3 tasks done
szymonmaslowski opened this issue Dec 9, 2024 · 3 comments
Open
3 tasks done
Assignees

Comments

@szymonmaslowski
Copy link

Just checking...

  • This is a cardano-wallet bug.
  • I am using the latest cardano-wallet release.
  • I am using the correct cardano-node version for that release of cardano-wallet.

Version

v2024-11-18

Platform

macOS 14

Installation method

Nix

Network configuration

preview

Context

In the Daedalus, we serve HWs by restoring them in the Cardano Wallet using their account_public_key. Those wallets are having an issue calling the constructTransaction endpoint.

Description

Steps to Reproduce

  1. Restore a wallet in Cardano Wallet using its account_public_key
  2. Call the constructTransaction endpoint with { vote: 'abstain' } payload

Expected behavior

TX with votes delegation is correctly constructed

Actual behavior

Receiving an missing_policy_public_key error in response

@szymonmaslowski
Copy link
Author

Unfortunately, changes from this PR do not solve the problem. Here is the change in the Daedalus repo bumping the CW to revision from the PR.

@szymonmaslowski
Copy link
Author

There are reports from Daedalus users experiencing the same problem with wallets restored from mnemonic. In this case, the problem seems to affect only some of the wallets. Our team was not able to reproduce it.

@abailly
Copy link
Collaborator

abailly commented Dec 16, 2024

@szymonmaslowski I can see this issue is referenced from a closed issue on your side, and there's been a Daedalus release, is this still relevant? Also, the description of the issue's context is pretty terse, can you elaborate on the conditions under which you observed the behaviour to be incorrect? Is this only for HW wallets? If I just restore a wallet from public key but the secret key is software, do you observe the same problem? What's the state of the wallet? How are the ADA's delegated?

It would help to have a minimal example reproducing the issue.

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

2 participants