Skip to main content

Uniscan NFT Explorer

  • Team Name: Uniscan
  • Payment Address: 0x480821a0700b0d5fBC722a5339ED2d49979Eaa42 (DAI)

Project Overview 📄​

Overview​

Uniscan NFT Explorer wants to be the best place to analyze, track and discover NFTs.

Uniscan NFT Explorer hopes to create a unified NFT dedicated explorer for the Polkadot / Kusama ecology. It can be used to discover and view the NFTs in important parachains in the Polkadot / Kusama ecology.

The vision of this explorer is to become a better platform for discovering and analyzing NFTs. In the future, we can provide more tools for discovering and analyzing NFTs, such as combining on-chain data and off-chain data to provide users with some statistical views.

We hope that through this grant, we can better understand NFT and lay a foundation for the realization of this vision. This grant is the first step of this vision, that is to achieve a basic browser structure and functions, and only focus on evm. Through this grant, we hope to

  1. establish a reliable technology architecture.
  2. choose the best technology stacks.
  3. better understand nft, and improve the data model,
  4. implement a better style suitable for NFT display.

Project Details​

Architecture​

This is a standard web program, the main structure includes three layers.

The first layer is the Web server, which is responsible for rendering browser pages, showing NFTs to users, and providing some interactive functions.

The second layer is the database layer. A data model is used in the database to store all NFTs data, and the Web server will query the data from the database.

The third layer is the data query layer connected to blockchains. In this layer, there will be a number of long-running workers. These workers will monitor or poll blockchains to discover NFTs, and then combine these NFTs with their related data into the database, and the push service will also be notified to push the latest data to the browser. In addition to obtaining data through blockchains, this layer may also grab data from some centralized or decentralized services, such as grabbing transaction data from Markets, etc. This part is not in the scope of this grant.

This grant application only focuses on the NFTs on the evm-compatible virtual machine in the Polkadot ecosystem, and only monitors and saves the ERC721 and ERC1155 compatible NFTs. And only considers connecting two substrate based blockchains.

In the future, we will apply for other grants based on the completion of this grant, including more chains, support for wasm based NFTs, and support for more types of NFTs, such as RMRK.

Mockups​

nftexplorer

Data models​

collections​
  • id: The collection's unique identifier
  • name: The collection's name
  • symbol: An abbreviated name of this NFT. null if it is an erc1155 collection.
  • blockchain_id: Blockchain id
  • contract_platform: Only support EVM compatible now, wasm will be supported
  • contract_address: Contract address
  • type: erc721 compatible | erc1155 compatible
  • total_supply: A count of tokens tracked by this NFT
  • explorer_url: A subscan(or other explorers) url to show its the normal info
  • holders: Number of holders
  • transfers: Number of transfers
  • creator: The creator's address id
tokens​
  • id: The token unique identifier in the system
  • id_in_contract: Token id or token type id(erc1155) in its nft contracts
  • collection_id: the NFT id to which this token belongs
  • unique: true | false, true if it is an erc721 compatible token, false if it is an erc1155 compatible token
  • supply: 1 if erc721
  • creator: The creator's address id
  • owner: The current owner‘s address id
  • title: Short title of this token
  • name: The name of this token
  • description: Describe the token
  • image: A URI pointing to a resource with mime-type image/*
  • metadata_uri: A distinct Uniform Resource Identifier (URI) for a given token
  • is_permanent: bool, a flag to show is this token has a permanent resource
  • explorer_url: A subscan(or other explorers) url to show its the normal info
  • transfers: Number of transfers
addresses​
  • id: The address unique identifier
  • blockchain_id: Blockchain id
  • important_level:
blockchains​
  • id: The blockchain unique identifier
  • title: Short title of this blockchain
  • description: Describe the blockchain
transfers​

if it is an erc1155 batch transfer, it will be split into many rows here.

  • collection_id: the collection id
  • token_id: the token id
  • value: used if it is an erc1155 transfer
  • from: from address
  • to: to address
  • created_at: Time when the transfer occurred
  • txhash: txhash

Apis​

Web APIs​

Because we don't want to make this application separate from the frontend and backend, there may be no well-defined APIs. Here are some APIs:

  • GET /tokens/latest

    Get the latest created NFT list

  • GET /transfers/latest

    Get the latest transfers

  • GET /tokens/highest_transfered/1

  • GET /tokens/highest_transfered/7

  • GET /tokens

    List all NFT tokens by condition

    params:

    • sort by:
    • type:
    • chain:
    • page

  • GET /tokens/:id

    Get token detail by id

  • GET /collections

    List all NFT collections by condition

    params:

    • sort by:
    • type:
    • chain:
    • page

  • GET /collections/:id/tokens

    Get the tokens of a collection

  • GET /addresses/:address

    Get the collections with tokens that belong to the address

    [
     {
      "collection_id": 1,
        "collection_name": "...",
      "tokens": [
       {
        "token_id": 2,
        "token_title": "...",
        ...
       },
       ...
      ]
     },
     ...
    ]

Technology stack​

frontend​
backend​

Ecosystem Fit​

We believe that there will be various NFTs in the Polkadot / Kusama ecosystem in the future, so a unified nft explorer must be very important. Now many parachains will support the creation of NFTs. Users interested in NFTs will want to have a unified entry to view these NFTs.

We found that there is no unified and easy-to-use NFT browser in the current Polkadot ecosystem.

Potential users of the NFT browser include NFT collectors, NFT creators, NFT speculators and other applications.

Similar projects​

https://nft.kodadot.xyz/rmrk/gallery

Kodadot gallery is a rmrk nfts gallery.

The difference between us is that the purpose and direction. Kodadot gallery is a part of the RMRK. Uniscan's current goal is to support NFTs of evm pallet. The Uniscan's final goal is to build an all-in-one NFT explorer for Polkadot & Kusama ecosystem with some data statistics for users to easily discover NFTs.

Why evm?​

  1. Evm is the most widely adopted virtual machine platform in the Polkadot/Kusama ecosystem, so there will be a lot of NFTs to be issued based on evm pallet.
  2. There is not an NFT explorer support evm in the Polkadot/Kusama ecosystem.
  3. It is difficult for the NFT explorers of the Ethereum ecosystem to cover the chains in the Polkadot ecosystem. And they are not permissionless.

Team 👥​

Team members​

  • Kyle Gu: product manager
  • Tuminfei: architecture and blockchain consultant
  • Aki Wu: full-stack developer

Contact​

  • Registered Address: 3 FRASER STREET #05-25 DUO TOWER SINGAPORE (189352)
  • Registered Legal Entity: UNI-ARTS FOUNDATION LTD.

Team's experience​

Uniscan is a team dedicated to create an unified NFT explorer. We have the ability to develop web, mobile, and blockchain applications. The team is familiar with Ethereum and Substrate development.

Aki Wu has many years of web and blockchain development experience, and is proficient in web development, and is familiar with ruby and rust languages. When working at Itering, he developed scale.rb, a Scale Codec library and Substrate Client implemented in Ruby language. scale.rb is a grant of the Web3 Foundation.

Kyle Gu is the product manager of Uniscan team. He has worked in the blockchain industry for many years and is familiar with the operation and development of blockchain projects.

Tuminfei is the architecture and blockchain consultant of Uniscan team. He has rich experience in the field of software development, especially in blockchain. He has implemented many projects as a leader. He is familiar with the development of Ethereum and Substrate. He is also a major maintainer of the UniArts chain.

Team Code Repos​

Development Status 📖​

Development Roadmap 🔩​

Overview​

  • Total Estimated Duration: 2.5 months
  • Full-Time Equivalent (FTE): 2 FTE
  • Total Costs: 16,000 USD

Milestone 1 — common components​

  • Estimated duration: 1 month
  • FTE: 2
  • Costs: 8,000 USD
NumberDeliverableSpecification
0a.LicenseMIT
0b.DocumentationWe will provide both inline documentation of the code and a basic tutorial that run the code, which will show how the new functionality works.
0c.Testing GuideCore functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.
0d.DockerWe will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone.
0e.Article
1.A evm log tracking lib using ethereum filterIt is a lib used to track event logs of certain addresses and topics.
It use ethereum compatible json-rpc apis(eth_newfilter, eth_getlogs) to track the logs.
It will be used to track the substrate ERC721 and ERC1155 NFTs.
It will be implemented in rust programming language.
2.A evm log tracking lib using substrate eventIt is a lib used to track event logs of certain addresses and topics.
It use substrate events(getStorage) to track the logs.
It will be used to track substrate ERC721 and ERC1155 NFTs.
It will be implemented in ruby programming language.
3.A lib to identify the NFTsThis lib is used by the above tracking lib to identify which contracts are NFT contracts(ERC721, ERC1155). ERC-165 Standard Interface Detection is used.
It will be implemented in ruby programming language.

Milestone 2 — Web server​

  • Estimated Duration: 1.5 month
  • FTE: 2
  • Costs: 8,000 USD
NumberDeliverableSpecification
0a.LicenseMIT
0b.Documentation1. We will provide both inline documentation of the code.
0c.Testing GuideCore functions will be fully covered by unit tests to ensure functionality and robustness. In the guide, we will describe how to run these tests.
0d.DockerWe will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone.
And, It will be used to run the server.
0e.ArticleWe will publish an medium english article that explains what was done as part of the grant and how to use it( How to use the three libraries in Milestone1, the description of the models in Milestone2).
1.ModelsImplement the models described in models.
It will be implemented in ruby programming language.
2.Views and ControllersImplement the views and the related controllers described in mockups and apis.
It will be implemented in ruby programming language.

Future Plans​

  • Strengthen the display effect on the small screen
  • Support the NFTs of Statemine
  • Support more evm based chain
  • Support wasm based NFTs
  • Support more NFT types or specifications, such as RMRK
  • Market data & view
  • Record important addresses and level them
  • Statistic chart, such as transfer frequency statistic
  • Signup & Signin. The use can add nfts to the favorites.