<p>An extended public or private key is always 78 bytes of data. When Base58 Check encoded, this results in a string that is up to 112 characters in size.</p>

<p>The format of the data is defined in <a href="https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#serialization-format" rel="noreferrer">BIP 32</a>.</p>

CC BY-SA 4.0
2020-09-10T09:48:51.143Z
is there any lower bound ? or is it arbitrary -> I have tried to generate like few thousands of extended keys and they are all 111 characters in size - Is this the rule or can it be less/more?
scagbackbone
CC BY-SA 4.0
2020-09-10T15:05:18.060Z
It should be a fixed size.
Ava Chow
CC BY-SA 4.0
2018-08-23T14:45:02.000Z
2018-08-23T14:45:02.000Z
Ava Chow
<p>What is the typical bytesize range for an extended public key? </p>

<p>An extended private key? </p>

<wallet><bip32-hd-wallets><xpub>
What is the typical size for an extended public key?
arshbot
# What is the typical size for an extended public key?

(Asked by: username_0 on 2018-08-23)

What is the typical bytesize range for an extended public key?

An extended private key?

**Tags:** wallet, bip32-hd-wallets, xpub


---

## 1 answers

### Answer by username_1 on 2018-08-23. Score: 6 | Accepted answer

An extended public or private key is always 78 bytes of data. When Base58 Check encoded, this results in a string that is up to 112 characters in size.

The format of the data is defined in [BIP 32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#serialization-format).

> **Comments:**
> **username_2**: is there any lower bound ? or is it arbitrary -> I have tried to generate like few thousands of extended keys and they are all 111 characters in size - Is this the rule or can it be less/more?  
> **username_1**: It should be a fixed size.  

---

