This is probably a stupid question, but is there a way to scrape a sender addy?

[coingenuity]

As far as I can tell, there's no CLI call that enables the client to get the sender's address when the CLI is the receiving account/address. I might be wrong, since the wiki hasn't been updated since 0.3.20.2, but there's no call that I can find that allows you to do it. I wrote a simple workaround, but it would be nice if there was an easy command that I've glazed over somewhere.

Any clues?

[1714956820]

1714956820

[error]

As far as I can tell, there's no CLI call that enables the client to get the sender's address when the CLI is the receiving account/address. I might be wrong, since the wiki hasn't been updated since 0.3.20.2, but there's no call that I can find that allows you to do it. I wrote a simple workaround, but it would be nice if there was an easy command that I've glazed over somewhere.

Any clues?

The transaction input addresses are available, but they may not correspond to the actual entity who ordered the bitcoins sent to you. For instance, if you send bitcoins to your wallet from an exchange or online wallet service like CampBX or Instawallet, then the sending addresses belong to the web service, not you, and are semantically useless for determining the actual person who sent the bitcoins.

[coingenuity]

How do you output an input address from within bitcoind?

[error]

How do you output an input address from within bitcoind?

You would have to patch bitcoind to get that information, or use an external tool like bitcointools.

[wumpus]

How do you output an input address from within bitcoind?

There is not really such a thing as 'input address' in Bitcoin. A transaction can have zero, one or multiple inputs. Those inputs can be addresses that received coins, but don't have to be. For example, generation transactions have no inputs at all. Transactions can spend multiple inputs when the amount to send is higher than the size of one of the inputs. And for more advanced scripts/contracts it might also work differently. This is why it is not shown in the UI.

If you want more detailed information about the inputs used you can enable debug mode (-debug) then doubleclick on a transaction...

[coingenuity]

How do you output an input address from within bitcoind?

You would have to patch bitcoind to get that information, or use an external tool like bitcointools.

Ah, beautiful. Thanks for the links.

[error]

How do you output an input address from within bitcoind?

You would have to patch bitcoind to get that information, or use an external tool like bitcointools.

Ah, beautiful. Thanks for the links.

Be careful when using that information. It may or may not be meaningful in whatever application you have envisioned (which you didn't disclose).

[coingenuity]

How do you output an input address from within bitcoind?

You would have to patch bitcoind to get that information, or use an external tool like bitcointools.

Ah, beautiful. Thanks for the links.

Be careful when using that information. It may or may not be meaningful in whatever application you have envisioned (which you didn't disclose).

I was mostly curious. I've already got a good solution, I just wondered if there was a better one.