<p>The idea is that it is returning the hash of the entire transaction data. Currently, that is always identical to the wtxid.</p>
<p>But in a hypothetical future, where more data may get added to transaction serializations, in addition to the base data (covered by txid) and witness data, hash would change to always cover everything.</p>

CC BY-SA 4.0
2023-03-13T23:27:26.637Z
2023-03-13T23:27:26.637Z
Pieter Wuille
<p>In the industry txid is known as &quot;transaction hash&quot;. Why wasn't the &quot;hash&quot; field called &quot;wtxid&quot;?</p>

<bitcoin-core><json-rpc><hash><transaction-id><getrawtransaction>
Why is wtxid called "hash" in Bitcoin Core's getrawtransaction RPC?
harbar
# Why is wtxid called "hash" in Bitcoin Core's getrawtransaction RPC?

(Asked by: username_0 on 2023-03-13)

In the industry txid is known as "transaction hash". Why wasn't the "hash" field called "wtxid"?

**Tags:** bitcoin-core, json-rpc, hash, transaction-id, getrawtransaction


---

## 1 answers

### Answer by username_1 on 2023-03-13. Score: 2 | Accepted answer

The idea is that it is returning the hash of the entire transaction data. Currently, that is always identical to the wtxid.

But in a hypothetical future, where more data may get added to transaction serializations, in addition to the base data (covered by txid) and witness data, hash would change to always cover everything.


---

