Both NewEngine and GetWitnessSigOpCount used sigScript[1:] (a raw byte suffix of the scriptSig) to identify the candidate redeem script for nested P2SH witness detection. GetPreciseSigOpCount and the existing P2SH execution path already get the redeem script as the final pushed element of the push-only scriptSig (via finalOpcodeData and savedFirstStack[len-1] respectively). This commit consolidates the nested-witness detection sites to use finalOpcodeData(0, scriptSig) so all three places agree on what the redeem script is. As a side effect of using the actual redeem script for detection, the len(witness) != 0 precondition in NewEngine becomes redundant — the redeem script's shape alone determines whether the spend is nested witness, and verifyWitnessProgram already enforces the required witness-stack shape downstream. |
||
|---|---|---|
| .. | ||
| data | ||
| bench_test.go | ||
| consensus.go | ||
| doc.go | ||
| engine.go | ||
| engine_debug_test.go | ||
| engine_test.go | ||
| error.go | ||
| error_test.go | ||
| example_test.go | ||
| hashcache.go | ||
| hashcache_test.go | ||
| log.go | ||
| opcode.go | ||
| opcode_test.go | ||
| pkscript.go | ||
| pkscript_test.go | ||
| README.md | ||
| reference_test.go | ||
| script.go | ||
| script_test.go | ||
| scriptbuilder.go | ||
| scriptbuilder_test.go | ||
| scriptnum.go | ||
| scriptnum_test.go | ||
| sigcache.go | ||
| sigcache_test.go | ||
| sighash.go | ||
| sign.go | ||
| sign_test.go | ||
| sigvalidate.go | ||
| stack.go | ||
| stack_test.go | ||
| standard.go | ||
| standard_test.go | ||
| taproot.go | ||
| taproot_test.go | ||
| template.go | ||
| template_test.go | ||
| tokenizer.go | ||
| tokenizer_test.go | ||
txscript
Package txscript implements the bitcoin transaction script language. There is a comprehensive test suite.
This package has intentionally been designed so it can be used as a standalone package for any projects needing to use or validate bitcoin transaction scripts.
Bitcoin Scripts
Bitcoin provides a stack-based, FORTH-like language for the scripts in the bitcoin transactions. This language is not turing complete although it is still fairly powerful. A description of the language can be found at https://en.bitcoin.it/wiki/Script
Installation and Updating
$ go get -u github.com/btcsuite/btcd/txscript
Examples
-
Standard Pay-to-pubkey-hash Script
Demonstrates creating a script which pays to a bitcoin address. It also prints the created script hex and uses the DisasmString function to display the disassembled script. -
Extracting Details from Standard Scripts
Demonstrates extracting information from a standard public key script. -
Manually Signing a Transaction Output
Demonstrates manually creating and signing a redeem transaction. -
Counting Opcodes in Scripts
Demonstrates creating a script tokenizer instance and using it to count the number of opcodes a script contains.
GPG Verification Key
All official release tags are signed by Conformal so users can ensure the code has not been tampered with and is coming from the btcsuite developers. To verify the signature perform the following:
-
Download the public key from the Conformal website at https://opensource.conformal.com/GIT-GPG-KEY-conformal.txt
-
Import the public key into your GPG keyring:
gpg --import GIT-GPG-KEY-conformal.txt -
Verify the release tag with the following command where
TAG_NAMEis a placeholder for the specific tag:git tag -v TAG_NAME
License
Package txscript is licensed under the copyfree ISC License.
