Identity Verification as optional “Add-on”
For several use cases, the integration of an external Identity Verification Service makes sense. Even though with Circles UBI, the main means of identifying users is by their social graph, this sometimes does not work well.
For example, a cloud service provider would have difficulties selling his services to unknown (not necessarily untrusted) users which are not in her local group or “few-hops” social graph network.
For these “B2B”-use-cases, other augmenting identity verification mechanisms add value. For more financial use cases, even KYC/AML might be necessary. So having pluggable Identity Verification Services makes sense for Circles.
Integration of Fractal Credentials
Fractal offers two kind of integrations:
- Fractal Wallet (Browser Extension)
- Fractal ID (OAuth2 Authorization Code Flow)
Fractal Wallet is a browser extension which is completely web3-compliant. The big advantage for Circles is that no server side processing is needed. The complete OAuth2 flow is executed on Fractal side, therefore only client-side integrations (web3.js/fractal.js) is necessary.
An obvious disadvantage is the dependency on a browser extension.
Fractal ID Authorization Code Grant Flow
For the Fractal ID Authorization Code Grant Flow, several components are involved. The communication sequence between the components is described here:
With this option, the user does not have to install a browser extension. However, the flow is more complex in implementation and a (centralized) server component is necessary, so clearly there is a trade-off.