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

NAMI not cip69 compatible #959

Open
elRaulito opened this issue Oct 20, 2024 · 0 comments
Open

NAMI not cip69 compatible #959

elRaulito opened this issue Oct 20, 2024 · 0 comments

Comments

@elRaulito
Copy link

When an input from contract has not datum, Nami thinks it's coming from a regular address and asks for the signature

In plutus v3 datum is not required therefore signature won't be present
the validator script will be present istead

failed:
eb27a8514f650ea8738a2dcef10f22f3e3e4bd9d6b1af41a94aa0ec32f2211e5
Some signatures are missing. A signed transaction must carry signatures for all inputs locked by verification keys or a native script. Transaction may also need signatures for each required extra signatories often required by Plutus Scripts. The field 'data.missingSignatories' contains the verification key hashes of expected but missing signatories.
Data: {"missingSignatories":["3230f3088ea556970fa4ad23062814bbee812ce5b55f70e8d1df1c0c"]}
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