<p>Recently, I researched TX messages in the bitcoin protocol and captured some bitcoin traffic in which the version field of a TX message in a specific packet was <code>2</code>. The <a href="https://en.bitcoin.it/wiki/Transaction" rel="nofollow noreferrer">Transaction</a> page of the Bitcoin wiki mentioned that the tx version is currently <code>1</code>.</p>
<p>I checked out that packet and I found that it is a valid packet and its value and the generated output address from that tx message is valid.</p>

CC BY-SA 4.0
2019-05-29T10:06:12.310Z
That is outdated. Since the implementation of BIP-68 transactions have v2
Ugam Kamat
CC BY-SA 4.0
2019-06-02T04:34:24.240Z
@UgamKamat So, it means that now we have two valid version, V1 = 1 and V2 = 2. is it correct?
Saeed
CC BY-SA 4.0
2019-06-02T09:14:08.990Z
yes. Transaction can have either version 1 or 2. However, if you use `OP_CSV` in your transaction, then the transaction versioning MUST be v2. If your transaction does not have `OP_CSV` then v1 and v2 transactions have the same meaning.
Ugam Kamat
<transactions><transaction-version>
Which is the correct value for Tx version in tx messages of bitcoin pcap?
Saeed
# Which is the correct value for Tx version in tx messages of bitcoin pcap?

(Asked by: username_0 on 2019-05-29)

Recently, I researched TX messages in the bitcoin protocol and captured some bitcoin traffic in which the version field of a TX message in a specific packet was `2`. The [Transaction](https://en.bitcoin.it/wiki/Transaction) page of the Bitcoin wiki mentioned that the tx version is currently `1`.

I checked out that packet and I found that it is a valid packet and its value and the generated output address from that tx message is valid.

**Tags:** transactions, transaction-version

> **Comments:**
> **username_1**: That is outdated. Since the implementation of BIP-68 transactions have v2  
> **username_0**: @UgamKamat So, it means that now we have two valid version, V1 = 1 and V2 = 2. is it correct?  
> **username_1**: yes. Transaction can have either version 1 or 2. However, if you use `OP_CSV` in your transaction, then the transaction versioning MUST be v2. If your transaction does not have `OP_CSV` then v1 and v2 transactions have the same meaning.  

---

## 0 answers

