ScriptPubKey classifier
Edit a fixture, predict the first changed field, then run it.
Script decides whether one input may spend one previous output. This guide begins with stack execution, then builds signatures, branches, hashes, timelocks, classic templates, native witness programs and nested SegWit forms.
Each specialist lesson expands one relationship in this end-to-end map.
ScriptPubKey commits the spending condition and value being spent.
ScriptSig and witness supply signatures, public keys, scripts and branch selectors.
Nodes apply opcodes in order under consensus limits and transaction context.
Hashes bind revealed keys or scripts to what the output committed earlier.
Signature opcodes verify the selected transaction digest and public key.
The input succeeds only if execution completes with a true top stack item.
You will be able to step through a stack trace, locate the first failed predicate, and build P2PK, P2PKH, P2MS, P2SH, OP_RETURN and native or nested SegWit forms.
Predict first, execute exact bytes or rules, then change one input and inspect the first failed boundary.
Switch among P2PK, P2PKH, bare P2MS, P2SH, and OP_RETURN. The trace exposes the exact stack item, commitment, or failure boundary unique to each form.
The first tool classifies the previous output and states the exact spend data it requires. The second parses a length-prefixed ScriptSig and hands it to that output. The third compiles an editable witness program and executes its stack.
Edit a fixture, predict the first changed field, then run it.
Edit a fixture, predict the first changed field, then run it.
Edit a fixture, predict the first changed field, then run it.
Use real learner input rather than a prewritten answer. Every result is calculated locally from the fields shown and invalid data fails closed.
Apply SHA-256 then RIPEMD-160 to hexadecimal bytes.
Change any field, predict what should change, then run the utility.
Safety boundary: This learning surface does not store inputs. Never paste a live seed phrase, private key, wallet backup, or confidential transaction.
Start at the top for a guided route, or open any lesson directly.
Script is a deliberately constrained stack language whose success depends on final truth and consensus limits.
Teach, predict, run, explainData pushes, numeric encodings, conditionals, and verification opcodes compose spending policies.
Teach, predict, run, explainCHECKSIG validates a signature over a transaction digest selected by a sighash mode.
Teach, predict, run, explainLegacy templates separate address-friendly commitments from revealed spending scripts.
Teach, predict, run, explainSegWit moves authorization data into witness structures and versions the program semantics.
Teach, predict, run, explainMultiple keys, timelocks, and hashlocks can form recovery, escrow, and channel policies.
Teach, predict, run, explainDisabled opcodes, resource limits, encoding rules, and malleability protections constrain safe composition.
Teach, predict, run, explainExperts trace every stack transition, identify the failing predicate, and distinguish malformed witnesses from false conditions.
Teach, predict, run, explainCompare the exact assembly, serialized bytes, spend data, standard uses, and failure boundary for Bitcoin's classic Script templates.
Teach, predict, run, explainConstruct P2WPKH, P2WSH, P2SH-P2WPKH, and P2SH-P2WSH outputs and follow each redeem, witness, hash, and signature check.
Teach, predict, run, explainThese distinctions stop the most consequential mistakes in this topic.