<p>Lets assume the private key is <strong>0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff</strong> </p>

<ol>
<li><p>Both Bitcoin and Doge can share a common private key and use the same Elliptic Curve algorithms to synthesize public keys.   </p>

<p>Here is a working example for how one can synthesize an <strong>uncompressed</strong> public key for Bitcoin or Doge from a common 256-bit hexadecimal encoded integer private key. </p>

<p>% echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public -u </p>

<p><strong>040d47568a5e517067a2836c3823fbc58169a7662bfae934a4d41da3e23c98d816e7202dd702ffe038147f78aee4973a581972960a1460312ffb6f3f0f13d4a52c</strong></p></li>
<li><p>Here is how a <strong>compressed public key</strong> can be calculated for either Bitcoin or Doge. Notice the public key is half the size.</p>

<p>% echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public </p>

<p><strong>020d47568a5e517067a2836c3823fbc58169a7662bfae934a4d41da3e23c98d816</strong></p></li>
<li><p>Computation of compressed and uncompressed Bitcoin and Doge addresses. One must examine this <a href="https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings#bip44-altcoin-version-mapping-table" rel="nofollow noreferrer"><strong>table</strong></a> to understand the <strong>version</strong> values [-v flags] that must be different for Bitcoin-based altcoins used such as Doge. Unsure if Doge fully supports compressed addresses, but is very likely to do so if the Doge source code forks are updated when Bitcoin is updated. Compressed addresses have been supported by Bitcoin for over 4 years.</p>

<p>% echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public | bx ec-to-address -v 0 </p>

<p><strong>1PbStXjfDNBU6FZA2iSeisVWwCFN9GK1eQ</strong> (is a compressed address)</p>

<p>% echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public | bx ec-to-address -v 30</p>

<p><strong>DTjYRngJWn5kdFjkmJSDGdf7pKyfUnVnGg</strong> (is a compressed address)</p>

<p>% echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public -u | bx ec-to-address -v 0</p>

<p><strong>1NGoV1EGZrwM7yvUYqRC7TMBMj7ftpjR2B</strong> (is an uncompressed address)</p>

<p>% echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public -u | bx ec-to-address -v 30</p>

<p><strong>DSQu2GAusGqdez75HRQkfDWnErqyEB4Bov</strong> (is an uncompressed address)</p></li>
<li><p>Believe the answer is yes.</p></li>
</ol>

CC BY-SA 3.0
2017-10-11T22:39:18.900Z
2017-10-11T22:39:18.900Z
skaht
<ol>
<li>Can I use the same method of generating Bitcoin private key and public key for Dogecoin?</li>
<li>After No.1 above is complete, does Dogecoin support compressed public key?</li>
<li>How do I generate Dogecoin address from the result of No.1 public key?</li>
<li>Can I use the same Bitcoin signing method on Dogecoin?</li>
</ol>

<p>Thank you</p>

<dogecoin>
Generate Dogecoin Keys
AFwcxx
# Generate Dogecoin Keys

(Asked by: username_0 on 2017-10-11)

1. Can I use the same method of generating Bitcoin private key and public key for Dogecoin?
2. After No.1 above is complete, does Dogecoin support compressed public key?
3. How do I generate Dogecoin address from the result of No.1 public key?
4. Can I use the same Bitcoin signing method on Dogecoin?

Thank you

**Tags:** dogecoin


---

## 1 answers

### Answer by username_1 on 2017-10-11. Score: 2

Lets assume the private key is **0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff**

1. Both Bitcoin and Doge can share a common private key and use the same Elliptic Curve algorithms to synthesize public keys.

   Here is a working example for how one can synthesize an **uncompressed** public key for Bitcoin or Doge from a common 256-bit hexadecimal encoded integer private key.

   % echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public -u

   **040d47568a5e517067a2836c3823fbc58169a7662bfae934a4d41da3e23c98d816e7202dd702ffe038147f78aee4973a581972960a1460312ffb6f3f0f13d4a52c**
2. Here is how a **compressed public key** can be calculated for either Bitcoin or Doge. Notice the public key is half the size.

   % echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public

   **020d47568a5e517067a2836c3823fbc58169a7662bfae934a4d41da3e23c98d816**
3. Computation of compressed and uncompressed Bitcoin and Doge addresses. One must examine this [**table**](https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings#bip44-altcoin-version-mapping-table) to understand the **version** values [-v flags] that must be different for Bitcoin-based altcoins used such as Doge. Unsure if Doge fully supports compressed addresses, but is very likely to do so if the Doge source code forks are updated when Bitcoin is updated. Compressed addresses have been supported by Bitcoin for over 4 years.

   % echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public | bx ec-to-address -v 0

   **1PbStXjfDNBU6FZA2iSeisVWwCFN9GK1eQ** (is a compressed address)

   % echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public | bx ec-to-address -v 30

   **DTjYRngJWn5kdFjkmJSDGdf7pKyfUnVnGg** (is a compressed address)

   % echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public -u | bx ec-to-address -v 0

   **1NGoV1EGZrwM7yvUYqRC7TMBMj7ftpjR2B** (is an uncompressed address)

   % echo "0000111122223333444455556666777788889999aaaabbbbccccddddeeeeffff" | bx ec-to-public -u | bx ec-to-address -v 30

   **DSQu2GAusGqdez75HRQkfDWnErqyEB4Bov** (is an uncompressed address)
4. Believe the answer is yes.


---

