đź“… Original date posted:2021-02-11
đź“ť Original message:Hi Dmitry,
Thank you very much for readying and analyzing my proposal!
>> Testnet path is unhardened from this point & till the end of the
>> derivation path: no need to prevent private key leak there,
>> simplifies test software (hardened paths require private key access
>> for derivation).
>
> I believe this will reduce robustness and will add complexity to the
> test software instead. If the derivation path is hardened in 'production
> code' and is unhardened in 'test code', then: code paths that depend on
> hardened derivation may not be tested; there will be unnecessary
> code that will need to deal with 'un-hardening' the paths for test code.
<...>
> It is OK to require privkey access to hardened paths in test
> software, because the same behaviour is expected in 'production’.
You are right, agree
> It is much more robust to just change the 'purpose' part of the path,
> and leave the rest unchanged.
Not sure whether the purpose is the correct place to indicate testnet: in this case it we will have to support one testnet per each blockchain type (which is not the case). So probably we should reserve a single dedicated value for any testnet withing ``blockchain` field using hardened path as you suggested - for instance, 0xFFFFFFFF may do the job.
Kind regards,
Maxim
Dr Maxim Orlovsky [ARCHIVE] /
npub1a8…rpwgy
2023-06-07 18:28:27
in reply to nevent1q…ekm3
Author Public Key
npub1a80jcetgws9xmu7wnylvekpymw2acym2psjpp03e0chmhq38pc8qwrpwgyPublished at
2023-06-07 18:28:27Event JSON
{
"id": "2611be4b65d336f4885c6197c0dac52b3403510a14f1d491f84b79d0113f9825",
"pubkey": "e9df2c6568740a6df3ce993eccd824db95dc136a0c2410be397e2fbb82270e0e",
"created_at": 1686162507,
"kind": 1,
"tags": [
[
"e",
"d2c8b65efdaee73f5c5fd62fe4b915d4fcf718277dfab7951f3a1bbc122c404e",
"",
"root"
],
[
"e",
"b26ec5f4537811ab8445e7a0e18b1f91513e6f7cb4f686f0651fe5b869e3d239",
"",
"reply"
],
[
"p",
"78f5a82a0b64fb3c18bd33a69c53b1af612b3ac8dd81e12f74ba62f3793dac05"
]
],
"content": "📅 Original date posted:2021-02-11\n📝 Original message:Hi Dmitry,\n\nThank you very much for readying and analyzing my proposal!\n\n\u003e\u003e Testnet path is unhardened from this point \u0026 till the end of the\n\u003e\u003e derivation path: no need to prevent private key leak there,\n\u003e\u003e simplifies test software (hardened paths require private key access\n\u003e\u003e for derivation).\n\u003e \n\u003e I believe this will reduce robustness and will add complexity to the\n\u003e test software instead. If the derivation path is hardened in 'production\n\u003e code' and is unhardened in 'test code', then: code paths that depend on\n\u003e hardened derivation may not be tested; there will be unnecessary\n\u003e code that will need to deal with 'un-hardening' the paths for test code.\n\u003c...\u003e\n\u003e It is OK to require privkey access to hardened paths in test\n\u003e software, because the same behaviour is expected in 'production’.\n\nYou are right, agree\n\n\u003e It is much more robust to just change the 'purpose' part of the path,\n\u003e and leave the rest unchanged.\n\nNot sure whether the purpose is the correct place to indicate testnet: in this case it we will have to support one testnet per each blockchain type (which is not the case). So probably we should reserve a single dedicated value for any testnet withing ``blockchain` field using hardened path as you suggested - for instance, 0xFFFFFFFF may do the job.\n\nKind regards,\nMaxim",
"sig": "c155fc1692e7ebd44cbcd24f82ce39e8cf381fb2a30af00bae4bfb5e6e4ef9879c7e721bb0474384d5dc35f843948f4aae60c49fcaeec40b259ee4128af33b53"
}