Pacific store

[vlbos]

Grant Application Checklist

• The application-template.md has been copied, renamed ( "project_name.md") and updated.
• A BTC address for the payment of the milestones is provided inside the application.
• The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
• The total funding amount of the project is below CHF 30k at the time of submission.

[mmagician]

@vlbos Thank you for the application.
We actually have some NFT teams building on Polkadot already, for example RareLink. Perhaps you could briefly comment on how your solution differs from theirs?

[vlbos]

@vlbos Thank you for the application.
We actually have some NFT teams building on Polkadot already, for example RareLink. Perhaps you could briefly comment on how your solution differs from theirs?

Thank you for your review .we update it . listing on how our solution differs from RareLink or Others

[mmagician]

@vlbos I have a couple of questions:

1. We've already built the largest marketplace for crypto collectibles

Could you provide a link to such marketplace? I never heard of PacificStore and also couldn't find any details online.

2. Why do you have Technical specifications and Zenlink DEX Module design as part of your first milestone?

3. We will need much more details in your milestones than Creation of integration APIs + documentation. This doesn't say anything about the code that you'll deliver. This applies to all of your milestones. Please update your grant application with relevant specifications please.

[Noc2]

@vlbos Please also specify the programming language/framework, which you are planning to use for each deliverable.

[vlbos]

@vlbos I have a couple of questions:

1. We've already built the largest marketplace for crypto collectibles

Could you provide a link to such marketplace? I never heard of PacificStore and also couldn't find any details online.

1. Why do you have Technical specifications and Zenlink DEX Module design as part of your first milestone?
2. We will need much more details in your milestones than Creation of integration APIs + documentation. This doesn't say anything about the code that you'll deliver. This applies to all of your milestones. Please update your grant application with relevant specifications please.

Thank you for your reviews.I'm sorry for rookie mistakes in the document.we updated it .Add details of the code of our milestones

[vlbos]

@vlbos Please also specify the programming language/framework, which you are planning to use for each deliverable.

Thank you for your reviews.we added programming language and framework part.

[Noc2]

Thanks for the update. Some of the formatting seems to be off. Additionally could you combine the Deliverables with the programming language/framework in one table? As Marcin pointed out, the deliverables are still a bit unclear to me: for example “Making Offers”, how will this work. Is it it implemented in the smart contract as well as the UI. And how does “Using ERC-20 tokens” work? Are you referring to tokens on ethereum, when you say erc-20 tokens? And do I understand it correctly, that you want to first create a solidity contract and then compile this with solang into a smart contract for edgware, correct? Did you already start to work on this smart contract? It sounds a little bit like you want to port OpenSea to edgeware with the help of solang. Is this correct?

[vlbos]

Thanks for the update. Some of the formatting seems to be off. Additionally could you combine the Deliverables with the programming language/framework in one table? As Marcin pointed out, the deliverables are still a bit unclear to me: for example “Making Offers”, how will this work. Is it it implemented in the smart contract as well as the UI. And how does “Using ERC-20 tokens” work? Are you referring to tokens on ethereum, when you say erc-20 tokens? And do I understand it correctly, that you want to first create a solidity contract and then compile this with solang into a smart contract for edgware, correct? Did you already start to work on this smart contract? It sounds a little bit like you want to port OpenSea to edgeware with the help of solang. Is this correct?

Thanks for the comment. basically correct.we will merge the tables ,simplify description ,elaborate more details of code.

[Noc2]

Thanks for the update. But if I understand it correctly, you are not really implementing all these functions and deliverables yourself. You are simply using solang to compile existing evm contracts into the correct wasm format for our contract module. I don’t understand why your deliverables also mention ink!, since it seems you won’t use ink!. Solang only compiles smart contracts to wasm in a way that the contract module can understand it. In general we would only support the parts of the application that focus on software development (that doesn’t already exist) related to Polkadot, Kusama and Substrate. So, I suggest to only focus on the parts that you actually have to implement and that are unique to our ecosystem.

[vlbos]

Thanks for the update. But if I understand it correctly, you are not really implementing all these functions and deliverables yourself. You are simply using solang to compile existing evm contracts into the correct wasm format for our contract module. I don’t understand why your deliverables also mention ink!, since it seems you won’t use ink!. Solang only compiles smart contracts to wasm in a way that the contract module can understand it. In general we would only support the parts of the application that focus on software development (that doesn’t already exist) related to Polkadot, Kusama and Substrate. So, I suggest to only focus on the parts that you actually have to implement and that are unique to our ecosystem.

Thanks for your suggestion. About wyvern contracts Rust cargo-contracts implement ,would you support it ?
These are the Ethereum smart contracts for the Wyvern Protocol, the Wyvern ERC20 token (WYV), and the Wyvern DAO.
it also is base part of opensea-js. as out first step to implement opensea-js on polkadot.
our future plan is the have-to implement of the other part of opensea-js on polkadot.it include opensea-js backend service and auto-generated UI according to a user's deployed contract and metadata.

By the way,
"you are not really implementing all these functions and deliverables yourself"
Our team has four people working part-time in this development.if needed ,we will add developers.

[Noc2]

Thanks for the quick response. In this case, what are you developers working on? If you for example need to adapt the existing opensea-js to integrate polkadot.js as well as add unique substrate related features, this would be potentially worth a small grant from us. Other than that, I know that https://moonbeam.network/ wants to launch a grant program soon, which might be better suited for these kinds of projects.

[vlbos]

Thanks for the quick response. In this case, what are you developers working on? If you for example need to adapt the existing opensea-js to integrate polkadot.js as well as add unique substrate related features, this would be potentially worth a small grant from us. Other than that, I know that https://moonbeam.network/ wants to launch a grant program soon, which might be better suited for these kinds of projects.

Thanks for your suggestion.our developers are working on frontend (javascript/typescript) or backend/system(C++/Rust) .
we will update the application according to your suggestions.
Many thanks

[Noc2]

Thanks for the update. This looks much better to me and I’m willing to go ahead with it.

[vlbos]

Thanks for the update. This looks much better to me and I’m willing to go ahead with it.

Thanks for the comment and approval.

[github-actions]

Congratulations! As part of the Open Grants Program, we want to help winning teams acknowledge their grants publicly while observing the foundation’s guidelines. To that end, we’ve created a badge for grant-winning teams. Here is a link to the download and guidelines.

Once you complete your first grant milestone, would you be interested in collaborating on an announcement about the work you’re doing? If so, then please get in touch with us at grantspr@web3.foundation prior to making the announcement (at least two weeks notice is preferred) so that we can coordinate on timing and content.

Please don’t announce the grant publicly before you finished at least the first milestone of the project.

[vlbos]

Thanks for the grant.

[alxs]

@vlbos care to share a quick status update, along with an ETA if possible? The project repo looks inactive and we were hoping to receive your next delivery a bit over 2 months ago now.

As long as you're actively working on the project, delays aren't a big problem, but we'd appreciate it if you could keep us in the loop. Note that if we don't hear from you soon, we will assume you're no longer interested and terminate the agreement.

[alxs]

This grant is being terminated due to inactivity. Feel free to apply again if you're still interested.