<p>You don't.  Bitcoin doesn't work that way.  To identify the sender, you can provide a new Bitcoin address for each payment request and then you'll know from which party the funds were sent as only that party would have that Bitcoin address. </p>

<p>Some services, such as SatoshiDICE, return funds to one of the inputs in a transaction.  This frequently causes losses however as those sending from a hosted (shared) E-Wallet don't own the Bitcoin address that their payment was sent from.  So returning funds to one of those inputs benefits some party other than the intended user.</p>

<p>Other parties use unique payment amounts to uniquely identify the sender.  For instance, a payment of 1.23 could be suffixed as 1.23000001 to differentiate that from another party that was asked to pay 1.23000002.  However doing that is no less work than simply providing a unique Bitcoin address for the two payment requests.</p>

<p>Planned for a forthcoming version of the Bitcoin-Qt/bitcoind client is a <a href="https://github.com/bitcoin/bitcoin/pull/2539" rel="nofollow">Payment Protocol</a> which might be useful to you as well.  </p>

CC BY-SA 3.0
2013-08-01T00:43:19.453Z
2013-08-01T00:43:19.453Z
Stephen Gornick
<p>Rather - how does <code>SatoshiDice</code> do it? I know it's not proper format and people advise against it, but how is it technically possible?</p>

<bitcoind><satoshidice><raw-transaction>
How can I tell what input address sent me coin?
Shamoon
# How can I tell what input address sent me coin?

(Asked by: username_0 on 2013-07-25)

Rather - how does `SatoshiDice` do it? I know it's not proper format and people advise against it, but how is it technically possible?

**Tags:** bitcoind, satoshidice, raw-transaction


---

## 1 answers

### Answer by username_1 on 2013-08-01. Score: 4 | Accepted answer

You don't. Bitcoin doesn't work that way. To identify the sender, you can provide a new Bitcoin address for each payment request and then you'll know from which party the funds were sent as only that party would have that Bitcoin address.

Some services, such as SatoshiDICE, return funds to one of the inputs in a transaction. This frequently causes losses however as those sending from a hosted (shared) E-Wallet don't own the Bitcoin address that their payment was sent from. So returning funds to one of those inputs benefits some party other than the intended user.

Other parties use unique payment amounts to uniquely identify the sender. For instance, a payment of 1.23 could be suffixed as 1.23000001 to differentiate that from another party that was asked to pay 1.23000002. However doing that is no less work than simply providing a unique Bitcoin address for the two payment requests.

Planned for a forthcoming version of the Bitcoin-Qt/bitcoind client is a [Payment Protocol](https://github.com/bitcoin/bitcoin/pull/2539) which might be useful to you as well.


---

