-
-
Notifications
You must be signed in to change notification settings - Fork 131
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
Unable to sign TX #51
Comments
Hey, what Lucid version are you on? |
I'm using the latest version from Vasil branch. 0.5.0 |
Regarding Nami I can say it doesn't work with the vasil branch yet because it was not updated yet. If you want to try Nami with vasil there is a seperate version for it: https://github.com/Berry-Pool/nami-wallet/tree/vasil |
Is there another way to test it? If Nami isnt supported and eternl isn't showing anything. |
Nami will support the Vasil changes as soon as the HF occurs on mainnet, but right now the testnet version of the official Nami extension still thinks it's in Alonzo. So in the meantime you can play with the seperate Vasil version of Nami. |
I'm happy to report that this does fix the issue. I think I was misunderstanding your earlier message. My apologies! |
Hi,
First of all, thank you very much for creating this library.
I've been trying to set this up in a Vue project but I'm getting an error when trying to sign the tx.
The error I get:
Uncaught (in promise) {code: -1, info: 'Inputs do not conform to this spec or are otherwise invalid.'}
The wallet has enough tADA in it. Nami is in testnet mode.
When trying with Eternl it opens the sign window but there's no information about the tx and I also can't sign it.
I've tried to check if it can 'see' the wallet, when I enter invalid address it will tell me. If I exceed the amount of available tADA it will tell me. So it has access to the UTXO's
The solution is probably very simple, but after 4 hours, I'm unable to determine the cause.
Any help would be greatly appreciated!
The text was updated successfully, but these errors were encountered: