First of, thanks for jb55’s fantastic device for making dumping a c-lighting key straightforward. Nevertheless, this isn’t the purpose of this publish.
What i’m right here to ask is in the event you have a look at his instance right here:
xprv9s21ZrQH143K2W9UqiTJL3qndXzRkEuzAoNwd6VLRu2VDtX6tACVz9q8BzDmJDkB6c6QQnfEWWvLtxB9M68XVpmcJCQodFrr843paWAXGeD root personal
xpub661MyMwAqRbcEzDwwjzJhBnXBZpv9hdqY2JYRUtwzEZU6grFRhWkXx9c3HJ4EKR1Nvdwf5U3VoekstoKSKjfcJYhRrhMYeEzZzu2h7uZAQX root public
xprv9wPk6zRy29x8BLXUHWh8ssqf89xQWtrZeLUgEXyUKSqNdUJhXTJsMtdLCexXxhgxPYUFpQvUhz2WAyhh3uCXSLedbHkvX7jTnX4xQofjdbA prolonged personal
combo(xprv9wPk6zRy29x8BLXUHWh8ssqf89xQWtrZeLUgEXyUKSqNdUJhXTJsMtdLCexXxhgxPYUFpQvUhz2WAyhh3uCXSLedbHkvX7jTnX4xQofjdbA/)#u4tc9nwu prolonged personal descriptor
xpub6AP6WVxrrXWRPpbwPYE9F1nPgBntvMaR1ZQH2vP5snNMWGdr4zd7ugwp3wukcTUxKu2rLCN9VBQAW3xioATnEWjZvQpx9cybj1jztJHJyp7 prolonged public
combo(xpub6AP6WVxrrXWRPpbwPYE9F1nPgBntvMaR1ZQH2vP5snNMWGdr4zd7ugwp3wukcTUxKu2rLCN9VBQAW3xioATnEWjZvQpx9cybj1jztJHJyp7/)#f64dm6yh prolonged public descriptor
Should you look actually rigorously, the precise prolong personal/public keys derived from the foundation (m/0/0) truly are totally different from what his instance says.
Somewhat it must be:
xprv9wT3HD7uDSkLA8WbJ7gVh57EJ3mmuVMesRTQSC8utJ3GCkCdp4LrbGFjrtW8vUjXEjL9tuC4uJpc33R6SYLxSx7qvRWgr7zf3pHxJupHzPG
xpub6ASPgieo3pJdNcb4Q9DW4D3xr5cGJx5WEeP1EaYXSdaF5YXnMbf794aDiBTMaEXXB5tkQgdjgWCGN7g8BocDF8CnFYaiUdEnzJxznPUi8Vx
Should you examine above with jb55’s instance after base58 decryption, you will notice that all the things is similar besides the [parent fingerprint] within the two xpubs and naturally the checksums. Regardless of the variations, they each produce the identical addresses.
What may consequence such a distinction in fingerprint occur? Does the writer purposely do this? It cannot be a mistake as a result of the checksum there’s only for stopping one.
One other query: will the distinction within the [parent fingerprint] make any points within the baby technology?