... Helsinki MYDATA 2018 — August 29-31 Helsinki, Finland. #RebootingWebOfTrust VII — September 24-26th, Toronto. Also 27-28th DID/Verifiable Credential Hackathon (F2F). TPAC — October 23rd-26th, Lyon, France.
... IIW — October 23rd-25th, Mountain View
Kim Hamilton Duffy: Moses is organizing a conference. introduction forthcoming. ✪
Heather Vescent: If our social capital is being used to build the community, then we should have a sense of ownership. ✪
Moses Ma: Let's resolve this via a governance group ✪
Heather Vescent: If we're co-creating this, then we should have a commons-based ownership model ✪
Kim Hamilton Duffy: Jumping in: library of references that you're advocating looks useful to w3c-ccg as well ✪
Moses Ma: Entire library will remain open source ✪
Manu Sporny: I hear you Heather, and want to speak in support of Moses' efforts. it's working in concert with the multi-year efforts we've got going. we don't know of ways to build this without engaging with these business models. it's a balancing act. ✪
Heather Vescent: It's just very inconsistent what gets funded... technology gets funded, but other things do not. ✪
Manu Sporny: Maybe there's a CRT that gets created that can manage that list and its best use. unfortunately, we need to make these decisions rather quickly. everyone's participation is based on their own acceptance. ✪
Heather Vescent: It's a huge red flag. Moses is doing great work, but we need a way for people who don't fit this business model to see their work valued. i'm going to advocate for everyone in the community to get value out of the work they're putting in. ✪
Markus Sabadello: Q regarding DID resolution: would DID resolution be in scope for the WG charter? one spec or multiple? ✪
Manu Sporny: We could add it. we need to have this conversation. it needs a spec that has been incubated. expanding the scope may risk objections. the first WG charter draft is narrowed to data model and DID spec. ✪
Manu Sporny: If you and Dmitri can commit to the work to do the spec, then we can put it in there. ✪
Kim Hamilton Duffy: Create a spec that demonstrates how you express a JWK using a LD Cryptosuite. Create a spec that demonstrates how you express a Verifiable Credential as a JWT Implementations and test suites for those specs ✪
Andrew Hughes: The raw recording for the tutorial session by manu on setting up a github repo and also a respec doc is here: https://youtu.be/vcL3ffgGEJM✪
Christopher Allen: This is realted to uPort, so let's fold it into that. ✪
Pelle Brændgaard: You can add a signing key to it ✪
Pelle Brændgaard: Goals were: Ethereum compatible, does identities, simple to add, edit, and resolve. ✪
Pelle Brændgaard: This supports our did:uport method. ✪
Christian Lundkvist: A philosophy that we've come to is that unlike previous requirements to create an (expensive) blockchain transaction, our new thinking is that the hash of a public key is the identity, so that the supporting smart contract can handle key revocations. thus to onboard, you do not need any blockchain transactions. ✪
Christian Lundkvist: Further on in the lifecycle, you may beed to do a key revocation, and that is the point of the blockchain transaction ✪
Markus Sabadello: I was workign with the author fo the ERC725 proposal. what is the difference between your new proposal and that one. i guess not needing to create a new smart contract to create an identity is a big one. plus <lossage> ✪
Pelle Brændgaard: Yes, ERC725 requires posting a contract. and it doesn't rely on verifiable claims. ✪
Pelle Brændgaard: ERC780 would allow you to make lossage claims. ✪
Pelle Brændgaard: Service endpoints require the contract to be posted. ✪
Manu Sporny: Having read through things at a high level, parts look familiar and parts don't. ✪
Manu Sporny: DID spec outlines various steps to get something done. do you have a document with steps like that? ✪
Manu Sporny: I'm also seeing a lot of JWTs and i don't know where those are used. ✪
Christian Lundkvist: The way i see it is that the claims themselves are always stored offchain, using JWT (versus LDS) this DID method should be completely agnostic to that. you can imaging taking any form of data that references this and it should be able to be resolved (in an orthoganal manner) ✪
Christopher Allen: Will you be at the post RWOT hackathon? ✪
Bohdan Andriyiv: Can humans select the DIDs, and will they acquire vanity value? ✪
Pelle Brændgaard: We do "a lookup that isn't actually really a lookup" ✪
Pelle Brændgaard: First we check onchain for changes to the DID ✪
Pelle Brændgaard: If there are no changes, then the (hashed) address is the public key ✪
Pelle Brændgaard: This is the same trick that Ethereum uses for recoverable signatures -something- added height and recovery bytes. ✪
Music starts to play from Kulpreet Singh device when he accidentally mutes it. Cue Samantha Mathews Chase skillfully singing a sensational solo about DIDs over the hold music. Rumble of laughter ensues... ✪
Christian Lundkvist: If you anchor on two chains, that's not really supported. when you first create the identity, you need to go to a specific Ethereum contract as the refernece point, to look for updates. ✪
Christian Lundkvist: If no updates, you generate a DID Document directly from the public key. ✪
Christian Lundkvist: There's no way to senibly do this on multiple chains. ✪
Christian Lundkvist: And to the later question about someone else registering your DID, it's not a security risk because to use it, you will need to be able to sign with the private key. ✪
Markus Sabadello: When the DID document is created, will it contain public keys? ✪
Christian Lundkvist: One of the more interesting things is connecting Kerberos to Active Directory and then using PKI capability of Kerberos to sign with your DID. ✪
Kim Hamilton Duffy: Over time. see you next week ✪