In contexts outside of "mempool policy", and broader than only transactions, what do the terms non-standard and standard mean (e.g. with reference to blocks, headers and well as transactions)?

How are they distinct from the term invalid ?

Are there any other terms or measures that might be used to refer to the "standardness" or validity of blocks, headers or transactions?

  • 3
    Does this answer your question? What is "(mempool) policy"? Commented May 2 at 12:02
  • @AntoinePoinsot possibly - you've a good answer there; does it still apply for contexts outside the mempool and more broadly than only transactions? (I have updated for this).
    – Lee
    Commented May 2 at 12:18
  • @AntoinePoinsot Does "standardness" only apply to transactions?
    – Lee
    Commented May 2 at 12:26
  • bitcoin.stackexchange.com/questions/52528/…
    – Lee
    Commented May 2 at 12:35
  • 1
    Yes, we only talk about standardness in the context of a transaction. Commented May 2 at 12:46

1 Answer 1


The terms standard and non-standard are specific to transactions. They have no application outside of that.

The terms originate from the IsStandard() function in the original Bitcoin software. Originally, the following five transaction types were considered standard:


The following were later added:


Anything other than these is non-standard.

Valid transactions are those that pass validity checks (e.g. matching UTXO(s) exist, script operates correctly).

It is possible for a transaction to be non-standard yet valid.

There is discussion of validity vs standardness here.

The term valid or validity may also be applied more broadly; to a block or block header for example.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.