Mike Macgirvin (dev) (npub1vcv…9su0) They were actually talking about changing eddsa-jcs-2022: https://github.com/digitalbazaar/data-integrity/issues/19#issuecomment-1847297553
>At this point, we should presume the eddsa-jcs-2022 spec is wrong and we should fix it.
I think we have two options:
1. Define new cryptosuite (e.g. eddsa-jcs-2022-fep-8b32) and use it. Switch to eddsa-jcs-2022` once the spec is stabilized
2. Go with eddsa-jcs-2022 and later try to guess what variant of eddsa-jcs-2022 is used. Run verification procedure according to the new spec, and if it fails, run according to the old spec.
(2) is probably easier at this point, no need to change the FEP, and also makes the argument against breaking the spec stronger
silverpill /
npub1df0…7gmw
2024-01-28 19:42:04
in reply to nevent1q…20jl
Author Public Key
npub1df0nthpgzfmvxrzj0cfypmmt45l0y770j260auqhm3l45hp3uhkqx27gmwPublished at
2024-01-28 19:42:04Event JSON
{
"id": "57a1ac973a2a90f0a77eee7c968c5199dd76482296e3c06c80897d93229a41ea",
"pubkey": "6a5f35dc281276c30c527e1240ef6bad3ef27bcf92b4fef017dc7f5a5c31e5ec",
"created_at": 1706467324,
"kind": 1,
"tags": [
[
"p",
"6619f50b64de2459dd1af3095893bac67a10b7ab9166fdde33dfcd3c0f194b00",
"wss://relay.mostr.pub"
],
[
"e",
"ff66568ac5911e00a8dd5163a01ea3a132d5b5d88d80ba50d8cd5877d623e4c6",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://mitra.social/objects/018d5160-f30f-a153-24a3-27f0b2f2101b",
"activitypub"
]
],
"content": "nostr:npub1vcvl2zmymcj9nhg67vy43ya6ceappdatj9n0mh3nmlxncrcefvqq789su0 They were actually talking about changing eddsa-jcs-2022: https://github.com/digitalbazaar/data-integrity/issues/19#issuecomment-1847297553\n\n\u003eAt this point, we should presume the eddsa-jcs-2022 spec is wrong and we should fix it.\n\nI think we have two options:\n\n1. Define new cryptosuite (e.g. eddsa-jcs-2022-fep-8b32) and use it. Switch to eddsa-jcs-2022` once the spec is stabilized\n2. Go with eddsa-jcs-2022 and later try to guess what variant of eddsa-jcs-2022 is used. Run verification procedure according to the new spec, and if it fails, run according to the old spec.\n\n(2) is probably easier at this point, no need to change the FEP, and also makes the argument against breaking the spec stronger",
"sig": "b50da3b79a2964149d6dc4224254240abad5f10d74807ee414dc09cd6fe6a6e595dfcb2bece9bfebad724e65b485a025a95a79d564866bf570b6feb74ce27ee7"
}