From what I gathered from your WP, you basically offered a platform where people can store their data, then use the platform to login, perform KYC/AML, and the likes of it?
We propose several distinct things that can be used synergistically.
An interoperable decentralized identifier that works within our ecosystem but that can be used on other systems because of its generic syntax (w3c standard). This DID can (not necessarily) be verified by KYC and thus ensure the authenticity of the users' identity if they wish to share information about themselves, this will be particularly useful in dating or social platforms and more...
A decentralized app platform automated by Smart Contract using our DID to ensure the protection of user data. This app store will bypass Google and Apple.
A modular decentralized app (ONE) on which any exterior actor will be able to build an extension of its current service while benefiting from our decentralized identifier.
The whole will work in synergy.
I'd like to highlight DID for KYC first. Is there any plan (and how will it be implemented) to integrate this feature with crypto projects in general? I'm talking about mandatory ICO, exchanges' withdrawal, and things alike. Can we integrate your platform to another platform although they have no record of partnership with you?
For instance, let's say I'm on ABC exchange and I'm required to do KYC. However, I'm reluctant to share my ID to ABC, given it is a new and questionable exchange. And it is known that ABC has no prior partnership with you. Is it possible that (perhaps in the future, with your platform so much advanced and developed) we just upload a certification from you on ABC's selfie or gov ID field to bypass the KYC? In other words, instead of giving our ID details to ABC, we just share a certification from you (or perhaps a link) and ABC will acknowledge it as a legal verification
The main objective is to have a DID that is interoperable with various systems even if they are not from our ecosystem directly.
If a service provider wishes to use our DID without having a dApp in our ecosystem, they will be able to do so, but they will simply not be referenced on our platform and will not benefit from our visibility and grants.
The platform will also be an automated hub allowing the creation of a multitude of services using the DID. There will be collective participation in the development of various use cases and dApps.
Let's take the example of an exchange that doesn't want to make a KYC of their customer, this exchange could very well require a DID badged KYC to access there services, in which case you could (with your DID) have access to it.
One possibility would be (in case of massive use of our technology) that you don't need to pass a KYC on several platforms but only once at the moment of the creation of the DID, and then use it on various platforms. From a legal point of view, a lot of things still need to be put in place to make sure that this will work everywhere, but this is under discussion with several actors.
Concerning ONE, it will be a user-friendly tool allowing the « centralization » of the different services you use with your SDI (in case they have developed an extension). ONE will also allow you to set up your DID and manage who has the right or not to access your personal informations, this include entities which are not part of the SYL ecosystem.
For more informations, I advise you to read the comprehensive WP
Show Posts
