Create Chainvista #2576
Create Chainvista #2576
Conversation
|
CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. Please submit the following text as a separate comment: I have read and hereby sign the Contributor License Agreement. You can retrigger this bot by commenting recheck in this Pull Request |
There was a problem hiding this comment.
Hi @mtsraw, please stick to the application template. Also note that, we do not approve applications if applicants cannot provide any proof of experience with Polkadot, blockchain, or open source software development and maintenance.
|
Thank you for submitting a grant application. |
|
Here is it
…On Thu, Jun 26, 2025, 1:59 PM github-actions[bot] ***@***.***> wrote:
*github-actions[bot]* left a comment (w3f/Grants-Program#2576)
<#2576 (comment)>
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
<https://github.com/w3f/Grants-Program/blob/master/applications/application-template.md#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
<https://grants.web3.foundation/docs/Support%20Docs/grant_guidelines_per_category>
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
<https://grants.web3.foundation/docs/faq#what-activitiespositions-do-you-fund>
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!
—
Reply to this email directly, view it on GitHub
<#2576 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOYEYDKOISCPVCSHKT5D3U33FOY7DAVCNFSM6AAAAAB7SD2V6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBXG4ZTKOJSG4>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Here it is :
…On Thu, Jun 26, 2025, 4:00 PM Mts Talish ***@***.***> wrote:
Here is it
On Thu, Jun 26, 2025, 1:59 PM github-actions[bot] <
***@***.***> wrote:
> *github-actions[bot]* left a comment (w3f/Grants-Program#2576)
> <#2576 (comment)>
>
> 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
> <https://github.com/w3f/Grants-Program/blob/master/applications/application-template.md#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
> <https://grants.web3.foundation/docs/Support%20Docs/grant_guidelines_per_category>
> 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
> <https://grants.web3.foundation/docs/faq#what-activitiespositions-do-you-fund>
> 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!
>
> —
> Reply to this email directly, view it on GitHub
> <#2576 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BOYEYDKOISCPVCSHKT5D3U33FOY7DAVCNFSM6AAAAAB7SD2V6WVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAMBXG4ZTKOJSG4>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
There was a problem hiding this comment.
Hi @mtsraw I don't see that any changes have been made, can you check again? It should adhere to the application template and contain some milestone delivery tables, etc.
|
I have done changes
Now kindly you review it
Here's the screenshot of that
…On Fri, Jun 27, 2025, 10:04 PM Keegan | W3F ***@***.***> wrote:
***@***.**** requested changes on this pull request.
Hi @mtsraw <https://github.com/mtsraw> I don't see that any changes have
been made, can you check again? It should adhere to the application
template
<https://github.com/w3f/Grants-Program/blob/master/applications/application-template.md>
and contain some milestone delivery tables, etc.
—
Reply to this email directly, view it on GitHub
<#2576 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BOYEYDPVWZVGN5RPTESZEZD3FV2QRAVCNFSM6AAAAAB7SD2V6WVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDSNRXGMYDKMJTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Project Abstract
ChainVista is an all-in-one Web3 security and discovery platform designed to reduce crypto scams, presale risks, and token contract vulnerabilities. We combine native smart contract scanning, presale scoring, whale intelligence, and airdrop eligibility into one unified interface.
By integrating this platform into the Substrate / Polkadot ecosystem, ChainVista will provide Substrate-based chains with a public security layer for token presales, whale monitoring, parachain token transparency, and airdrop verification. The system directly empowers retail investors, DAOs, parachain launchpads, and ecosystem users to safely engage in DeFi markets while protecting capital, driving trust, and onboarding new users into Polkadot’s expanding multichain environment.
Grant level
[ ] Level 1: Up to $10,000, 2 approvals
[x] Level 2: Up to $30,000, 3 approvals
[ ] Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)
Application Checklist
[x] The application template has been copied and aptly renamed (chainvista.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
[x] I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[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).
[ ] 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)