Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nomenclature - transaction ids are being populated in hash field for transaction #32

Open
aknirmal90 opened this issue Sep 5, 2019 · 3 comments
Labels
enhancement New feature or request

Comments

@aknirmal90
Copy link
Member

https://github.com/blockchain-etl/bitcoin-etl/blob/master/bitcoinetl/mappers/transaction_mapper.py#L41

Maybe place a disclaimer because I just found out that the hash was actually representing transaction_id.

@medvedev1088
Copy link
Member

I think it's a good idea. Do you know if BlockSci's tx.hash also contains txid https://citp.github.io/BlockSci/reference/chain/tx.html?

@aknirmal90
Copy link
Member Author

aknirmal90 commented Oct 31, 2019

Yes, BlockSci's tx.hash also references the txid and not the hash

Just verified that blocksci is also doing the same by reviewing a few segwit transactions on blocksci and my bitcoin node. The field they call hash is actually the txid field on the bitcoin-cli response.

@aknirmal90
Copy link
Member Author

Most blockchain explorers support lookups by txid but they call it hash.
Seems like most implementations are referencing txid as hash.

@allenday allenday added the enhancement New feature or request label May 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants