Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add DC #2134

Closed
wants to merge 3 commits into from
Closed

add DC #2134

wants to merge 3 commits into from

Conversation

onexie
Copy link

@onexie onexie commented Dec 4, 2023

Project Abstract

  • DC: Decentralized Cloud
  • DC is a DePIN,We will build a decentralized network infrastructure for developers very convenient to develop decentralized applications with their Web2.0 development experience.And the user experience of using DApps based on DC is just like using the Apps based on Web2.0.
  • We provide developers with a complete gRPC interface and client SDK to enable rapid integration with the DC network services for the development of DApps.

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 Polkadot (USDC & USDT) address in the application).
  • I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
  • 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: @_onexie_:matrix.org (change the homeserver if you use a different one)

Signed-off-by: onexie <116145646+onexie@users.noreply.github.com>
Copy link
Contributor

github-actions bot commented Dec 4, 2023

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

@onexie
Copy link
Author

onexie commented Dec 4, 2023

I have read and hereby sign the Contributor License Agreement.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for your interest in our grants program. However, at the moment, your application still contains wording that is simply copied from the template, like: "We will publish an article/workshop that explains [...] (what was done/achieved as part of the grant). (Content, language and medium should reflect your target audience described above.)" Could you update this? Also we usually don't support: "internal testing". We only support the development of new open source features via our grants program. Apart from this would need to have additional technical details for each deliverable (e.g. programming language, etc.). Furthermore, what do you mean with "parallel chain"?

@Noc2 Noc2 added changes requested The team needs to clarify a few things first. details missing Not enough technical details. labels Dec 4, 2023
Copy link
Contributor

github-actions bot commented Dec 4, 2023

Thank you for submitting a grant application.

We've assessed your submission and have found that it requires a higher level of technical detail in order to be considered for review. We encourage you to expand on it by providing a more precise specification/technical details. The section on project details in the application template is a good reference as to what type of information we expect applicants to provide, and these category-specific requirements contain more precise guidelines depending on what type of software you're building.

An area of the application that we often find to be insufficiently elaborated are the milestone deliverables. At a minimum, please indicate what languages/technologies you will be using to implement each deliverable, and provide a technical summary of its expected functionality. Note that deliverables should be tangible, reusable by other teams and in most cases not already present in the ecosystem. If they are, you will need to provide a comparison to existing implementations and explain why it makes sense to fund your approach. Also see our FAQ for a breakdown of what we fund and what we don't.

Let us know as soon as you're done with your changes, and we'll give your application another look!

@keeganquigley keeganquigley added the admin-review This application requires a review from an admin. label Dec 6, 2023
@onexie
Copy link
Author

onexie commented Dec 7, 2023

Hello, I have already modified our application and added technical details related to the project.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update. I will mark the application as ready for review and share it with the rest of team. However, I have some follow-up comments:

  • It sounds like you already developed most of the project and only asking us for a payment to open-source the code. Is this correct?
  • We usually only support deliverables that are beneficial for others, so "
    The DC network has entered the public testing phase, and anyone can participate." isn't something that we would support.

@Noc2 Noc2 added ready for review The project is ready to be reviewed by the committee members. and removed changes requested The team needs to clarify a few things first. details missing Not enough technical details. labels Dec 7, 2023
@onexie
Copy link
Author

onexie commented Dec 7, 2023

  • We usually only support deliverables that are beneficial for others,

Hello, here are my responses to your two comments:

Regarding "It sounds like you already developed most of the project and only asking us for a payment to open-source the code. Is this correct?"

You understood correctly that we have basically completed most of the cloud service functionality based on basic functions. Going forward, we have two major parts of work:

1、The economic model development on DCChain is still at the initial stage. Previously in the functional development phase, we mainly designed and implemented payment and charging related functions based on security model principles. However, for this project to truly grow, a sound economic model must be established to attract device providers and application developers. This part may require us to devote more effort to study the economic models and implementation approaches of other blockchain projects, and then improve DC's economic model.

2、Development of application SDKs. After completing the basic functionality development, in order to realize SDK development for mainstream development languages to allow ordinary developers to quickly develop Dapps, we need to complete this work before others can easily develop Dapps. Currently we have only completed the Dapp SDK development for Android.

Regarding "The DC network has entered the public testing phase, and anyone can participate."

I apologize, my previous description may have been problematic. My actual meaning is that "releasing the DC network and entering the public beta testing phase" is a state that the DC network needs to enter after other deliverables are completed, rather than its current state. The original intention of DC network is to bring decentralized cloud service capabilities to parachains of Polkadot, while for performance considerations, the DC network itself will not support smart contract functionality. Therefore, the DC network also needs the features of other parachains to facilitate convenient calls from DApps based on the DC network to smart contracts or unique functions of other parachains.

@keeganquigley
Copy link
Contributor

Thanks for the application @onexie I have to agree that since the project is already in the public beta phase, and much of it has been built, it's probably not the best fit for the grants program. This is because we focus on early-stage PoCs that don't exist yet, and I'm not sure that the components would be re-usable for others.

Additionally, we don't fund Solidity development, since our expertise is mainly in ink! contracts. Therefore for these reasons I'm not going to support this application, but I thank you for the time and effort you put into it, and I wish you the best of luck in finding funding.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot for the application and all the effort you put into this. The grants committee decided today to close your application, given the reasons above. We wish you all the best for your project, and let us know if you have any questions.

@Noc2 Noc2 closed this Dec 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
admin-review This application requires a review from an admin. ready for review The project is ready to be reviewed by the committee members.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants