- From: Brian Richter <brian@aviary.tech>
- Date: Wed, 3 May 2023 00:50:54 -0700
- To: Manu Sporny <msporny@digitalbazaar.com>
- Cc: Gabe Cohen <gabe@tbd.email>, "W3C Credentials CG (Public List)" <public-credentials@w3.org>
- Message-ID: <CAPUZd8uHxDy9Lr5z9C09G=iuEh35ydeY83AK5UUksJpyRit2Kw@mail.gmail.com>
hmm nevermind I guess finder was giving me the wrong bytes.. Looks like the bespoke solution is still going to win by a large margin. If anyone has any other ideas on how to compress a fully expressive DID Document I'm all ears.. Right now I'm using the same technique as did:peer numalgo 2. Sorry for the list spam everyone.. I'll try to keep my technical discussions to a minimum Brian On Wed, May 3, 2023 at 12:22 AM Brian Richter <brian@aviary.tech> wrote: > Manu, I know you can comment on some of the technical details 😁 > I just used CBOR-LD to compress the short form instead of something more > bespoke and cut it down a further 60% in on chain bytes. > > Brian > > On Tue, May 2, 2023 at 6:58 AM Manu Sporny <msporny@digitalbazaar.com> > wrote: > >> On Mon, May 1, 2023 at 6:16 PM Brian Richter <brian@aviary.tech> wrote: >> > Yes, we agree Bitcoin as it is currently architected will never support >> billions of users on layer 1 however the bet I'm making is that there will >> be users willing to pay a premium to get their keys and services endpoints >> embedded on layer 1. >> >> To pile on to the thread, diversity in the DID Method ecosystem is a >> goal. All DID Methods make trade-offs, and as long as the DID Method >> is up-front about the tradeoffs it is making, then that's what >> matters, IMHO. >> >> While I can't comment on the technical mechanism used in depth, it >> sounds like a perfectly reasonable way to approach the problem if you >> want to use Bitcoin and don't want to depend on a Layer 2 network. >> >> -- manu >> >> -- >> Manu Sporny - https://www.linkedin.com/in/manusporny/ >> Founder/CEO - Digital Bazaar, Inc. >> https://www.digitalbazaar.com/ >> >
Received on Wednesday, 3 May 2023 07:51:10 UTC