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

Same always fail script on Liqwid and Wingriders #413

Open
MarcelKlammer opened this issue Apr 17, 2024 · 1 comment
Open

Same always fail script on Liqwid and Wingriders #413

MarcelKlammer opened this issue Apr 17, 2024 · 1 comment

Comments

@MarcelKlammer
Copy link

Wingriders requested that the following script

CBOR: 4746010000222601
Hash: 51936f3c98a04b6609aa9b5c832ba1182cf43a58e534fcc05db09d69
mainnet: addr1w9gexmeunzsykesf42d4eqet5yvzeap6trjnflxqtkcf66g5740fw
preprod: addr_test1wpgexmeunzsykesf42d4eqet5yvzeap6trjnflxqtkcf66g0kpnxt

is marked as it's own entry, because it's a simple always fail script, that is currently added to the Liqwid entry.

The name of the new entry could be something like: "always-fail-script"

It's an edge case, but both platforms use the same script and Wingriders would rather not see their script marked as Liqwid's script since that's confusing in UIs.

@t4ccer
Copy link

t4ccer commented Apr 21, 2024

We have the same issue at Clarity, we use it to reference inputs containing scripts

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