Bitcoin Core decodescript RPC: Script Classification Guide

This guide explains Bitcoin Core decodescript RPC in plain English. It shows what the command does, what its result means and what it cannot prove.

Raw hex is authoritative

Validate even-length bounded hex and retain its exact digest before decoding. Assembly is a human-readable interpretation and can omit byte-level distinctions relevant to non-minimal pushes or unusual encodings. Reviews should compare the original script bytes and parsed opcode stream, not recreate policy solely from displayed assembly text.

Type classification

The returned type is a template classification such as pubkey hash, script hash or non-standard. Classification is descriptive, not proof of standard relay or spendability at a particular height. Unknown or non-standard results require deeper analysis and must not be coerced into a familiar address merely to satisfy application schemas.

Required signatures

reqSigs is an inferred summary for recognised templates, not a universal execution theorem. Bitcoin Script can contain conditionals, timelocks, hashlocks and branches whose actual requirements depend on stack data and consensus context. Decode the complete policy and test representative satisfaction and failure paths before making custody claims.

Address presentation

The addresses array may provide familiar encodings for recognised scripts. An address is derived presentation, while the scriptPubKey or redeem script is the payment condition. Validate network and checksum and compare the exact expected script. Avoid claiming ownership because one address appears in a decoder response.

P2SH wrapper

For a redeem script that is not already P2SH, the historical result can show a p2sh address that would commit to the script. This does not register the script in any wallet, supply private keys or guarantee recovery. Preserve the redeem script and import it through a reviewed watch or spend workflow before funding the wrapper.

No execution or signatures

decodescript does not run the program, apply block-height rules or verify a witness or scriptSig. Use an isolated script harness or regtest spend with exact consensus version for execution claims. Separate descriptive decoding from policy evaluation and from financial approval.

How specialists test it

Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.

Conclusion

decodescript helps classify and review script bytes, but it does not establish policy, ownership or spendability. Reliable use keeps the raw script authoritative and proves execution separately under the intended consensus context.