0

Reading this thread about determining the sending address of a bitcoin transaction. I'm a bit confused, how do you differentiate between the change address and the "receiving" address of the last transaction?

txid = <relevant transaction id>
addresses = []
raw_tx = decoderawtransaction(getrawtransaction(txid))
for(input in raw_tx['vin']) {
  input_raw_tx = decoderawtransaction(getrawtransaction(input['txid']))
  addresses.push(input_raw_tx['vout'][input['vout']]['scriptPubKey']['addresses'] [0])
}

Would addresses not include other outputs that are unrelated to the sending address? I'm trying to build a block explorer and I'm uncertain how to determine which address sent coins in each transaction. Is it possible to tell?

Community
  • 1
bvpx
  • 1,132
  • 7
  • 28
  • Payments are not sent from addresses, they're only sent *to* addresses. – David Schwartz Aug 04 '13 at 18:22
  • Is that to say there is no way to tell with 100% certainty which address signed a transaction into the network? – bvpx Aug 04 '13 at 21:30
  • 1
    You can tell which address(es) keys were used to sign the transaction, but that doesn't tell you who sent the transaction, only what keys were needed to sign it. – David Schwartz Aug 05 '13 at 03:07
  • Let's say a website has online wallets, and each account is given an address which they can send coins to other addresses on the site from. Considering the site controls every RPC call of all of these addresses, and you always use the `sendfrom` command, is it true that you'd be able to tell which address signed each transaction? Is there any possibility for abuse if the users of the site don't have access to the private keys? (I'm thinking of making a color coin type app, with small transaction amounts, but very long delays between transactions to avoid spam of the network). – bvpx Aug 05 '13 at 05:14
  • I can't see how that would work, unless the site sends each transaction twice, first to the source it needs to send them from for the real send. To the extent you can send funds "from" an address, it must be the address those funds were last sent *to*. Also, I'm not sure this would help -- people wouldn't, in general, know transactions came from this site so even if this site could make the information reliable, people wouldn't know it was reliable and so couldn't rely on it. – David Schwartz Aug 05 '13 at 06:43
  • Could the site not provide a signed message to prove it owns an address? The idea is that the "color coin" within this network of people should not be sent outside of the network and is tracked by the site itself, which validates sending and receiving bits of that color coin amongst users of the site. It's simply using the blockchain to recognize these transactions publicly. – bvpx Aug 05 '13 at 18:20
  • Yeah, but I think that would be an example of an entire class of silly answers to the question you asked. You can be 100% certain that a payment was sent from a specified address if **you** sent it too. Yes, if some out of band mechanism you trust, assures you of something, then you can be certain of it. – David Schwartz Aug 05 '13 at 19:26
  • possible duplicate of [When a transaction is split into two outputs, how does the network "know" you're the owner of the "change" address?](http://bitcoin.stackexchange.com/questions/12468/when-a-transaction-is-split-into-two-outputs-how-does-the-network-know-youre) – Stephen Gornick Aug 06 '13 at 03:57
  • @Stephen Gornick the questions are entirely different, this is a blockchain data structure question whereas the last question was about the distinction between an address, an account, and the way the private key works in the wallet. They are sort of similar, though. – bvpx Aug 06 '13 at 16:38

2 Answers2

2

From the Bitcoin Wiki:

An input is a reference to an output in a different transaction.

A transaction can have multiple outputs, e.g., a normal one and the change, which specify the recipient address in their scriptPubKey. So usually to each output belongs one address, and the input specifies which output it redeems.

If an output specifies multiple destination addresses (which is rarely the case), only one of those can redeem the transaction. You can find out which one by looking at the scriptSig of the input.

Malte
  • 151
  • 5
  • Okay, so the `addresses` field in the `scriptPubKey` can potentially contain multiple addresses? What `scriptSig` specifically can allow this? – bvpx Aug 03 '13 at 21:57
2

Every output is identified by the hash of the transaction it is in, and the serial number of this output in the list of transaction outputs.

If an output is spent as the input of another transaction, the input of that transaction contains two fields, txid and vout, to specify the tx id and the serial number of that output.

In the code snippet you give, first input['txid'] is used to pinpoint the transaction, and then input['vout'] is used to find the specific output.

Meni Rosenfeld
  • 19,650
  • 35
  • 70
  • Okay, so when you're looking at a transaction, the `vin` array contains `txid` and `vout` metadata, so if you then look at that `txid` and find the `vout` with the same `n` value as `vout` you've found the output that refers to that exact transaction? Meaning you can be sure that if you're looking at the `vout` field of the transaction with the `txid` hash and `n = vout` then you've found the exact output that refers to that input? But can't `addresses` in the `scriptPubKey` array have more than one address? – bvpx Aug 03 '13 at 21:54
  • @bvpx: I'm not sure but I believe multisig outputs will have multiple addresses listed. – Meni Rosenfeld Aug 04 '13 at 07:54