<p><a href="http://mpex.us" rel="nofollow">MPEx</a> uses the last 7 decimals to identify individual deposits made to their publicly known deposit address. Here is a sample of how they do it:</p>

<pre><code>-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In order to make this deposit please send to the exchange address ( 1Fx3N5iFPDQxUKhhmDJqCMmi3U8Y7gSncx ) the sum of 10.03878878 BTC exactly. Your transaction will be manually approved, so please allow up to 48 hours for funds to show up in your account.

If your funds don't show up within 48 hours please contact mircea_popescu in #bitcoin-assets. Thank you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFQrFKnkhT8a/G2mSERAu4cAKCSkXszTDUquQT83nhzpXTlqxDd1ACgiBiO
gq0FBE+XYRV+AJrUHXuWC0E=
=2Azr
-----END PGP SIGNATURE-----
</code></pre>

CC BY-SA 3.0
2012-11-24T06:26:19.790Z
Satoshidice, e. g., use the unit 1 satoshi (0,00000001 BTC) to "tell" you that you lost in a bet.
Felipe
CC BY-SA 3.0
2013-03-29T23:41:09.330Z
And this is one of the most retarded uses one could do, since they should instead use personalised addresses...
o0'.
CC BY-SA 3.0
2012-11-21T04:03:21.787Z
2012-11-21T04:03:21.787Z
smickles
<p>I believe some of the Bitcoin gambling sites use the Satoshi level digits to indicate the 'roll of the dice', 'spin of the wheel' etc. </p>

CC BY-SA 3.0
2012-11-22T21:47:29.363Z
2012-11-22T21:47:29.363Z
jim618
<p>One idea that comes to mind is to use them as a transaction ID to bind the sender to the recipient instead of generating a unique Bitcoin address per sender.  If done carefully, this may allow more versatile use of vanity addresses.</p>

<p>Since the address space of the transactions is relatively small (only 5 digits to play with), one idea is to use a random 4 digit suffix that is valid for a short period of time.  Use the final / Fifth bit as a checksum that can also be ommitted if the conversion rate BTC to USD exceeds $100 but is below $999</p>

<p>Example</p>

<ol>
<li>An item costs 10 BTC, and the buyer clicks "check out"</li>
<li>The seller creates a new transaction ID (9998) records it, and makes it expire in 1 day.</li>
<li>The seller calculates the checksum.  Since the sum of 9+9+9+8 is 35, an odd number, the checksum is set to "1".  (if it had been even the checksum would be "0")</li>
<li>On checkout the seller pays 10.00019998 BTC to the seller, possibly to a vanity address</li>
<li>The payment is received by the seller and visible in the transaction history.</li>
<li>The seller does checksum of the transaction (9998) with the checksum bit (1) and passes</li>
<li>The result is even so the transaction is valid (less likely a typo was made)</li>
<li>The seller looks up transaction ID 9998 in the database.  If the Tx is invalid, or the date is greater than 24 hours, then a refund is sent to the seller.</li>
</ol>

CC BY-SA 3.0
2012-11-20T18:25:41.057Z
2012-11-20T18:38:14.297Z
2012-11-20T18:38:14.297Z
makerofthings7
<p>At the current conversion rates only the first three decimal points of an individual Bitcoin can be exchanged for a USD equivalent.  e.g. 0.002 BTC equals 2 USD cents.</p>

<p>That opens up possibilities for using the last five decimal places of a Bitcoin to include "metadata" about the transaction.</p>

<p>What alternative usages are there for these few bits and is anyone using them?</p>

<transactions><vanity-address><satoshi><business>
Alternative uses for last five decimal places of an individual Bitcoin (0.000xxxxx)
makerofthings7
# Alternative uses for last five decimal places of an individual Bitcoin (0.000xxxxx)

(Asked by: username_0 on 2012-11-20)

At the current conversion rates only the first three decimal points of an individual Bitcoin can be exchanged for a USD equivalent. e.g. 0.002 BTC equals 2 USD cents.

That opens up possibilities for using the last five decimal places of a Bitcoin to include "metadata" about the transaction.

What alternative usages are there for these few bits and is anyone using them?

**Tags:** transactions, vanity-address, satoshi, business


---

## 3 answers

### Answer by username_1 on 2012-11-21. Score: 0 | Accepted answer

[MPEx](http://mpex.us) uses the last 7 decimals to identify individual deposits made to their publicly known deposit address. Here is a sample of how they do it:

```
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In order to make this deposit please send to the exchange address ( 1Fx3N5iFPDQxUKhhmDJqCMmi3U8Y7gSncx ) the sum of 10.03878878 BTC exactly. Your transaction will be manually approved, so please allow up to 48 hours for funds to show up in your account.

If your funds don't show up within 48 hours please contact mircea_popescu in #bitcoin-assets. Thank you.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFQrFKnkhT8a/G2mSERAu4cAKCSkXszTDUquQT83nhzpXTlqxDd1ACgiBiO
gq0FBE+XYRV+AJrUHXuWC0E=
=2Azr
-----END PGP SIGNATURE-----

```

> **Comments:**
> **username_2**: Satoshidice, e. g., use the unit 1 satoshi (0,00000001 BTC) to "tell" you that you lost in a bet.  
> **username_3**: And this is one of the most retarded uses one could do, since they should instead use personalised addresses...  

---

### Answer by username_4 on 2012-11-22. Score: 1

I believe some of the Bitcoin gambling sites use the Satoshi level digits to indicate the 'roll of the dice', 'spin of the wheel' etc.


---

### Answer by username_0 on 2012-11-20. Score: 1

One idea that comes to mind is to use them as a transaction ID to bind the sender to the recipient instead of generating a unique Bitcoin address per sender. If done carefully, this may allow more versatile use of vanity addresses.

Since the address space of the transactions is relatively small (only 5 digits to play with), one idea is to use a random 4 digit suffix that is valid for a short period of time. Use the final / Fifth bit as a checksum that can also be ommitted if the conversion rate BTC to USD exceeds $100 but is below $999

Example

1. An item costs 10 BTC, and the buyer clicks "check out"
2. The seller creates a new transaction ID (9998) records it, and makes it expire in 1 day.
3. The seller calculates the checksum. Since the sum of 9+9+9+8 is 35, an odd number, the checksum is set to "1". (if it had been even the checksum would be "0")
4. On checkout the seller pays 10.00019998 BTC to the seller, possibly to a vanity address
5. The payment is received by the seller and visible in the transaction history.
6. The seller does checksum of the transaction (9998) with the checksum bit (1) and passes
7. The result is even so the transaction is valid (less likely a typo was made)
8. The seller looks up transaction ID 9998 in the database. If the Tx is invalid, or the date is greater than 24 hours, then a refund is sent to the seller.


---

