Create DataBlock.md

[diposs]

Project Abstract

A searchable database that provides a record of precedence, cross-chain analysis, proof of history, context, security, and ownership of NFTs across multiple parachains in the Polkadot ecosystem and other Blockchains. The tracker will collect data like NFT creation, past ownership history, metadata. The data will be made accessible via polybase and Datablock own SDK.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (bank details via email or BTC, Ethereum (USDC/DAI) or Polkadot/Kusama (USDT) address in the application).
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @diposs:matrix.org (change the homeserver if you use a different one)

[CLAassistant]

All committers have signed the CLA.

[Noc2]

Thanks for the application. But to be honest, the current deliveries look a little bit strange to me and not necessarily beneficial for others. "Data model definition" seems only valid for your project and only if you continue to work on the project, and the "NFT scanner module" contains a lot of chains that we don't support as part of our grants program. Could you potentially update this or comment on it?

[diposs]

Polybase.xyz is a very versatile web3 database system. In my view it is more like a backend as services. I could have applied a general database like mongodb but I wanted a service in the web3 space that checks all the boxes. "Data model definition" uses polybase polylang to write out the schemas. All schemas are public so access to how the database is written and how it handles data is all public. Yes, the data stored could be made private like every other web2 database but, it isn't beneficial to have it private. I want an information repo that can be challenged for data inconsistencies or any mistakes.
The reason for involving lots of chains is for cross-chain analysis. Nft minted on one chain by a certain person or persons should be known by everyone. If such nft data is minted elsewhere the data act as proof of history, precedence and security. If the chains allowed are only polkadot and it substrates, it still permits fraud in the system since most users would be oblivious to its existence elsewhere.
This modeling style and inclusion of other chains outside the polkadot ecosystem provides security for both the popular and unpopular NFT project, be it media or document.

Thank you.

[diposs]

Modified the chains to just include polkadot and Ethereum.
In anticipation to this questions - #1832 (review)

Thanks for the application. A couple of questions:

• When you talk about NFTs, do you mean the NFTs pallet, PSP34s, uniques pallet, or EVM-compatible ones?
• Indexing NFT-related events seems to be a common indexer task. See, for example, https://github.com/emarai/squid-polkadot-psp34-nft-indexing. Why should we fund another, NFT-only indexer?

First Question - Everything would be attempted. This project is very personal to me. My first set of cool arts I purchased in the were all stolen art. I didn't purchase them for the cost. I wasn't searching for hype or popular piece. I wanted something I that spoke to me personally. This was an art work that its price was higher than the original mint price for BAYC but it was purchased only to have it booted for fraud. I am not indexing the event only my main objective is the metadata. Having the history / event log helps with security but it isn't the main factor. As good as IPFS CID is just a change of a byte means the file may as well be an original in its sight. This doesn't make the work Unique. Visually it is still a plagiarized work. This milestone is for Blockchain Indexation but the project Goal is helping to combat plagiarism or blatant project theft.
In my view the blockchain is a blind cashier, she stamps every transaction as long as the format is right.

Second Question - I have researched the project in question. It takes account of quantitative data point, Similar data but not the same. The project have very different focus. I want a searchable database that provides a record of precedence, cross-chain analysis, proof of history, context, security, and ownership of NFTs across multiple parachains in the Polkadot ecosystem and other Blockchains. The tracker will collect data like NFT creation, past ownership history, metadata.

The Big player get this Bored Ape Yacht Club creator wins lawsuit over copycat NFT collection but users have been scammed or ripped off. This project is the cents paid to prevent dollars of lessons from being ripped off or scammed by plagiarized works.

[Noc2]

Thanks for the quick reply. I would still recommend to define the actual deliveries more concrete (e.g. what kind of NFT standards will you support) and how it's useful compared to existing solutions. The fact that you will use polybase alone isn't very concrete. Also for this grant, feel free to remove ETH as well. We are looking for projects that are beneficial for the Polkadot/Kusama/Substrate ecosystem as part of this grants program.

[diposs]

@Noc2 Modifications have been made. The project would be focused on just Polkadot and its parachains. I would also provide a Graphql Schema.

| 1. | Data model definition | Designing and defining the architectural overview of the data model for this application using polybase.xyz and a graph schema would be provided.   |
| 2. | NFT scanner module | This module will scan the blockchain for any NFT related data from the genesis block and invoke indexer module for POLKADOT PSP34s and EVM-compatible NFTs. Other chains might be included.  |

[Noc2]

Thanks for the update. I will mark the applications as ready for review. However, I personally won't accept it since I don't see a lot of value in it compared to the existing solutions. But the rest of the team might have a different opinion.

[keeganquigley]

Thanks for the application @diposs a couple of questions/comments:

• Is this application in response to your own needs as a user that were not being met? Have you done any temperature checks in the community to see if this is needed and researched the other NFT projects here?
• Is the Vercel app currently supposed to do anything? I can see the search bar but can't get it to index anything.
• Your application states that EVM compatibility will be completed "later on", but the delivery tables states that the scanner module will work with "EVM-compatible NFTs". This seems contradictory to me, can you explain which is the case?
• How do you plan to fund upkeeping the app and integrating XCM v4 when it is released?

Thanks!

[diposs]

• Is this application in response to your own needs as a user that were not being met? Have you done any temperature checks in the community to see if this is needed and researched the other NFT projects here?
• Yes. Temperature checks, No! ondora.xyz and nftscans.com are similar projects but not the same as mine
• Is the Vercel app currently supposed to do anything? I can see the search bar but can't get it to index anything.
• it isn't yet connected to output the data from my polybase collection but if you wish for the explore version
  https://explorer.testnet.polybase.xyz/collections/pk%2F0x89de820323237a0e6cab8c5f29dfbf2f026f8c1da20c01f5b06b31877252a9d0f493bf95b625b667b1bdb3fb1593553bda1f056220cb2aa0e680316dba8b9a2c%2Fsh!%2FIndexBlock
• Your application states that EVM compatibility will be completed "later on", but the delivery tables states that the scanner module will work with "EVM-compatible NFTs". This seems contradictory to me, can you explain which is the case?
• later on, Yes. it doesn't stop the project from indexing data of EVM- Compatible NFTs.
• How do you plan to fund upkeeping the app and integrating XCM v4 when it is released?
• I do not wish to respond.

my opinion

Every Blockchain grant tends to be just a little selfish.
Just fix my Blockchain or limit the scope.
Being honest I rather work on multiple Blockchains than just one.
I have been advised to remove other chains from my application.

This entire process put I and my project at the mercy of Polkadot. from agreeing to fully opensource to polkadot being the sole judge of an acceptable job welldone or not to funds only being paid after job completion. Nothing before completion.
All this policies aren't a turn off to me but if the line of questioning is this considering how lopsided the agreement is for a level1 project, Please close if you feel having an entire overview of the entire blockchain to provide enhance security by informing the community of fraud committed on other chains due to the value extracted on other chains isn't Value enough?
I am contented with having this proposal closed.
Thank you

[keeganquigley]

Thanks for your answers @diposs, they definitely helped me to understand the project more. Regarding your last paragraph, having committee members leave comments/questions on an application is a regular part of the review process. We ask these questions partly to learn/understand the project better, and also to ensure that the project will keep being maintained.

Please understand that one committee member's opinion alone doesn't dictate whether or not an application gets accepted. Rather, applications are decided on by the grants committee as a whole. For level 1 grants, only two approvals are needed to accept the application.

That being said, I will go ahead and close the application per your request. Please let me know if you would like us to re-open it.