Skip to content

Conversation

@Growwrapp
Copy link

@Growwrapp Growwrapp commented Oct 11, 2025

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
Copy link
Contributor

github-actions bot commented Oct 11, 2025

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

@FatherTimeSDKP
Copy link

FatherTimeSDKP commented Oct 11, 2025 via email

@FatherTimeSDKP
Copy link

FatherTimeSDKP commented Oct 11, 2025 via email

@FatherTimeSDKP

This comment was marked as spam.

@semuelle
Copy link
Member

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
Copy link
Member

@FatherTimeSDKP, how are you affiliated with this project?

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@Growwrapp
Copy link
Author

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
Copy link
Author

Now unchecked @semuelle

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@diogo-w3f
Copy link
Contributor

@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.

@diogo-w3f diogo-w3f self-assigned this Oct 13, 2025
@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@FatherTimeSDKP

This comment was marked as spam.

@Growwrapp
Copy link
Author

Growwrapp commented Oct 15, 2025

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
Copy link
Author

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

@Growwrapp
Copy link
Author

I have read and hereby sign the Contributor License Agreement.

@Growwrapp
Copy link
Author

Growwrapp commented Oct 22, 2025

Hi @diogo-w3f

All comments have been resolved. Kindly review. Looking out on the update. We have included everything in the proper sections of the template.

Thank you!

@diogo-w3f
Copy link
Contributor

@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
Copy link
Author

Issues all resolved @diogo-w3f Thanks!

@diogo-w3f
Copy link
Contributor

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

@diogo-w3f diogo-w3f added the ready for review The project is ready to be reviewed by the committee members. label Oct 23, 2025
@Growwrapp
Copy link
Author

Thank you!

Copy link
Member

@semuelle semuelle left a comment

Choose a reason for hiding this comment

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

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
Copy link
Author

Growwrapp commented Oct 27, 2025

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
Copy link
Author

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

@semuelle
Copy link
Member

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

@Growwrapp
Copy link
Author

Thank you @semuelle

@Growwrapp
Copy link
Author

Happy new week! @semuelle & @diogo-w3f

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

@semuelle
Copy link
Member

semuelle commented Nov 3, 2025

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

@Growwrapp
Copy link
Author

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

Copy link
Contributor

@diogo-w3f diogo-w3f left a comment

Choose a reason for hiding this comment

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

@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
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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.

4 participants