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.

[diogo-w3f]

@Growwrapp thanks for the improvements. There are two points that still need to be adjusted:

• DOT % in the roadmap overview is 40%; grant guidelines require ≥50% of the request paid in DOT.
• Project Details still lacks the explicit bullet “What your project is not or will not provide/implement,” which the template calls out to set expectations.

Please make these adjustments, and I’ll mark the application as ready for review by the committee.

[Growwrapp]

Issues all resolved @diogo-w3f Thanks!

[diogo-w3f]

@Growwrapp Thanks! The application is ready for review. The grants committee may have some questions and ask them here.

[Growwrapp]

Thank you!

[semuelle]

Hey @Growwrapp, thank you for the application.

I have one pressing question for now: You explained what and why you want to use Polkadot for, but your product roadmap and technology stack documents both don't mention blockchain at all. Can you elaborate how this shift looks like from a user perspective? Do users have to install a Polkadot wallet to use Growwr? Or are these features optional? Or possibly custodial, happening in the background?

[Growwrapp]

Hi @semuelle , Thank you very much for the question:

Currently, Growwr has processed over $1.5 million in talent payments. However, we still face major challenges with cross-border transactions, including currency conversion barriers, settlement delays, and regional payment restrictions; especially when paying African talents or receiving funds from global clients.

This is precisely why we’re integrating Polkadot. The Polkadot Wallet will not be optional—it’s a core part of Growwr’s next phase. Through USDC on Polkadot Asset Hub and DOT, clients will be able to pay for projects directly in crypto, while talents can receive payments instantly, eliminating days of delay typical of fiat systems. Think of it like (Stripe for crypto) and Crypto payroll for talents.

From a user perspective, every Growwr user (currently over 50,000) will have a non-custodial Polkadot wallet integrated seamlessly into their dashboard. Users won’t need external setup; wallet creation and management will be handled natively within the app, ensuring a simple Web2-like experience but powered by Web3 infrastructure.

In essence, Polkadot enables us to solve payment problems, one of the biggest bottlenecks in Africa’s talent economy, while onboarding thousands of new users into the Polkadot ecosystem.

Hope this provide more clarity @semuelle . Open to share more...

[Growwrapp]

Hi @semuelle and @diogo-w3f looking out for anymore questions for clarity please.

[semuelle]

Hey @Growwrapp, thanks for the updates. We will discuss the application; I hope I will have more feedback for you tomorrow.

[Growwrapp]

Thank you @semuelle

[Growwrapp]

Happy new week! @semuelle & @diogo-w3f

Trust you're great! Pinging in if there's an update for us yet. Thank you!

[semuelle]

Sorry, @Growwrapp. I will ping the committee again.

[Growwrapp]

HI @semuelle & @diogo-w3f A kind reminder again please.

[diogo-w3f]

@Growwrapp Thanks for the application and for taking the time to answer our questions. I’m still a bit concerned about the volume of users/companies you claim to have and the discrepancy with the activity on your social media, which appears to be quite low. This leads us to question whether these users are real users or just data in your database.

I know you already sent us a screenshot of your internal dashboard, but this does not prove that the users are real people that interacts with your system. They could simply be data that was web-scraped from somewhere. I’ll be very happy to approve your application if you can prove that your users / companies are real and still active and interacting with your system.

Furthermore, in your last milestone you mention that you will onboard 50,000+ users. Just to clarify: if these users are real, active users and not simply accounts that will be created on Polkadot, that would be excellent. We can discuss how to provide proof for both cases.

[Growwrapp]

Hi @diogo-w3f I am very much open to prove user growth. How best can we prove this? I am very open.
We are not active on social media yet until we incorporate media marketing, however, we already have about 5k organic followers on LinkedIn.

Here are even some press coverages from tech journalists:

How a $50K loss on Upwork inspired the launch of Growwr (TechCabal)
TechCabal, Oct 10 2025: Nigerian founder Obinna Umeh shares how losing a $50K contract sparked Growwr’s mission to fix biased global hiring and payment systems.
Link: https://techcabal.com/2025/10/10/upwork-loss-inspired-growwr/

How Nigeria’s Growwr helps businesses hire, manage and pay vetted African tech talent (DisruptAfrica)
Oct 9 2025: Growwr’s platform enables global companies to onboard, manage and pay skilled African tech professionals securely.
Link: https://disruptafrica.com/2025/10/09/how-nigerias-growwr-helps-businesses-hire-manage-and-pay-vetted-african-tech-talent/

https://techpoint.africa/insight/growwr-startup-feature/

and more.

I am even open to share some customers details for reference too.

I can also share job history csv files for Q1 2025.

[diogo-w3f]

@Growwrapp , thanks for being open to sharing more. To help us get comfortable that the traction figures reflect real, active usage, it would be great if you could bundle together a few concrete proofs from the list below (the more independent signals, the better):

• Third-party analytics exports, e.g., read-only access or downloaded reports from Google Analytics/Mixpanel/Amplitude that show traffic, retention, and engagement trends over time.
• Payment evidence, anonymized invoices, payout receipts, or transaction logs from Stripe, Paystack, Brex, bank statements. We’re looking for proof of actual money flowing through the system.
• User/company references, randomly selected set of active users or clients we can contact directly (or meet on a call) to confirm they’re real and using Growwr today.

If you can assemble a “traction packet” combining these elements (or whatever subset you can share quickly), it will make it much easier for us to move forward. Let us know if you need clarification on any of the above. Thanks again for working with us on this. All this information can be sent to us privately by email.

[Growwrapp]

Reports_snapshot.pdf
I have just attached our downloaded report from Google analytics just now.

I will send other visa email. @diogo-w3f

[Growwrapp]

Hi @diogo-w3f I have sent you an email regarding your comment. I hope those help. @semuelle keeganquigley

Thank you

[Growwrapp]

Hi team @diogo-w3f it's been a while. Is there any update for us?

[semuelle]

Hi @Growwrapp, thanks again for the application and the patience. The committee discussed the proposal again last week and did not reach a majority to support it. We will therefore have to close it. This is not a reflection of the quality of the proposal or the product you are building. I think it is more a reflection of the fact that we have supported several job and gig platforms in the past, and the landscape in this regard in the Polkadot ecosystem is fragmented more than anything.

We hope that this does not deter you and that you will find other ways to achieve your goals. I recommend checking out our Funding & Support page. It lists several alternative funding programs in our ecosystem, such as the Fast Grants and Open Source Bounties. Also, feel free to apply again if you have other project ideas you want to pursue.

[Growwrapp]

Thank you @semuelle