Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Development & Technical Discussion
Re: Bitcoin-etl transactions.json parameters explanation
by
kristiano92
on 08/10/2020, 09:35:14 UTC
Quote from: PrimeNumber7 on October 06, 2020, 07:21:44 PM
Quote from: kristiano92 on October 06, 2020, 04:17:34 PM
Quote from: PrimeNumber7 on October 04, 2020, 10:35:39 PM
Quote from: kristiano92 on October 04, 2020, 03:41:37 PM
Ok, thanks Smiley When it comes to outputs, can they be always "1" ? I haven't found any ouput > 1
The transaction you referenced in the OP has two outputs.

It is very common for an individual to have transactions that have exactly two outputs, one to the person/enttity they are sending coin to and one change output.

Many businesses who send many transactions per day will consolidate transactions such that they send coin to many individuals/entities in a single transaction.

Here is an example of a recent transaction that has more than two outputs.


I thought about required_signatures parameter for outputs. This parameter doesn't include P2SH Multisig. It shows "1" for multisigs addresses. I am right?
You cannot tell if an output needs to be signed by more than one private key.

The only exception to the above is if that address has previously signed a transaction that you can review.

Do you mean that is it possible only when I have input ?


I have one more question about bitcoin-etl. What is the best way to recognize witness transactions ? What parameters should be used ? Addresses , which starts with 3.. could be segwit or non-segwit (multisig)