🛂Meta ID

Meta ID is an identity system that offers both wallet and identity authentication functionalities. Through Meta ID, users can easily manage their digital assets, including cryptocurrencies and non-fungible tokens (NFTs), while also being able to verify their identity for various online services. As the unique identifier for registered users on GasZero, Meta ID serves both users and third-party dApp developers, aiming to establish a trusted and secure relationship between users and dApps, following the principles of self-sovereign identity and default privacy. The platform provides a comprehensive and user-friendly interface experience, ensuring that users can confidently and conveniently access their accounts and perform transactions through secure authentication processes. Whether you are a developer looking to integrate MetaID into your application or a user seeking a reliable identity and wallet solution, MetaID is your best choice.

How to integrate Meta ID into your dApps:

1. Create a Meta ID: Visit the website https://metaid-sandbox.gaszero.com/. Follow the instructions provided on the website to create a Meta ID. This will involve generating a cryptographic identity that you can use to interact with the Meta ID system.

2. Create an application: Access the Meta ID portal or developer console.

3. Obtain access key and secret: After creating the application, you should receive an access key and secret. These credentials are used to authenticate your application when making requests to the Meta ID system. Keep the access key and secret secure as they grant permissions for your application to interact with the Meta ID system.

4. Follow the integration documentation: Consult the official documentation or developer guide provided by Meta ID platform. These resources will provide detailed information on how to integrate your dApp with Meta ID. The documentation should outline the necessary steps, API endpoints, and authentication mechanisms for interacting with the MetaID system.

5. Implement the integration: Based on the documentation, incorporate the required functionality into the codebase of your dApp. This may involve making API calls to the Meta ID system, handling responses, and managing user interactions related to Meta ID functionality.

6. Test and iterate: Thoroughly test your integration to ensure it works as expected. If you encounter any issues or have specific requirements, refer to the documentation or developer support channels provided by Meta ID for assistance.

Remember to refer to the official documentation and resources provided by Meta ID for the latest and most accurate information on integrating with their platform.

OAuth workflow

       +-------------------+                              +-------------------+
       |                   |                              |                   |
       |   Client (Your    |                              |    MetaID         |
       |   Application)    |                              |   Authorization   |
       |                   |                              |    Server         |
       +-------------------+                              +-------------------+
                |                                                  |
        1.  Register                                               |
                |                                                  |
                +------------------------(A)---------------------->|
                |                Client Registration               |
                |              (Client ID, Client Secret)          |
                |                                                  |
        2.  Redirect User                                          |
                |                                                  |
                <------------------------(B)-----------------------+
                |              Authorization Request               |
                |           (Client ID, Redirect URI, Scope)       |
                |                                                  |
        3.  User Consents                                          |
                |                                                  |
                +------------------------(C)---------------------->|
                |                  User Consent                    |
                |                                                  |
        4.  Authorization Code                                     |
                |                                                  |
                <------------------------(D)-----------------------+
                |                Authorization Grant               |
                |               (Authorization Code)               |
                |                                                  |
        5.  Request Access Token                                   |
                |                                                  |
                +------------------------(E)---------------------->|
                |               Token Request                      |
                |     (Client ID, Client Secret,                   |
                |      Redirect URI, Authorization Code)           |
                |                                                  |
        6.  Access Token                                           |
                |                                                  |
                <------------------------(F)-----------------------+
                |              Access Token Issuance               |
                |              (Access Token, Token Type,          |
                |               Expiration Time, Scope)            |
                |                                                  |
        7.  Access Protected Resource                              |
                |                                                  |
                +------------------------(G)---------------------->|
                |               API Request                        |
                |        (Access Token, Protected Resource)        |
                |                                                  |
        8.  Refresh Token (optional)                               |
                |                                                  |
                <------------------------(H)-----------------------+
                |               Token Refresh                      |
                |           (Refresh Token, Client ID,             |
                |            Client Secret)                        |
                |                                                  |
                +------------------------(E)---------------------->|
                |               Token Request                      |
                |     (Client ID, Client Secret,                   |
                |      Redirect URI, Refresh Token)                |
                |                                                  |