Use cases

Problems

Suri's proposal resides in solving the following problems:

  • Multiple digital identities: every person has its digital identity split in several parts, one for each application they sign on, so there're no opportunities for interoperability between parties. On the other side, companies do not have a single location where people can search for their information, website, social network, etc.

  • Multiple signup methods: people need to sign up in almost every app they want to use, following the same process repeatedly and probably giving personal information to those apps.

  • Personal data protection: companies that require users need to store users' personal information in a secured way to accomplish with laws like GDPR. This increase costs and distracts entrepreneurs from the main goal of their businesses.

Solutions

The solution that Suri offers to solve all those problems is the infrastructure of SUNS. With SUNS, users can:

  • Have a single digital identity: suris can store any kind of information, public or private. This make suris the perfect self-governed identity provider. Moreover, using suris with the most recent cryptographic technologies like ZK-proofs, users have the ability to give third-parties verification on their data without even sharing it.

  • Global social information: because the identity resides in the suri and apps subscribe to it, just by updating their suris, users can update their social media identity all at once in every platform.

  • Move funds in a traceable way: all movements inside suri can be traced in order to obtain a list of transactions that can be useful to pay taxes or any other financial-related process.

  • Make agreements: users can establish agreements with other suris (parties). The underlying blockchain technology serves to proof the agreement is correct, that both parties have agreed to the terms and the timestamps of every interaction with it. This proofs can serve in judicial processes replacing expensive notarial costs.

Companies have those and also can benefit from:

  • Deploy and develop a brand: users will be able to use locate companies' information right in their suri, which actually can be exactly their name, so users won't confuse remembering different names for the URL or whether it ended by .com, .org or any other.

  • Empashise the brand: suris are written from left to right, starting the top level first. This means to access any sub-suri, let's say a specific resource in a company ecosystem, like the documentation, user will first write the company's suri, then the sub-suri, emphasizing first the brand it belongs to. For example: if the suri is my_company, the docs section would be: my_company.docs

  • Service load balancer: thanks to the built-in support for balancing algorithms, companies can set up different servers behind a suri instead of paying expensive services to accomplish that task.

  • Serve multiple websites on the same machine: currently we need to use reverse proxies to serve multiple websites on the same machine. With the SUNS Program this will be possible without the need of a reverse proxy.

    Insight

    This feature will not be limited to websites but will be working for any protocol/service.

  • Do not depend on federated authorisation: instead of relying on third-parties like Google or Facebook to provide companies with users' information, they can just verify the ownership of a suri and get the information from it.

  • Deploy different payment models: companies can deploy different payment models like subscriptions or on-demand payments, so they can focus on their business instead of integrating complex payment gateways.

  • Almost-free payment gateway: companies that require payments inside their platform usually pay a % of each transaction to the gateways. Suri does not charge anything but a negligible fee to make them automatic. At the time of writing, the fee is approximately 0.000005 SOL + TX costs ~= 0.00033 USD per update.

Last updated