The glamour of Web3 lies in the fact that the data belong to the users themselves, but it is extremely difficult to access and display their own or user Web3 data due to the inefficiency and design of the block chain and the lack of data format standards. So I did open-source project [Unidata] (https://unidata.app/) to provide easy access to Web3 data that are human friendly to Web3 developers.
The Etheum NFT data is currently the most commonly used data for Web3, so I use Etheum NFT for example. #!
Etheum NFT uses EIP-721 standards, whose data format is very “flexible ” , such as a picture of a NFT that may be used according to the different preferences of the publisher <<PROTECD_BLONK_0> > <PROTECTED_BLONK_1> > or <PROTECTED_BLONK_2> > , or even a picture at all, and possibly a video, 3D model, which causes a lot of trouble for the front-end presentation.
- It is also very difficult to obtain all the Etheum NFTs owned by an address, and because of the design of the Etheum, it needs to read all the transaction records of this address, and Etheum is not just the main network, but also various side chains such as Polygon, BSC, Arbitrum, Fantom, Gnosis, which is an impossible task for the front end, which can be partially addressed by a variety of data indexing services at present, but how should they be chosen if they return in different data formats, with different functions and different chains?
In response to the first question, Unidata designed a series of friendly and uniform data formats, divided into four parts: Profiles, Links, Assets and Notes. Etheum NFT belongs to Assets format. By a fixed data format returned by Unidata, the front end will no longer need to do troublesome, confusing data formats.
Also worth mentioning is the fact that Etheleum NFT, Unidata currently supports Solana NFT, Etheeum NFT and Solana NFT in a uniform data format, and that Unidata will continue to support more Assets sources, which will all be uniform.
Once the first problem is resolved, the second problem can easily be resolved. The approach of Unidata is to consolidate and aggregate the data returned by each service in the same format. For example, the OpenSea service supports the main network, the Alchemy service supports Polygon, the Moralis service supports the BSC, Arbitrum, Fantom, POAP service supports the POAP NFT of the Gnosis chain. All NFTs of the main network, Polygon, BSC, Arbitrum, Fantom, POAP can be accessed through the Unidata line code. An online demonstration can be [read here] (https://unidata.app/guide/assets/etheum-nft/#live-demo).
Apart from Assets, Unidata, there are three parts: Profiles, Links, Notes.
[Assets] (http://unidata.app/guide/assets/) Etheneum NFT (Mainnet, Polygon, BSC, Arbitrum, Fantom, Gnosis, POAP, Solana NFT, Alchemy, Solscan, Moralis, OpenSea.
[Notes] (https://unidata.app/guide/notes/) There is currently support for Mirror Entry, Etheum NFT Activity (Mainnet, Polygon, BSC, Arbitrum, Fantom, Gnosis, POAP), RSS3.
[Profiles] (https://unidata.app/guide/profiles/) currently supports ENS, Crossbell, Infra.
[Links] (https://unidata.app/guide/links/)
There are also many additions that can be added [to document all services and data sources currently supported] (https://unidata.app/guide/#supported-sources).
[!] [GitHub Org’s Stars] (.attachments/Unidata?style=social.svg+xml)] (https://github.com/DiYgod/Unidata)] [![Discord] (./attachments/968954680514342973?labelel=Discord&logo=discord&style=social.svg+xml)] (https://discord.gg/gggrhdS9Fe) [! [TiltrayFollow] (./attachments/Unidatastyle=social.svg+xml)] (https://twitter.com/Unidata)
[image] (./attachments/bafybeicuh3kxrw44ta2cg6emxlx2rm4nnuar5lova6locq5cr4637vbni4.png)