Guild network identity service

[PopcornPaws]

Description

In order to link web2 identities (discord, telegram, twitter, etc.) to the primary crypto identity (i.e. address) we need an off-chain service similar to Polkadot's registrar challenger. It should be listening to on-chain events and generate challenge hashes for users that wish to link a web2 identity to their account. These hashes can be queried from the UI and the user has to submit this hash via a DM to our respective bot on a given platform. This bot caches and sends the incoming DMs to the identity service via a REST api. Once the identity service received the necessary data from the bots it compares the hash with the challenge hash and dispatches a confirmation transaction on-chain if it matches.

Solution

We have two main options to tackle this. The first is to try and reuse Polkadot's registrar challenger, add our own telegram + discord connectors. However, there are a few issues here:

• it seems that adding a new identity type would require lots of changes throughout the code (lib.rs, primitives.rs, adapters, etc.)
• would be nice if adding new identity types was more modular that doesn't require any change from the main service
• we could probably implement this without websockets (only a subxt api is needed that we already have)

The other option is that we write our own service

• that's modular (new bots, email clients, etc. can be added/removed on-the-fly)
• doesn't need a watcher because a subxt client is integrated for network interaction
• not sending judgements, just verifies that an identity can be linked