summaryrefslogtreecommitdiff
path: root/bip-0048.mediawiki
diff options
context:
space:
mode:
authorFonta1n3 <fontainedenton@googlemail.com>2021-02-24 21:36:10 +0800
committerFonta1n3 <fontainedenton@googlemail.com>2021-02-24 21:36:10 +0800
commitbf8c208da516143b75d62241279887e61b86e1bb (patch)
treef22c1170f780fca3ea09860e25c66ccb4fee285b /bip-0048.mediawiki
parent86e77903bac083f70f19a3356e28eb5174e8cab7 (diff)
downloadbips-bf8c208da516143b75d62241279887e61b86e1bb.tar.xz
fix: define motivation, remove account creation blurb.
Diffstat (limited to 'bip-0048.mediawiki')
-rw-r--r--bip-0048.mediawiki18
1 files changed, 9 insertions, 9 deletions
diff --git a/bip-0048.mediawiki b/bip-0048.mediawiki
index 245a066..4f8d542 100644
--- a/bip-0048.mediawiki
+++ b/bip-0048.mediawiki
@@ -21,10 +21,16 @@ This BIP is a particular application of BIP43.
==Motivation==
+The motivation of this BIP is to define the existing industry wide practice of utilizing m/48'
+derivation paths in hierarchical deterministic multi-sig wallets so that other developers may
+benefit from a standard.
+
The hierarchy proposed in this paper is quite comprehensive. It allows the handling of
multiple accounts, external and internal chains per account, multiple script types and
millions of addresses per chain.
+This paper was inspired from BIP44.
+
==Key sorting==
Any wallet that supports BIP48 inherently supports deterministic key sorting as per BIP67 so that all possible
@@ -75,21 +81,15 @@ This number is used as child index in BIP32 derivation.
Hardened derivation is used at this level.
-Software should prevent a creation of an account if a previous account does not
-have a transaction history (meaning none of its addresses have been used before).
-
-Software needs to discover all used accounts after importing the seed from
-an external source. Such an algorithm is described in "Account discovery" chapter.
-
===Script===
-This level splits the key space into three separate <code>script_type</code>(s). To provide
+This level splits the key space into two separate <code>script_type</code>(s). To provide
backward and forward compatibility.
-The following represent mainnet, account 0:
-
The recommended default is pay to witness script hash <code>m/48'/0'/0'/2'</code>.
+The following represent mainnet, account 0:
+
<code>1'</code>: Nested Segwit (p2sh-p2wsh) <code>m/48'/0'/0'/1'</code></br>
<code>2'</code>: Native Segwit (p2wsh) <code>m/48'/0'/0'/2'</code></br>