- From: Christopher Allen <ChristopherA@lifewithalacrity.com>
- Date: Thu, 31 Jul 2025 12:49:35 -0400
- To: Will Abramson <wip.abramson@gmail.com>
- Cc: Credentials Community Group <public-credentials@w3.org>
Received on Thursday, 31 July 2025 16:49:51 UTC
In On Thu, Jul 31, 2025 at 12:11 PM Will Abramson <wip.abramson@gmail.com> wrote: > Hello CCG community, > > Digital Contract Design in collaboration with Legendary Requirements and > Danube Tech are proposing a new CCG Work Item for adoption: > https://dcdpr.github.io/data-integrity-schnorr-secp256k1/ > > See the proposal issue here: > https://github.com/w3c-ccg/community/issues/254 > > We feel this is important as there are currently no up to date Data > Integrity cryptosuites available for the secp256k1 curve, which has wide > adoption throughout multiple blockchain ecosystems. > I do endorse this work item heartily, especially as FROST and MuSig require Schnorr. After a quick review of your draft, I suggest there needs to be some investigation on if a distinction between bip340-schnorr and the tweaked version (ie bip340-tr-schnorr) should be considered. Though tweaking (committing to a hash) is required for Bitcoin taproot, I have heard there are some other scenarios where tweaking may be required to prevent attacks, especially with bip32 derivatives. I’m not an expert on this topic, however. Thus I suggest you reach out to some cryptographers. — Christopher Allen >
Received on Thursday, 31 July 2025 16:49:51 UTC