TrustedWeb

Trusted Web's Github pageTrusted Web's YouTube pageTrusted Web's Twitter page
/
Trusted Web's Github pageTrusted Web's YouTube pageTrusted Web's Twitter page
/
お知らせ

Wallet-based identity management and online communication

2024/06/10Use Cases
Wallet-based identity management and online communication

This page shows the "Wallet-based identity management and online communication" exploried and tested by DataSign Inc., in the 2023 "Use Case Demonstration Project of the Trusted Web".

Please click on the links at the bottom of this page to learn more about the details of the demonstration.

Current issues and What Trusted Web Solves

 Current Issues (Pain Points)

  • Consumer 1 finds it helpful to use the login function of the social service (IdP) but does not want to give attribute information managed by the IdP to unfamiliar service providers.
  • When consumer 1 tries to send a message using a specific social service, consumer 2 (friend or business partner) must also be using that specific social service to send the message. Email is not secure because the sender cannot be verified.
  • Service providers want to confirm and verify the attributes of consumers, but identity verification is high cost and inhibits consumers' UX.
  • Service providers want to provide consumers with an easy way to sign up for services, but supporting multiple social services would adversely impact the UX.

 

 

What Trusted Web Will Solve

  • Consumer 1 can send the minimum attributes to service providers and consumer 2 at his/her own choice, without depending on specific provider.
  • Consumer 1 can verify attributes with consumer 2 or service provider mutually and can communicate securely online within the agreed scope, without depending on specific provider.
  • Consumer 2 can also do the same as the above two cases of consumers 1.
  • Service provider can easily verify and confirm the attributes and provide appropriate services without depending on specific provider.


 

Data to be verified


 

UI/UX

  • How to achieve user-friendly UI/UX in wallet and messaging service?

 

Privacy

  • What technologies should be selected for privacy by design?

 

Community

  • What kind of community should be created to spread the proposed architecture?

 

Governance

  • What governance and rules are essential?

 

Main Achievements

  • UI/UX design and research for the wallet and messaging service were conducted under the supervision of the designers, and we verified that the UI/UX is user-friendly and released publicly available Figma UI component files.
  • We developed the wallet and messaging service using global standard technologies that are expected to be widely used in the future and selected the technologies to be used based on the advice of experts regarding selective disclosure, anonymity, and external dependence for privacy by design.
  • We established an open-source community called OWND Project (https://github.com/OWND-Project/) for continuing operation and promotion the developed wallet and messaging service.
  • We developed a governance model for the wallet and messaging service within the OWND Project community and published it as a white paper to enable governance of future products using the OWND Project open-source software.

 

Documents

To communicate with Trusted Web stakeholders,
please use the contact form.

Inquiry Notes

Thank you for contacting Trusted Web Promotion Council HP website.
In order to properly process your opinions and comments, please follow the format below.
*Notes and description examples can be deleted when sending.

<Email Subject>
Regarding the content of the inquiry, please write a concise entry in the subject line so that the source of the inquiry and the type of inquiry can be identified at a glance.
example)
【●●Co., Ltd.】Request for participation in the discussion community of Trusted Web
【●●Co., Ltd.】Privacy Policy Questions

<Type of inquiry>
Please select the type of inquiry from the following.
1. Request to participate in community on Trusted Web GitHub
2. Opinions and comments regarding the structure of the website and the contents of the content
3. Other opinions and comments

<Inquiry contents>
1. Request to participate in community on Trusted Web GitHub
・Please fill in the name of the organization you wish to participate in, the name of the individual, the e-mail address that can be contacted, and the Github account.
Example) ●● company, name, e-mail address (for the number of people who wish to participate), Github account
・Please write in detail about the content of the discussion you would like to participate in and the points you would like to contribute.
Please note that there is a possibility that you will not be able to participate in the community based on your desired content, contribution content, experience, etc.
Example) We are developing ~~ systems in-house. We are trying to solve XXX, which was an issue in the use case demonstration in FY2022, and we will have trusted web experts take a look at it and point it out, make improvements as necessary, and contribute to the realization of the trusted web. would like to participate in

2. Opinions and comments on the website structure and contents
・Please specify the target HP page / content name and fill it in.
Example) Regarding ●● on the use case page, the description is "●●", but is it ●●?

3. Other opinions and comments
・Please fill in the details of your inquiry.

Inquiry