Using WebSocket as a way to communicate back to the mobile/desktop wallet (Agent (services or user) as a proxy for communication between service and digital wallet - Robert Mitwicki
Aries Toolbox the vision and plans for the future - open discussion
Other businesses
Note: This call is Recorded. Recordings posted at the bottom of the page.
Date
(7AM Los Angeles, 10AM New York, 3PM London, 4PM CET, 18H Moscow)
Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws.
Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.
Attendees
Name (Organization) <email>
Robert Mitwicki Robert Mitwicki(The Human Colossus Foundation)
Chained credential solves the delegation problem but that is not the only one
There is no specific requirements to change anything in the VC spec at all. is just about adopting convection
VC are head for a problem - same problem as the certificate authorities at the beginning of the web, this what we are trying to avoid is to keep the list of all trusted parties. Instead of small list of entities to trust and cover whole space.
If everyone can be issuers, the problem appears how to keep truck who I can trust.
Data provenance → side the sources into VC
We need clever way to do the revocation (wip)
logic in verifier code is needed to support chained credentials
how nonce is used in embedded proofs:
verifier checks old nonce to verifiy that this happened in the past
Does I have to disclose privacy by just letting someone walk up the history upstream of the credentials?:
ZKP veriants and their privacy implications
Cross correlation through multiple use - offline
Anonymous of the entities in the chain can be achieved.
Late and strong anonymity - is up to the case
Aries toolbox
base Intention: "Postman" for Agent - to help developers to develop agents.
Development tool
Administrator tool - to control the agent
Demo purposes
UI module - corresponds to one or more protocols in the backend
Discussion will be continued on the Call B .
RFC Progress
Other Business
Future Topics
Next Meeting
Other:
Where should we document interoperability results (AIP 1.0)? A page in this wiki space?