<p>When you use that site, you are encoding the hex as a hex string, not of the actual bytes that they should be. The base58 encoding for addresses operates on the bytes themselves which are represented in the hex string. However that website is just encoding the hex string (which, as bytes, is double the length and is entirely other data).</p>

CC BY-SA 4.0
2018-05-06T03:42:39.897Z
2018-05-06T03:42:39.897Z
Ava Chow
<p>Andrew Chow told you <em>why</em>. Now I'll tell you how.</p>

<p>First, convert hex to ASCII (I suggest <a href="https://www.rapidtables.com/convert/number/hex-to-ascii.html" rel="nofollow noreferrer">this website</a>)</p>

<p>(I can't copy the ASCII result below, since that would cause problems.)</p>

<p>Then copy the weird-looking ASCII text it created, and paste it to the Base58 Encoder.</p>

<p><a href="https://i.sstatic.net/1QXRv.gif" rel="nofollow noreferrer"><img src="https://i.sstatic.net/1QXRv.gif" alt="enter image description here"></a></p>

<p>Done!</p>

CC BY-SA 4.0
2018-05-06T15:37:18.260Z
2018-05-06T15:37:18.260Z
MCCCS
<p>I am trying to convert public key hex to Bitcoin address.</p>

<p>From this website <a href="http://gobittest.appspot.com/Address" rel="nofollow noreferrer">http://gobittest.appspot.com/Address</a>, I can do some test.</p>

<p>For example, I have this public key:</p>

<pre><code>04b4d653fcbb4b96000c99343f23b08a44fa306031e0587f9e657ab4a2541129368d7d9bb05cd8afbdf7705a6540d98028236965553f91bf1c5b4f70073f55b55d
</code></pre>

<p>According to the website, the address should be:</p>

<pre><code>1DU8Hi1sbHTpEP9vViBEkEw6noeUrgKkJH
</code></pre>

<p>which is the base58 encode of <code>0088C2D2FA846282C870A76CADECBE45C4ACD72BB655DA1216</code>.</p>

<p>However, if I do Base58 encoding directly on <code>0088C2D2FA846282C870A76CADECBE45C4ACD72BB655DA1216</code> on this website <a href="https://www.browserling.com/tools/base58-encode" rel="nofollow noreferrer">https://www.browserling.com/tools/base58-encode</a>, I will get:</p>

<pre><code>bSLwwticQjhNvEtqTMZXbn3dLmFrPvNrDGE4hmHsfADpHWb3b2ruh3XqtNzv8ESS8V6V
</code></pre>

<p>which is totally different from the 34-char Bitcoin address.</p>

<p>Anyone knows why? </p>

<bitcoin-core><address><public-key><address-generation><base58>
base58 cannot get 34 chars results (as Bitcoin address does) but 68 chars
fluency03
# base58 cannot get 34 chars results (as Bitcoin address does) but 68 chars

(Asked by: username_0 on 2018-05-06)

I am trying to convert public key hex to Bitcoin address.

From this website <http://gobittest.appspot.com/Address>, I can do some test.

For example, I have this public key:

```
04b4d653fcbb4b96000c99343f23b08a44fa306031e0587f9e657ab4a2541129368d7d9bb05cd8afbdf7705a6540d98028236965553f91bf1c5b4f70073f55b55d

```

According to the website, the address should be:

```
1DU8Hi1sbHTpEP9vViBEkEw6noeUrgKkJH

```

which is the base58 encode of `0088C2D2FA846282C870A76CADECBE45C4ACD72BB655DA1216`.

However, if I do Base58 encoding directly on `0088C2D2FA846282C870A76CADECBE45C4ACD72BB655DA1216` on this website <https://www.browserling.com/tools/base58-encode>, I will get:

```
bSLwwticQjhNvEtqTMZXbn3dLmFrPvNrDGE4hmHsfADpHWb3b2ruh3XqtNzv8ESS8V6V

```

which is totally different from the 34-char Bitcoin address.

Anyone knows why?

**Tags:** bitcoin-core, address, public-key, address-generation, base58


---

## 2 answers

### Answer by username_1 on 2018-05-06. Score: 4

When you use that site, you are encoding the hex as a hex string, not of the actual bytes that they should be. The base58 encoding for addresses operates on the bytes themselves which are represented in the hex string. However that website is just encoding the hex string (which, as bytes, is double the length and is entirely other data).


---

### Answer by username_2 on 2018-05-06. Score: 1

Andrew username_1 told you *why*. Now I'll tell you how.

First, convert hex to ASCII (I suggest [this website](https://www.rapidtables.com/convert/number/hex-to-ascii.html))

(I can't copy the ASCII result below, since that would cause problems.)

Then copy the weird-looking ASCII text it created, and paste it to the Base58 Encoder.

[![enter image description here](https://i.sstatic.net/1QXRv.gif)](https://i.sstatic.net/1QXRv.gif)

Done!


---

