w3f
Sator x Polkadot Grant Proposal
Project Abstract
Please replace these instructions with a brief description of your project summarising key points (1-2 paragraphs).
If your application is a follow-up to a previous grant, please mention which one in the first line of the abstract and include a link to previous pull requests if applicable.
Grant level
- [ ] Level 1: Up to $10,000, 2 approvals
- [ ] Level 2: Up to $30,000, 3 approvals
- [x ] Level 2.5 up to $70,000
- [ ] Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)
Application Checklist
- [x] The application template has been copied and aptly renamed (
project_name.md). - [ x] I have read the application guidelines.
- [ x] A BTC, Ethereum (USDT/USDC/DAI) or Polkadot/Kusama (aUSD) address for the payment of the milestones is provided inside the application.
- [ x] The software delivered for this grant will be released under an open-source license specified in the application.
- [ x] The initial PR contains only one commit (squash and force-push if needed).
- [x ] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
- [ x] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is:
@_______:matrix.org(change the homeserver if you use a different one)
I’m closing this application for now due to inactivity. Let me know if you want to continue to work on it and I can reopen it.
Hey, I've updated the PR to reflect Level 3. The application will be open source and we can use the Apache 2.0 license, or whatever is standard in your experience.
Have made updates to the grant in response to the previous comments. Changed grant to Level 2 status.
Yes, I can change these items and make the milestones more specific for your team to better evaluate please re-open this thank you
I'm closing this again due to inactivity. Let me know if you actually want to work on it. We usually close PRs after two weeks without any comment.
yes, would like to push updates. Can provide updates inline until this is reopened, lmk
pushed updates regarding smart contract specification and removed the original template text that isn't bolded
Regarding the “Smart contract for NFT Marketplace,” where do you actually plan to deploy this, and in which programming language? On your independent chain? Don’t you need to implement this in ink!?
The Marketplace currently operates with a Golang back end and React Native front end. Currently the marketplace supports Solana NFTs, and we want to add Polkadot. We do not have an independent chain. Are you recommending that we should explore parachain development? From what I can see, we would implement this in ink.
Regarding the UI-related work, do you have mock-ups or designs that you can share already?
Sure, here is an example of mockups from the iOS/Android application. Here you can see where we would add Polkadot wallet compatibility to the existing application, as well as Polkadot NFTs to the marketplace, available from the iOS / Android application as well as directly from nft.sator.io. This would be mobile + desktop combined development
Regarding the Polkawallet SDK-related deliverables, it looks like you simply want to follow this tutorial for your own wallet. This doesn’t seem useful for others, and it also doesn’t sound like it takes three months to implement. Could you comment on this?
It requires more time as we are live in the iOS Apple store and Android stores and have to comply by their guidelines. The Flutter application has a Go backend as well, and there are no official Go SDK or API docs for this specific integration.
I think the end-to-end test shouldn’t be a separate milestone. Ideally, they are part of the previous milestone. I've removed the end-to-end tests milestone and have updated the milestone deliverables accordingly. Will now go ahead and sign the T&C
The most likely scenario is to link the marketplace via Substrate. We'll design smart contract logic using the module library and RUST; test locally with the SDK. We'll then create a Substrate runtime and integrate with SNI; test with the SDK.
We do use Rust contracts and will use them in this milestone.
I was simply referring to writing smart contracts in ink! for Substrate, the purpose of using Polkadot would be to multi-chain the NFT marketplace. In regards to RUST, we are building smart contracts for the Sator marketplace using RUST to onboard Solana users.
K, I will reopen the PR. Could you update this? In general, we need as many technical details as possible here since these are the requirements of our contracts. Otherwise, you could, for example, deliver any rust smart contract, and we would need to accept it.