📅 Original date posted:2022-05-10
📝 Original message:> I suppose ultimately this brings up the question of the scope of this BIP. The abstract points out that the BIP contains both a definition of address derivation, but also how to sign fidelity bond certificates.
>
> My feeling is that the latter might be better not included? I note that the 'Motivation' section gives motivation for standardisation of derivation (this includes things like time schedule), but not the second area - certificate signing. I think the second area is much more tricky, but much more to the point is, isn't it the case that that second area, can be interpreted without consensus between wallet developers? So say you were a hardware wallet provider, or a "node in a box" provider - your customers want you to provide the ability move funds around, including e.g. moving funds out of an old Joinmarket wallet (in which say there is a now expired timelock address utxo) by just entering its BIP39 seed. If this BIP addresses that, it should be enough.
>
> I don't doubt that there's gains to be had from a broader community discussing and agreeing the details of how to create a fidelity bond certificate, but it's a separate, and more difficult, task.
>
> Cheers,
> waxwing/AdamISZ
Further to that last point, as the BIP draft currently says:
" Almost all wallets implementing this standard can use their
already-existing "Sign Message" function to sign the certificate
message. As the certificate message itself is always an ascii string,
the wallet may not need to specially implement this section at all but
just rely on users copypasting their certificate message into the
already-existing "Sign Message" user interface. This works as long as
the wallet knows how to use the private key of the timelocked address
for signing messages."
So, isn't that an argument that we don't need to specify the certificate message format here?
On the other hand, I can hardly disagree that it's worth presenting a kind of 'default' way of doing it. But I fear it is not at all simple to decide what a secure, general format should be (as per the discussion we started having here about domain separation tags).
Cheers,
waxwing/AdamISZ
AdamISZ [ARCHIVE] /
npub1nv…kqw2t
2023-06-08 01:08:50
in reply to nevent1q…0wf8
Author Public Key
npub1nv7tjpn2g8tvt8qfq5ccyl00ucfcu98ch998sq4g5xp65vy6fc4sykqw2tPublished at
2023-06-08 01:08:50Event JSON
{
"id": "af0cf41aeb627e4b60b055b8ecb4e213487176d2cc01d4400d6d9f160be49589",
"pubkey": "9b3cb9066a41d6c59c090531827defe6138e14f8b94a7802a8a183aa309a4e2b",
"created_at": 1686179330,
"kind": 1,
"tags": [
[
"e",
"ed87b4a661b1ec563ef35bba3e76c69fedd4dee29f9239e792212ae30f6447d4",
"",
"root"
],
[
"e",
"67b5affd6449fee36a786abd016c3dafb4d24b5d3ca00c2d861b127ba6cbaaf2",
"",
"reply"
],
[
"p",
"9b3cb9066a41d6c59c090531827defe6138e14f8b94a7802a8a183aa309a4e2b"
]
],
"content": "📅 Original date posted:2022-05-10\n📝 Original message:\u003e I suppose ultimately this brings up the question of the scope of this BIP. The abstract points out that the BIP contains both a definition of address derivation, but also how to sign fidelity bond certificates.\n\u003e\n\u003e My feeling is that the latter might be better not included? I note that the 'Motivation' section gives motivation for standardisation of derivation (this includes things like time schedule), but not the second area - certificate signing. I think the second area is much more tricky, but much more to the point is, isn't it the case that that second area, can be interpreted without consensus between wallet developers? So say you were a hardware wallet provider, or a \"node in a box\" provider - your customers want you to provide the ability move funds around, including e.g. moving funds out of an old Joinmarket wallet (in which say there is a now expired timelock address utxo) by just entering its BIP39 seed. If this BIP addresses that, it should be enough.\n\u003e\n\u003e I don't doubt that there's gains to be had from a broader community discussing and agreeing the details of how to create a fidelity bond certificate, but it's a separate, and more difficult, task.\n\u003e\n\u003e Cheers,\n\u003e waxwing/AdamISZ\n\nFurther to that last point, as the BIP draft currently says:\n\n\" Almost all wallets implementing this standard can use their\nalready-existing \"Sign Message\" function to sign the certificate\nmessage. As the certificate message itself is always an ascii string,\nthe wallet may not need to specially implement this section at all but\njust rely on users copypasting their certificate message into the\nalready-existing \"Sign Message\" user interface. This works as long as\nthe wallet knows how to use the private key of the timelocked address\nfor signing messages.\"\n\nSo, isn't that an argument that we don't need to specify the certificate message format here?\n\nOn the other hand, I can hardly disagree that it's worth presenting a kind of 'default' way of doing it. But I fear it is not at all simple to decide what a secure, general format should be (as per the discussion we started having here about domain separation tags).\n\nCheers,\nwaxwing/AdamISZ",
"sig": "0d5262664bd8fca7127ebfe51d0019e00132d820df8295c90d6e0a8a7b982356c3e195ab67846ae0ae2fd8c0edc6d3acbd1f52ea6783837a73cbdf9872462bac"
}