[GP11] DeviceNFT: A Unique Approach to Crypto Security and Uniqueness

Author: alexkat

Goal:

Our main aim is to discourage multi-accounting and enhance the uniqueness and security of user interactions across the crypto space. We aim to do this through the development of a distinctive device identification application and an NFT minting system.

Abstract:

Development of a cross-platform user application for automating the process of device identification and NFT minting. The application will collect certain device parameters, generate a unique hash, and trigger the creation of a unique NFT, which will be stored in the user’s EVM-compatible wallet.

Motivation:

The proposed device identification application and NFT minting system can greatly increase the security and uniqueness of user interactions throughout the crypto ecosystem. By discouraging multi-accounting, we can provide a fairer and more balanced environment for all users. In addition, by associating each device with a unique NFT, we can create a unique digital asset for each user that can be traded or sold, adding an extra layer of functionality and value to the user experience.

Details:

Our proposed project involves the development of a cross-platform application that streamlines the process of user device identification and NFT minting. The application will collect certain device parameters, produce a unique hash, and initiate the creation of a unique NFT, which will then be stored in the user's EVM compatible wallet.

Scope:

The project includes the creation of a unique open source device identification application written in C++ (for Windows, OSX, Linux), Java (for Android) and Swift (for iOS). Web interface on React, Backend Nodejs.

Success Criteria:

Successful collection of specific device parameters and generation of a unique hash by the application. Successful triggering of a unique NFT creation based on the generated hash. Prevention of re-binding a device that already has an associated NFT.

Timeline & Budget:

The proposed project development timeline is six months with the following schedule:

Month 1: Development and testing of a Windows application. Month 2: Development and testing of applications for OSX and Linux. Month 3: Development and testing of an Android application. Month 4: Development and testing of an iOS application. Month 5: Submission of the applications to the Play Market and Apple Store. Month 6: Selection of a group of users from the community for alpha testing, fixing possible bugs, and launching the production version. The project budget is set at $36,000 ($6,000 monthly) in GAL tokens to cover the costs of developing, testing, optimizing, and releasing the application.

Web Interface Description:

The DeviceNFT web interface will have a user-friendly and intuitive layout that ensures a seamless interaction between users and the platform. The interface will be based on the "Devices" section, designed in the form of a passport. This section will host a catalog of released NFTs (ERC721) associated with devices. It will also provide links to download the device identification app. Once the app is launched, users will be able to enter the wallet address they wish to link to their device and activate the sync button. This action will cause the program to send the hashed device ID data to the DeviceNFT API. Users can then return to the device page on the DeviceNFT website to confirm their request. Once the request is approved, an NFT mint request will be initiated and the new associated device will appear in the list of user devices. To improve the user experience, the web interface will also support the concept of adding multiple accounts (wallets) to a single device, which will be covered in a separate proposal. The design will prioritize ease of use, clarity, and appealing aesthetics, delivering a fluid and engaging user experience.

Conclusion:

Our proposed application will automate the process of device identification and NFT creation, enhancing the user experience and making it easier for users to interact with the Web3 credential framework. By discouraging multi-accounting, the application will improve the uniqueness and security of user interactions and allow for more flexibility in transferring device ownership throughout the crypto space. The author of this proposal will oversee development and testing of the application.