[GP11-1] 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 period is 6 months with the following schedule:

• Month 1-2: Develop and test the applications for Windows, OSX, Linux, Android, and iOS.
• Month 3-4: Front-end development of the user "devices" section on the DeviceNFT website, and back-end development for the application interaction with the DeviceNFT API.
• Month 5: Submission of the application to the Google Play Store and Apple App Store. Integration and testing of the application with the DeviceNFT website.
• Month 6: Selection of a group of users from the DeviceNFT community for alpha testing, fixing potential errors, and the official launch of the production version.

As development and research progress, there may be necessary adjustments to the timeline. These will be communicated and justified accordingly to ensure that the project remains as transparent and accountable as possible.

The budget for the project is $20,000 worth of GAL tokens, distributed as follows:

• $10,000 will be provided at the beginning of the project to cover the cost of initial development, testing, debugging, and optimization of the application.
• The remaining $10,000 will be disbursed upon successful completion of the project, as demonstrated by the application's ability to meet the outlined success criteria and the successful launch of the application.

This budget will cover all costs associated with the project, including development, testing, debugging, optimization, and release of the application.

Upon the successful completion of development, the data generated by DeviceNFT will be offered to Galxe for utilization in their Sybil prevention measures. This contribution will be contingent on Galxe's formal acceptance and approval of the request, facilitating a cooperative effort to enhance security within the crypto ecosystem.

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.