Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

5.1 Use Cases That Do Not Involve Verifiable Credentials #19

Open
martchcl opened this issue Aug 30, 2022 · 1 comment
Open

5.1 Use Cases That Do Not Involve Verifiable Credentials #19

martchcl opened this issue Aug 30, 2022 · 1 comment
Assignees
Labels
priority: medium This issue is important to resolve before the next release. type: editorial The issue only involves wording and not normative content.

Comments

@martchcl
Copy link
Contributor

martchcl commented Aug 30, 2022

[Metaverse use case] | identifying authentic avatars/ preventing deep fakes (image, audio, voice)?]

Drummond Reed
01:50 25 Aug
@[email protected] @[email protected] Please add at least one AI/metaverse use case that is NOT verifiable credentials.

@talltree talltree added priority: medium This issue is important to resolve before the next release. type: editorial The issue only involves wording and not normative content. labels Oct 17, 2022
@a-fox
Copy link
Contributor

a-fox commented Oct 26, 2022

Would something like this work:

User-controlled secure interactions
End-users in physical world and digital world (social media & metaverse) are naturally drawn to create new connections with each other. Today it's mainly human-to-human, but in the near future we're going to see more of human-to-AI, human-to-machine -type of interactions. All of these different types require standard interfaces. These interfaces are used to facilitate various interactions, such as secure chatting, payments, authentication. Each of these services already exist as digital services today, but all of them also require their own service providers and applications. Using ToIP, the siloed and individually formed service interactions can be managed through a single interface and controlled by the end-user. The connection is controlled and maintained jointly by both parties, and trust is based on the verifiable DID-based connection.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: medium This issue is important to resolve before the next release. type: editorial The issue only involves wording and not normative content.
Projects
None yet
Development

No branches or pull requests

4 participants