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.

Sign up for GitHub

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

Jump to bottom

how to set script flags when signing a tx #60

Open

torusJKL opened this issue Oct 18, 2022 · 1 comment

torusJKL commented Oct 18, 2022

With bsv.js (legacy 1.x version) we can define script flags when signing a transaction.

e.g.:
bsv.Interp.SCRIPT_ENABLE_MAGNETIC_OPCODES | bsv.Interp.SCRIPT_ENABLE_MONOLITH_OPCODES |
bsv.Interp.SCRIPT_VERIFY_STRICTENC |
bsv.Interp.SCRIPT_ENABLE_SIGHASH_FORKID | bsv.Interp.SCRIPT_VERIFY_LOW_S | bsv.Interp.SCRIPT_VERIFY_NULLFAIL |
bsv.Interp.SCRIPT_VERIFY_DERSIG |
bsv.Interp.SCRIPT_VERIFY_MINIMALDATA | bsv.Interp.SCRIPT_VERIFY_NULLDUMMY |
bsv.Interp.SCRIPT_VERIFY_DISCOURAGE_UPGRADABLE_NOPS |
bsv.Interp.SCRIPT_VERIFY_CHECKLOCKTIMEVERIFY | bsv.Interp.SCRIPT_VERIFY_CHECKSEQUENCEVERIFY | bsv.Interp.SCRIPT_VERIFY_CLEANSTACK

would be the flag value 870366.

When we sign with bsv-wasm we don't have the option to set the flags and the unlocking of our non-standard script fails.

Does bsv-wasm support settings flags when signing a tx?

Owner

Firaenix commented Apr 19, 2023

This isn't possible at the moment, I probably wont be adding it myself, however if there is a working PR with tests, I'd be happy to merge it in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment