Socialtoshi

Screenshots

Problem Statement

Imagine a platform where you can be free from bots spamming your inbox, or having to scroll through dozens of posts to find a real one. How is this possible?With verified DIDs on PolygonID when you create a profile on our platform you are entering an environment where everyone only gets one account, one identity. Verified profiles share accountability with the ecosystem. No more bots or ads. Those are the days of the past.Every "Claim" represents membership in a decentralized web of trust and is related to each member's identity through KYC. Socialtoshi community membership can belong to an organization, like a DAO, a club, or a shop loyalty membership. Each of these communities can utilize the Polygon KYC verification flow connected with the power of DIDs, claims, issuers, and verifiers.Socialtoshi enables users to build a reputation within their digital communities build on a trusted network of verified users. More trust is enabled through a decentralized reputation and only real connections are made.And with DID Auth integration (coming "soon"), users can utilize their existing decentralized identity to authenticate enabling interoperability with the ecosystem.Socialtoshi can restore the private keys of users who opt-into into key recovery services through the same KYC verification during the account creation. Users who lose their private keys can regain access to their DIDs and reputation.

Solution

We built this hackathon app on Flutter for easy future deployment to all devices (across the web, iOS, Android, and Desktop). We utilized FlutterFlow which is a fantastic low-code tool to quickly prototype for all devices. Since this will be on all devices we used Firebase/Firestore for our Database to allow direct data connection and reduce lag caused by API on mobile. In order to create a DID, we use Google Functions that call to our backend API which utilizes 'polygon-did-resolver' 0.0.10 and 'polygon-did-registrar' 0.0.11 to facilitate core PolygonID DID operations like creation and verification of DIDs. We trigger a call from the DB entry of a successful KYC instead of another API call, the goal was to hide the call from the front end completely. We hacked a fake KYC call because there is no Polygon KYC without integrating with a PolygonID wallet for authorizing a KYC Claim.We enjoyed creating a social network and a web of trust that would help reduce any non-human entities spamming the network with useless posts, a key loss disaster and recovery service, etc.