🚧 This page includes experimental features which are unstable and subject to change. 🚧
EVM Identity Management
Within Web3, the most popular solution for authorizing specific users to access an application is the use of Non-Fungible Tokens (NFTs) on EVM-based blockchains. In effect, this is EVM-based identity management. To enable application developers to use Quible with their existing identity management solution, Quible supports relaying identity information across chains efficiently.
This is made possible by the use the Quible Relayer Network, a trust-minimized UTXO bridge which utilizes MPC to sign bridging transactions. This is similar in design to the Sygma Relayer.
┌──────────────────────────────────────────────────┐ │ │ │ │ │ Step 1 │ │ │ │ │ │ ┌────────┐ │ │ │ Author │ ┌─Quible──────────────────────────┐ │ │ └────────┘ │ │ │ │ │ │ ┌─────────────────────────────┐ │ │ │ └───────►│ │ Destination Identity Object │ │ │ │ │ └─────────────────────────────┘ │ │ │ │ │ │ │ └─────────────────────────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ Author creates an identity │ │ │ │ │ └──────────────────────────────────────────────────┘
┌───────────────────────────────────────────────────┐ │ │ │ │ │ Step 2 │ │ │ │ │ │ ┌────────┐ ┌─Quible──────────────────────────┐ │ │ │ Author │ │ │ │ │ └────────┘ │ ┌─────────────────────────────┐ │ │ │ │ │ │ Destination Identity Object │ │ │ │ │ │ └─────────────────────────────┘ │ │ │ │ │ │ │ │ │ │ ┌─────────────────────────┐ │ │ │ └───(@)────►│ │ Relayer Deposit Address │ │ │ │ │ └─────────────────────────┘ │ │ │ │ │ │ │ └─────────────────────────────────┘ │ │ │ │ │ │ ┌─Deposit────────────────────────────────┐ │ │ │ │ │ │ │ ┌───────┐ │ │ │ │ │ Value │ │ │ │ │ └───────┘ │ │ │ │ │ │ │ │ ┌─Inscription────────────────────────┐ │ │ │ (@) = │ │ ┌──────────────────────┐ │ │ │ │ │ │ │ NFT Contract Address │ │ │ │ │ │ │ └──────────────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ ┌────────────────────────────────┐ │ │ │ │ │ │ │ Destination Identity Object ID │ │ │ │ │ │ │ └────────────────────────────────┘ │ │ │ │ │ └────────────────────────────────────┘ │ │ │ │ │ │ │ └────────────────────────────────────────┘ │ │ │ │ │ │ Author submits deposit │ │ │ │ │ └───────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────┐ │ │ │ │ │ Step 3 │ │ │ │ │ │ ┌─Quible Relayer Network───────────┐ │ │ │ │ │ │ │ ┌──────┐ ┌──────┐ ┌──────┐ │ │ │ │ │ │───►│ │───►│ │ │ │ │ │ │ Node │ │ Node │ │ Node │ │ │ │ │ │ │◄───│ │◄───│ │ │ │ │ │ └──────┘ └──────┘ └──────┘ │ │ │ │ │ │ │ └──────────────────────────────────┘ │ │ ▲ │ │ │ │ │ ▼ │ │ ┌──────────────────────────┐ │ │ │ Third Party RPC Provider │ │ │ └──────────────────────────┘ │ │ ▲ │ │ │ │ │ ▼ │ │ ┌─EVM Blockchain───┐ │ │ │ │ │ │ │ ┌──────────────┐ │ │ │ │ │ NFT Contract │ │ │ │ │ └──────────────┘ │ │ │ │ │ │ │ └──────────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ Relayers subscribe to NFT Contract │ │ │ │ │ └──────────────────────────────────────────────────┘
┌──────────────────────────────────────────────────┐ │ │ │ │ │ Step 4 │ │ │ │ │ │ ┌─Quible Relayer Network───────────┐ │ │ │ │ │ │ │ ┌──────┐ ┌──────┐ ┌──────┐ │ │ │ │ │ │───►│ │───►│ │ │ │ │ │ │ Node │ │ Node │ │ Node │ │ │ │ │ │ │◄───│ │◄───│ │ │ │ │ │ └──────┘ └──────┘ └──────┘ │ │ │ │ │ │ │ └──────────────────────────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ ┌─Quible──────────────────────────┐ │ │ │ │ │ │ │ │ │ │ │ ┌─────────────────────────────┐ │ │ │ │ └────►│ │ Destination Identity Object │ │ │ │ │ │ └─────────────────────────────┘ │ │ │ │ │ │ │ │ │ │ ┌─────────────────────────┐ │ │ │ └─────────►│ │ Relayer Deposit Address │ │ │ │ │ └─────────────────────────┘ │ │ │ │ │ │ │ └─────────────────────────────────┘ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ Relayers spend deposited value to pay │ │ for updates to the destination identity. │ │ │ │ │ └──────────────────────────────────────────────────┘
How do NFTs become relayed?
To begin, authors transfer a supply of QBL to a transaction output that can be spent by the relayer rewards pool. This is effectively making a deposit with the relayer protocol. This transaction output can also be made spendable by the author, which allows the author to withdraw their QBL at any time in the future.
Inscribing NFT details
This transaction must be inscribed with the NFT details which include the network ID and the contract address of the NFT. This allows for relayers to know where to find your NFT-based identity information. Additional details include the object ID where the NFT’s claim data should be stored.
Relayer incentive
Once an author has deposited a supply of QBL and inscribed their NFT details, the relayer network can begin relaying identity information.
Each time the relayer network reaches consensus on a set of updates that need to be relayed, they perform a Multi-Party Computation to sign the transaction containing all of the updates and send it to Quible. From the deposits made by authors, the transaction siphons a small fee reward given to the each relayer node that participated in the MPC.
Continuous relaying
The Quible Relayer Network continuously processes each block from upstream EVM chains, and watches for changes made to the configured NFTs. This ensures that Quible stays up to date with any changes made to your NFT in real-time.