Get the address sent from

[madmadmax]

I have an address in bitcoind and I would like to receive the first address that bitcoins were sent from in Bitcoin.net.

For example if I have an address 37muSN5ZrukVTvyVh3mT5Zc5ew9L9CBare with a balance of 9.5 coins, I would like to receive the address those coins were sent from. This is a problem since I will have multiple addresses each with a couple of coins and I want to get the addresses the coins were sent from for each address.

[Stephen Gornick]

I have an address in bitcoind and I would like to receive the first address that bitcoins were sent from in Bitcoin.net.

For example if I have an address 37muSN5ZrukVTvyVh3mT5Zc5ew9L9CBare with a balance of 9.5 coins, I would like to receive the address those coins were sent from. This is a problem since I will have multiple addresses each with a couple of coins and I want to get the addresses the coins were sent from for each address.

The Raw Transactions API will give you this info.


Filter the results of listunspent for the output address to learn the transaction ids.  Then get each transaction and pull the first input for each.

use:
getrawtransaction
then for the output of that,
decoderawtransaction

 - http://en.bitcoin.it/wiki/Raw_Transactions

[Edit: See the next few posts to tell you why there is no "from" addresses with Bitcoin.   The right way to know what invoice a payment is for (or what customer sent the payment) is to give out a new address for each transaction.]

[Pieter Wuille]

If you want to distinguish separate incoming payments, the advised way is creating a separate receive address for each.

Bitcoin transactions do not really have 'from' addresses. All transactions do is consume coins, merge and split them, and produce new coins, potentially assigned to new address(es). It is indeed possible to retrieve where the input coins for your transaction were previously sent to, but in the general case this is not very useful information, as it only tells you which address previously controlled the coin, which is not necessarily the one who sent it. In the case of e-wallets with shared wallets, for example, it only tells you an address that belongs to the provider's wallet, and sending something to it will not necessary mean it ends up on the account of the one who sent it. If you want to do return payments, ask for a return address.

[madmadmax]

If you want to distinguish separate incoming payments, the advised way is creating a separate receive address for each.

Bitcoin transactions do not really have 'from' addresses. All transactions do is consume coins, merge and split them, and produce new coins, potentially assigned to new address(es). It is indeed possible to retrieve where the input coins for your transaction were previously sent to, but in the general case this is not very useful information, as it only tells you which address previously controlled the coin, which is not necessarily the one who sent it. In the case of e-wallets with shared wallets, for example, it only tells you an address that belongs to the provider's wallet, and sending something to it will not necessary mean it ends up on the account of the one who sent it. If you want to do return payments, ask for a return address.

This is what I do at the moment, how can I check from which address was the payment sent to mine?

[Pieter Wuille]

If you want to distinguish separate incoming payments, the advised way is creating a separate receive address for each.

Bitcoin transactions do not really have 'from' addresses. All transactions do is consume coins, merge and split them, and produce new coins, potentially assigned to new address(es). It is indeed possible to retrieve where the input coins for your transaction were previously sent to, but in the general case this is not very useful information, as it only tells you which address previously controlled the coin, which is not necessarily the one who sent it. In the case of e-wallets with shared wallets, for example, it only tells you an address that belongs to the provider's wallet, and sending something to it will not necessary mean it ends up on the account of the one who sent it. If you want to do return payments, ask for a return address.

This is what I do at the moment, how can I check from which address was the payment sent to mine?

[madmadmax]

If you want to distinguish separate incoming payments, the advised way is creating a separate receive address for each.

Bitcoin transactions do not really have 'from' addresses. All transactions do is consume coins, merge and split them, and produce new coins, potentially assigned to new address(es). It is indeed possible to retrieve where the input coins for your transaction were previously sent to, but in the general case this is not very useful information, as it only tells you which address previously controlled the coin, which is not necessarily the one who sent it. In the case of e-wallets with shared wallets, for example, it only tells you an address that belongs to the provider's wallet, and sending something to it will not necessary mean it ends up on the account of the one who sent it. If you want to do return payments, ask for a return address.

This is what I do at the moment, how can I check from which address was the payment sent to mine?

How is this possible then:http://blockchain.info/address/37muSN5ZrukVTvyVh3mT5Zc5ew9L9CBare    ?

I understand that the last address received from may not be the correct one and if you send there they might be lost but I still need it.

[kjj]

Look at the transaction that you got.  The input part of that transaction will have a list of transaction outputs redeemed.  For each of them, look up the transaction and check the scriptpubkey part of that output.

But you really should figure out a way to do whatever you are doing that doesn't require that, because no matter how much you think you need it, the system totally doesn't work that way.  Transactions do not have From: addresses.

[madmadmax]

Look at the transaction that you got.  The input part of that transaction will have a list of transaction outputs redeemed.  For each of them, look up the transaction and check the scriptpubkey part of that output.

But you really should figure out a way to do whatever you are doing that doesn't require that, because no matter how much you think you need it, the system totally doesn't work that way.  Transactions do not have From: addresses.

Is there any way to do it with Bitcoin .NET C#? I have been trying but can't seem to figure it out

[madmadmax]

Anyone? I am still looking for how to do it

[madmadmax]

*bump*

[kjj]

The answers are in this thread already.  What are you having problems with?

Are you wondering how to use the RPC service from .net?

[CIYAM]

I understand that the last address received from may not be the correct one and if you send there they might be lost but I still need it.

Perhaps it would help if you could tell us what exactly you need this for?

Also I hope you realise that it is even possible that funds could be sent to you from "coinbase" (e.g. if a miner were offering this as some kind of anonymising service) in which case there are no real inputs to tie your output to (apart from those of every tx that paid any fees in the entire block if that's of any use at all).

[madmadmax]

I understand that the last address received from may not be the correct one and if you send there they might be lost but I still need it.

Perhaps it would help if you could tell us what exactly you need this for?

Also I hope you realise that it is even possible that funds could be sent to you from "coinbase" (e.g. if a miner were offering this as some kind of anonymising service) in which case there are no real inputs to tie your output to (apart from those of every tx that paid any fees in the entire block if that's of any use at all).

I understand all this, it's still irrelevant for what I want to use it, I just need it.

The answers are in this thread already.  What are you having problems with?

Are you wondering how to use the RPC service from .net?

Yes, I am wondering what calls to make.

[kjj]

The answers are in this thread already.  What are you having problems with?

Are you wondering how to use the RPC service from .net?

Yes, I am wondering what calls to make.

The Raw Transactions API will give you this info.

Filter the results of listunspent for the output address to learn the transaction ids.  Then get each transaction and pull the first input for each.

use:
getrawtransaction
then for the output of that,
decoderawtransaction

 - http://en.bitcoin.it/wiki/Raw_Transactions

[CIYAM]

I understand all this, it's still irrelevant for what I want to use it, I just need it.

I think we have already explained that what you think you need simply does not exist - so can you now try once again to explain what you actually need (without re-stating what is in the thread title)?

[madmadmax]

I understand all this, it's still irrelevant for what I want to use it, I just need it.

I think we have already explained that what you think you need simply does not exist - so can you now try once again to explain what you actually need (without re-stating what is in the thread title)?

The address the coins were last owned by, return address, you get the point.

[CIYAM]

As I stated if the coins came from "coinbase" then there simply *is no return address* - do you get it now?

(also as was pointed out previously if the user was using a web-wallet service or some sort of "mixer" service the input address can in no way be reliably used to send coins back to the original sender - hence the warnings given to people wanting to play with satosh dice)

[madmadmax]

As I stated if the coins came from "coinbase" then there simply *is no return address* - do you get it now?

(also as was pointed out previously if the user was using a web-wallet service or some sort of "mixer" service the input address can in no way be reliably used to send coins back to the original sender - hence the warnings given to people wanting to play with satosh dice)

I already got it 100 times by now, I undestand that it isn't the most reliable method, what code would I use to get this address?

[DannyHamilton]

As I stated if the coins came from "coinbase" then there simply *is no return address* - do you get it now?

(also as was pointed out previously if the user was using a web-wallet service or some sort of "mixer" service the input address can in no way be reliably used to send coins back to the original sender - hence the warnings given to people wanting to play with satosh dice)

I already got it 100 times by now, I undestand that it isn't the most reliable method, what code would I use to get this address?

By now I'd think you would have noticed that you are getting a lot of responses saying that you can't get what you are asking for, and very few (any?) responses offering exactly what you are asking for.

I'd think this would seem to indicate one of the following:

• The entire bitcoin community is having fun at your expense by withholding from you the information you are asking for
• The entire bitcoin community is misunderstanding what you are asking for, perhaps you should try explaining it better.
• You aren't understanding what you are asking for, perhaps you should think about it a bit and try explaining it better
• You are asking for something that isn't available, perhaps you should consider a better way to accomplish your goal

Are there other possibilities here I haven't thought of?  Which of the above do you think is most likely?

[CIYAM]

I already got it 100 times by now, I undestand that it isn't the most reliable method, what code would I use to get this address?

The correct answer to your question is mu (please read G.E.B. to find out exactly what that means - and I hope you enjoy the experience as much as I did as it is IMHO one of the best books ever written).



For the lazy:

2. /moo/ The correct answer to the classic trick question "Have you stopped beating your wife yet?". Assuming that you have no wife or you have never beaten your wife, the answer "yes" is wrong because it implies that you used to beat your wife and then stopped, but "no" is worse because it suggests that you have one and are still beating her. According to various Discordians and Douglas Hofstadter the correct answer is usually "mu", a Japanese word alleged to mean "Your question cannot be answered because it depends on incorrect assumptions".