--- Log opened Tue Feb 28 00:00:57 2023
06:52 -!- provoostenator [~provooste@user/provoostenator] has quit [Ping timeout: 260 seconds]
06:53 -!- bitcoin-git [~bitcoin-g@2001:470:69fc:105::2:690] has quit [Ping timeout: 260 seconds]
07:09 -!- provoostenator [~provooste@user/provoostenator] has joined #bitcoin-hwi
07:34 < ghost43_> is there some spec somewhere what notations to accept for a hardened bip32 path level, as part of a string?
07:34 < ghost43_> I've seen ', h/H, p/P, even negative numbers...
07:36 < ghost43_> AFAICS bip32 does not even mention this
08:00 -!- bitcoin-git [~bitcoin-g@2001:470:69fc:105::2:690] has joined #bitcoin-hwi
08:00 -!- bitcoin-git [~bitcoin-g@2001:470:69fc:105::2:690] has quit [Excess Flood]
08:16 -!- bitcoin-git [~bitcoin-g@2001:470:69fc:105::2:690] has joined #bitcoin-hwi
08:36 -!- Netsplit *.net <-> *.split quits: ajonas, warren
08:37 -!- Netsplit over, joins: warren, ajonas
09:39 < achow101> ghost43_: ', h, and H are acceptable for HWI
09:39 < achow101> but I don't think there's actually a spec that defines it
09:40 < achow101> and bip32 uses a subscript H
11:33 < ghost43_> achow101: https://github.com/bitcoin-core/HWI/blob/43cc81d3af7e1de20fa8c92570d305440bb0a33b/hwilib/descriptor.py#L200
11:33 < ghost43_> p/P is also mentioned here at least
11:34 < ghost43_> (but not in key.parse_path)
12:13 < achow101> Yeah, I don't remember where I saw that, but I guess someone must've used that notation at one point
--- Log closed Wed Mar 01 00:00:58 2023