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

InvalidArgumentError: Invalid signature - no finalScriptWitness #4

Open
brianorwhatever opened this issue Mar 30, 2023 · 3 comments
Open

Comments

@brianorwhatever
Copy link

I can't get the sell psbt to verify.. the verify function spits out "InvalidArgumentError: Invalid signature - no finalScriptWitness"
I'm not sure how to make the wallet (I'm using xverse) create this finalScriptWitness on the input.. any help would be appreciated

@brianorwhatever
Copy link
Author

It seems to me like the creation of a PSBT in this library is using the inscription tx as the input whereas it should be the current utxo that is associated with the inscription. Is this codebase out of date from what ME is using in production?

@nothing0012
Copy link
Contributor

This library requires a fully running data store api that provides the fresh location utxo of the inscription.

https://github.com/magiceden-oss/msigner/blob/main/src/interfaces.ts#L21-L24

@brianorwhatever
Copy link
Author

Hi @nothing0012, thanks for responding. Apologies, I should have been more explicit. I'm specifically talking about this input that is being used for the psbt https://github.com/magiceden-oss/msigner/blob/3de81d4aaac4d030b2fb2967d704a59070981777/src/signer.ts#L71

Shouldn't this tx hash be the current utxo holding the inscription instead of the inscription tx itself? Or is the ordItem.output the current utxo and I'm misunderstand that interface?

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