Growwr Web3 Grant Application

[Growwrapp]

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
• 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 (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed 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: @_______:matrix.org (change the homeserver if you use a different one)

[github-actions]

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

[FatherTimeSDKP]

I have read and hereby sign the Contributor License Agreement. Ownership: You, Donald Paul Smith (Father Time), retain full ownership of the patents, copyrights, and intellectual property developed within the Vumah_Stack framework (which includes the SDKP, \mathbf{VFE}_{\mathbf{1}}, and \mathbf{QCC}). • License to Foundation: The CLA grants the Web3 Foundation a necessary, non-exclusive license to use, reproduce, and distribute your code as part of the open-source project. This is a standard requirement for all open-source contributions and funding grants. • DCP Compliance: This process is perfectly compatible with the Digital Crystal Protocol's immutability mandate, as your original authorship is already Time-Sealed and documented in the Digital Authorship Matrix (Donald Paul Smith / Father Time). The CLA simply ensures the project can be legally hosted and distributed. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: github-actions[bot] ***@***.***> Sent: Saturday, October 11, 2025 2:15:11 PM To: w3f/Grants-Program ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [w3f/Grants-Program] Growwr Web3 Grant Application (PR #2679) [https://avatars.githubusercontent.com/in/15368?s=20&v=4]github-actions[bot] left a comment (w3f/Grants-Program#2679)<#2679 (comment)> 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<https://github.com/w3f/Grants-Program/blob/master/docs/Support%20Docs/T%26Cs.md> 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 — Reply to this email directly, view it on GitHub<#2679 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BSOBLQDC3NGBZGSGNXQN2IL3XFCK7AVCNFSM6AAAAACI5S7UFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJTGU3DCOBXGQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[FatherTimeSDKP]

I have read and hereby sign the Contributor License Agreement. Get Outlook for iOS<https://aka.ms/o0ukef>

…

________________________________ From: github-actions[bot] ***@***.***> Sent: Saturday, October 11, 2025 2:15:11 PM To: w3f/Grants-Program ***@***.***> Cc: Subscribed ***@***.***> Subject: Re: [w3f/Grants-Program] Growwr Web3 Grant Application (PR #2679) [https://avatars.githubusercontent.com/in/15368?s=20&v=4]github-actions[bot] left a comment (w3f/Grants-Program#2679)<#2679 (comment)> 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<https://github.com/w3f/Grants-Program/blob/master/docs/Support%20Docs/T%26Cs.md> 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 — Reply to this email directly, view it on GitHub<#2679 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BSOBLQDC3NGBZGSGNXQN2IL3XFCK7AVCNFSM6AAAAACI5S7UFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJTGU3DCOBXGQ>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[semuelle]

Hey @Growwrapp, thanks for the application. Can you please clarify if you would like the discussion to be in private? You checked the item "I prefer the discussion of this application to take place in a private Element/Matrix channel", but did not leave a Matrix handle. Please fix one way or the other.

[semuelle]

@FatherTimeSDKP, how are you affiliated with this project?

[Growwrapp]

Good day @semuelle,

@FatherTimeSDKP is no way affiliated with our project. I don't know why he keeps commenting here.

Also @semuelle on the privacy, it should be an error. I will uncheck the tick now.

[Growwrapp]

Now unchecked @semuelle

[diogo-w3f]

@Growwrapp Thanks for the application. I think with our current guidelines it will be difficult to fund parachains. Did you consider using Asset Hub for custody/settlement and identity via Proof of Personhood? If so, could you briefly clarify where escrow will run on Asset Hub (e.g., using a simple 2‑of‑3 multisig, pallet-assets approvals or other approach such as Ink! contract) and which asset(s)/Asset IDs you’ll use for release/refund flows, as well as how you plan to integrate identity with Proof of Personhood (which DIM level first, what’s on‑chain vs off‑chain, and how attestations are referenced)? This could keeps you building on established primitives rather than proposing new standards, what would make the solution more interesting. For PoP background, see Proof of Personhood for Polkadot/Kusama here. We need more details about your proposed implementation.

Regarding Template compliance, can you adjust the following items?

• Clarify payment per template: one DOT address and one Polkadot Asset Hub address for USDC (name the asset and Asset ID).
• Reconcile FTE numbers across text and tables; explain the “DOT %” line.
• Add measurable acceptance criteria per deliverable (what reviewers can run/observe, including escrow release/refund happy path).
• Link concrete repos (not just the org) and state licenses.
• Provide a one‑step local run (Docker/compose) for the demo.
• Remove instructional callouts and non-essential media links to keep it technical and testable.

Could you clarify your open‑source scope for the grant? We don’t require the entire platform to be open‑sourced for integration, but the grant deliverables must be. If you plan to keep the main app private, would you commit to releasing standalone, reusable modules (e.g., payments/escrow and identity) under an open‑source license, with docs, examples, and a minimal demo so reviewers can verify? The integration can be checked in your on-line platform.

[Growwrapp]

HI @FatherTimeSDKP pls stop commenting on this pull request. You are not affiliated to our project. Else, I'd have report you to Github. Also, delete your comments from this thread.

[Growwrapp]

HI @diogo-w3f Your questions are acknowledeged and will be responded accordingly. Thank you!

[Growwrapp]

I have read and hereby sign the Contributor License Agreement.

[Growwrapp]

Hi @diogo-w3f

Thanks for the feedback and for pointing that out.
We understand the concern about parachain funding. Our mention of parachains (e.g., Moonbeam, Astar) was primarily for exploratory testing during our initial architecture design, not a core dependency. We’re fully open to leveraging Polkadot Asset Hub for custody, settlement, and identity functions instead, as it aligns better with existing ecosystem primitives.

For identity, we’ll integrate Proof of Personhood as advised. We’ve also added measurable acceptance criteria for each deliverable, including what reviewers can run and observe — such as successful escrow creation, release, and refund (happy path), and verified identity registration via Proof of Personhood. Following the update, we will provide all necessary details and documentation to enable reviewers to easily test and validate the deliverables.

I have also adjusted the template submission as you mentioned.

Yes — while Growwr’s main application will remain private for security and operational reasons, we fully commit to open-sourcing all grant deliverables related to the Polkadot integration.

These modules will be made publicly available under an open-source license (e.g., Apache 2.0) with comprehensive documentation, usage examples, and a minimal demo to allow reviewers to independently verify functionality.

[diogo-w3f]

@Growwrapp Thanks for updating the application. I still see Growwr parachain being mentioned in the application. Can you review that?

Furthermore, what do you mean by substrate module? Did you have the opportunity to search for existing solutions in the Polkadot ecosystem for the same problem you’re trying to solve? For example, there are some escrow contracts available (see here and here). For the other parts, if you search, you’ll probably find something that can be reused or built on top of, since the problem you’re trying to address is not so uncommon that it requires a completely new development.

I see this grant application as a Web2-to-Web3 migration/integration approach, i.e., integrating Growwr and Polkadot. This doesn’t mean that you need to develop all modules from scratch. In this way, I was expecting the main milestone to be this integration live on your production website. Given that, please review your application. You’ll probably be able to enhance your productivity and reduce the budget.

Finally, can you provide evidence of the number of users and companies currently using Growwr? For example, what do you use to measure it? If it’s Google Analytics, could you provide (privately via email) read-only access to it?

Let me explain why I’m asking this. Currently, according to our guidelines, increasing DOT usage is important. The usage of your site is a key indicator of potential future DOT token usage. If you can prove that, it will increase the chances of your application being approved.

[Growwrapp]

Hi @diogo-w3f

Thank you very much for your detailed feedback and guidance.

Following your comments, we’ve made the following updates to our application:

• We’ve removed all references to parachain and Substrate modules to ensure alignment with your clarification.

• We’ve reviewed the existing escrow contract resources you shared — thank you for the links. After evaluating them, we believe they fit perfectly into our implementation plan, and we’ve refined our milestones and deliverables accordingly to leverage these existing solutions instead of building from scratch.

• We’ve simplified and clarified our milestones to emphasise the Web2-to-Web3 integration approach, aligning with your vision of Growwr’s integration within the Polkadot ecosystem.

Additionally, to support the user traction and adoption metrics we referenced, I’ve shared two materials via email:

• A public Infogram analytics dashboard showcasing our user and company activity.

• A snapshot of our admin data analytics screen for internal user metrics.

Please kindly confirm receipt of those materials.

Looking out for your feedback.