Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
S
slips
Project
Project
Details
Activity
Releases
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
CI / CD
CI / CD
Pipelines
Jobs
Schedules
Charts
Registry
Registry
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Jobs
Commits
Issue Boards
Open sidebar
DeStream-public
slips
Commits
9a5cc31c
Commit
9a5cc31c
authored
Oct 11, 2017
by
Tomas Susanka
Committed by
Pavol Rusnak
Oct 11, 2017
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
slip-0032: typo (#118)
parent
9ee7b4b0
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
slip-0032.md
slip-0032.md
+2
-2
No files found.
slip-0032.md
View file @
9a5cc31c
...
...
@@ -42,11 +42,11 @@ Extended public and private keys are serialized as follows:
*
32 bytes: the chain code
*
33 bytes: the public key or private key data (ser
<sub>
P
</sub>
(K) for public keys, 0x00 || ser
<sub>
256
</sub>
(k) for private keys)
This structure is encoded using Bech32 format described in BIP-01
37
. We will
This structure is encoded using Bech32 format described in BIP-01
73
. We will
use 'xpub' human-readable part for extended public keys and 'xprv' for extended
private keys.
## References
*
[
BIP-0032: Hierarchical Deterministic Wallets
](
https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki
)
*
[
BIP-0173: Base32 address format for native v0-16 witness outputs
](
https://github.com/bitcoin/bips/blob/master/bip-01
37
.mediawiki
)
*
[
BIP-0173: Base32 address format for native v0-16 witness outputs
](
https://github.com/bitcoin/bips/blob/master/bip-01
73
.mediawiki
)
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment