Skip to main content

User Guide

The WIDE digital identity bridge enables users to export identity data from wallets of closed identity networks and use the identity data with their Ethereum-compliant key pairs throughout full identity lifecycles. All data is protected through client-side encryption and presented to relying parties by the wallet user. In short, WIDE provides export, persistance, as well as encryption -, storage -, and presentation capabilities for long-lived any-wise identifiers in storage-scarce Web3 wallets.

In this context, bridging refers to the privacy preserving, but server-based remote storage of encrypted claim and the assured availability for identity presentations by holders on demand over Web2 flows. When the wallet presents claims, it requests them from the WIDE bridging server. The wallet then acts as a proxy, waits for the WIDE server to return data, the wallet then decrypts the data and forwards it to the relying party. The relying party can verify that a dataset was hashed upon upload to the WIDE bridging server and did not change.

For this reason, WIDE logs entries over record uploads on Optimism to enable trust assertions of verifiers (relying parties), because WIDE cannot attest to the validity or correctness of the data. Thus, bridging means that WIDE only attests to having seen a random but unique string at a given time from a specific address that signed the data.

Its strength, however, is that WIDE covers the gap of Web3-based Web2-logins. There are many solutions that allow Web2 onboarding to Web3, but only few have used Web3 technologies for Web2 authentication flows. For this reason, WIDE reverse implements Web2 to Web3 onboarding solutions in dataflows optimised for verifiers.

When a user requests the data from WIDE, assuming online-only use cases, the user authenticates using Log-in-with-Ethereum and requests structured, but encrypted claims. They then decrypt it on client side and act first as identity subject against a relying party to then return the requested information by the identity provider through acting as an identity provider.

Features​

  1. UI-based data export
  2. Privacy-preserving cloud storage
  3. Web3-based open authentication
  4. Simple data sharing
  5. Reliable identity storage
  6. Native EVM-support
  7. Portable and trustworthy data attestations
  8. Simple UI-based identity card management