- From: Charles E. Lehner <charles.lehner@spruceid.com>
- Date: Tue, 27 Apr 2021 10:14:22 -0400
- To: public-credentials@w3.org
There is an issue related to this here: https://github.com/w3c-ccg/did-method-key/issues/32 I believe the compressed and uncompressed form can be converted back and forth without loss of key information. Hopefully the specifications and implementations agree on which to support. Consistency with the other key types that support compression could also be nice. -- Charles On Tue, 27 Apr 2021 16:53:26 +1200 Kyle Den Hartog <kyle.denhartog@mattr.global> wrote: > It does matter for resolution, but I'm not sure if it was intentional. > Ideally, the folks working on multiformat would be defining how to > represent this as a part of their multikey work they've laid out and > did:key method would pick that up off the shelf. Unfortunately, that > work appears like it's stalled so far and so the examples become the > next best thing for knowing how other people are likely implementing > things. > > -Kyle > > On Tue, Apr 27, 2021 at 2:09 PM Brent Shambaugh > <brent.shambaugh@gmail.com> wrote: > > > I'm curious. > > > > In the did:key method spec, p-256, p-381, and p512 appear to be > > uncompressed. Does this matter or was this intentional? > > > > https://w3c-ccg.github.io/did-method-key/#p-256 > > > > -Brent Shambaugh > > > > GitHub: https://github.com/bshambaugh > > > > >
Received on Tuesday, 27 April 2021 14:14:39 UTC