VTA Benchmark
Deep Technical Audit

Script Flags + P2SH Verification

This audit focuses on the validation flags actually passed into the VTA transaction-input verification path, and on the distinction between ordinary script execution and Pay-to-Script-Hash (P2SH) policy/validation. It avoids importing modern Bitcoin flags into VTA unless the inspected VTA source establishes them.

P2SH

VERIFIED IN VTA PATH

The audited VTA mempool path calls CheckInputs() with SCRIPT_VERIFY_P2SH together with SCRIPT_VERIFY_STRICTENC.

Strict Encoding

VERIFIED IN VTA PATH

STRICTENC is part of the inspected CheckInputs() invocation used during transaction acceptance.

Modern Flags

NOT ASSUMED

DERSIG, LOW_S, NULLDUMMY, WITNESS, TAPROOT and other modern flags are not claimed for VTA without release-specific source evidence.

Validation Flow

Inputprevout + script data CheckInputs()input authorization P2SH + STRICTENCflags observed in path Script Evaluationsignature / P2SH logic Resultaccept/reject Why the flags matter P2SH enables redeem-script evaluation; STRICTENC constrains accepted signature/public-key encodings. These are validation rules in the inspected path — not a blanket statement about every VTA release. Modern-feature boundary No SegWit / Taproot / modern script-flag support is inferred from Bitcoin's current source.

Audit Matrix

AreaFindingStatus
P2SH flagVTA's inspected AcceptToMemoryPool() path calls CheckInputs() with SCRIPT_VERIFY_P2SH.Verified
STRICTENC flagThe same inspected call includes SCRIPT_VERIFY_STRICTENC.Verified
Script engineThe source contains EvalScript(), including stack, element and opcode resource limits.Verified
CHECKSIGThe script engine reaches signature checking through CHECKSIG/CheckSig logic.Verified
CHECKMULTISIGThe script engine validates key/signature counts and iterates signatures against public keys.Verified
P2SH sigopsThe supplied VTA paper documents counting P2SH signature operations toward the block sigops limit to reduce expensive-to-validate block attacks.Documented in paper
DER / LOW-S / NULLDUMMYNo current VTA claim is made here without exact VTA source evidence for those individual flags.Not established
SegWit / TaprootModern Bitcoin script features are not imported into this VTA audit by analogy.Not established
Independent script test vectorsNo live corpus of valid/invalid VTA scripts was executed by this page.Not measured

Payment Relevance

Authorization

P2SH and signature rules determine whether a spending transaction can satisfy the locking conditions of an output.

DoS resistance

Script and sigop limits reduce the amount of validation work a transaction or block can impose.

Version discipline

A feature should be marked supported only after the exact VTA release/source path is verified.

Evidence rule: The strongest VTA-specific finding here is the actual flag combination observed in the transaction-input verification call: P2SH + STRICTENC. Modern Bitcoin flags are deliberately not used as evidence for VTA.