BIP48 currently defines script types only for p2wsh and p2sh-p2wsh, but not for the newer p2tr.
This PR proposes defining the the script_type for p2tr as 3
, to provide a clear standard for the derivation to use in p2tr scripts.
BIP48 currently defines script types only for p2wsh and p2sh-p2wsh, but not for the newer p2tr.
This PR proposes defining the the script_type for p2tr as 3
, to provide a clear standard for the derivation to use in p2tr scripts.
196@@ -194,6 +197,13 @@ Public derivation is used at this level.
197 |-
198 |testnet
199 |first
200+|p2tr
201+|external
202+|first
203+|m / 48' / 1' / 0' / 3' / 0 / 0
98@@ -99,10 +99,10 @@ Hardened derivation is used at this level.
99
100 ===Script===
101
102-This level splits the key space into two separate <code>script_type</code>(s). To provide
103+This level splits the key space into three separate <code>script_type</code>(s). To provide
104 forward compatibility for future script types this specification can be easily extended.
105
106-Currently the only script types covered by this BIP are Native Segwit (p2wsh) and
107+Currently the only script types covered by this BIP are Taproot (p2tr), Native Segwit (p2wsh) and
This would need sign-off by the BIP author (Fontaine dentondevelopment@protonmail.com).
Pinging @Fonta1n3 for feedback or approval.
This would need sign-off by the BIP author (Fontaine dentondevelopment@protonmail.com).
Pinging @Fonta1n3 for feedback or approval.
Thanks for the ping, appreciate it, will have a look this afternoon and revert back.
247+|testnet
248+|first
249+|p2tr
250+|external
251+|first
252+|m / 48' / 1' / 0' / 3' / 0 / 0
I didn’t add because there was none for p2sh-p2wsh, only testnet, but we could add for both I think.
Would you like to make a PR?