Hey @MattL, thanks for your response and feedback. Apologies for the delay in my reply. Here are the answers to your questions. I will also update our proposal with these answers.
The grant request of 250k OP seems too large for a project in private alpha. Consider scaling down the requested amount or provide a detailed breakdown of how the funds will be used to justify the request.
We are in PUBLIC Alpha currently and busy arranging hackathons with user onboarding as well. Hackathons are being finalized with Dubai Blockchain Center, Jordan web3 and others.
Thanks for the advice and will scale down from 250k to 150k.
It seems like this proposal is trying to do a LOT of different incentives to handle most of the expenses that will be incurred by the team. Marketing expenses, Audit Expenses, and Hackathon expenses would not fit within no-sale.
The proposal does not provide a clear process for allocating the 30% of tokens intended for dApp deployments. To ensure quality submissions, please specify the criteria for receiving these incentives and any vetting process in place.
On the criteria for receiving OP incentives:
Regarding the 30% allocation for dApp deployments, each user deploying a dApp to Optimism will be incentivized with OP tokens to the equivalent value of the deployment gas fees. Deployers will also receive the OP token equivalent of gas cost for transactions going through the deployed contract. As the usage and transactions increase, the deployer will receive additional OP tokens equating to a percentage of the transaction’s value.
Template developers will receive OP tokens based on the amount of times their templates have been deployed to Optimism. For example, if a template gets deployed 10 times and has at least 20 transactions or $50 in transaction value, OP tokens will be dropped for the developer.
With regards to the 40% for marketing, OP tokens will be rewarded to people sharing Forward’s affiliate and referral links and on-boarding new users. For example, every person that gets 10 users to sign-up on the Forward platform will receive OP tokens and additional OP tokens for each user that deploys a dApp on Optimism.
20% for hackathons will be used as prizes for the developers uploading templates which have been assessed by the judges of the hackathon. For example, the first prize for the best hackathon template adjudicated by the judges will receive 500 OP tokens.
The remaining 10% of tokens will act as a bonus for the developer and deployer if the uploaded template is officially audited before deployment. For example, the developer of the audited template will receive an additional OP token drop when deployed, with the deployer also receiving more OP tokens for using the audited template.
We are also open to discuss what amount of OP tokens should be dropped for each topic.
The proposal does not clearly articulate the problem it is trying to solve within the Optimism ecosystem. Please provide a more detailed explanation of the need for this project and how it will benefit the ecosystem.
The problem that Forward is trying to solve is that Forward wants to make it easy, affordable and quick for any person to build and deploy a dApp directly to Optimism.
Forward will benefit the Optimism ecosystem by allowing any person irrespective if they are technically inclined or not, to build and deploy full-stack dApps. dApps being deployed would be aimed at real world use and business cases where the deployers would promote and market their dApp to increase the usage of it.
Developers can also upload their own templates and monetize the usage thereof. With more developers uploading templates in the Forward Marketplace, more unique dApp templates and deployments would occur. This would also drive more users to interact with the Optimism deployed dApps.
The provided metrics lack specificity and are not tied to clear timeframes. Without specific target dates, it is difficult to assess progress and hold the project accountable. Additionally, the critical milestones mentioned seem to be a subset of the benchmark milestones, which makes them redundant. Please revise the milestones to provide clearer and more measurable targets. Review the milestone assessment doc for more information. 1
Benchmark Milestones (revised):
- Forward will have 28,000 users by the end of July ‘23 and 70,000 by the end of December ‘23.
- Forward will have 840 developers uploading templates to the Marketplace by the end of July ‘23 and 2800 by the end of December ‘23.
- Forward Marketplace will grow from 12 templates to having 105 templates by end of July ‘23 and aiming for 700 by end of December ‘23.
Critical Milestones (revised):
- Forward will have at least 140 dApp deployments on Optimism by the end of July ‘23 and over 350 by end of December ‘23.
- Forward will have at least 35 unique template deployments on Optimism by end of July ’23 and over 105 by end of December ‘23.
- dApp usage metrics on Optimism will be at least 5,000 transactions by end of July ‘23 and over 50,000 transactions by end of December ‘23.
- Forward’s affiliation system will be integrated by the end of August ‘23.
- The EIP 2535 (Diamond Contract Deployment) will be integrated by the end of August ‘23.
With regards to metrics and timeframes:
dApp deployments on Optimism:
Dates: This is an ongoing and updating metric. We will provide MONTHLY updates on the 1st of every month showing the current stats.
Source of truth: This can be verified on-chain, we can provide a list of dApp contract addresses for you to check. This can also be verified through our API directly for authorized users once our API’s are made public.
dApp templates being used to deploy on Optimism:
Dates: This is an ongoing and updating metric. We will provide MONTHLY updates on the 1st of every month showing the current stats.
Source of truth: This can be verified by logging into the Forward Factory as a user/developer to see the templates in the Marketplace.
dApp usage metrics on Optimism:
Dates: This is an ongoing and updating metric. We will provide MONTHLY updates on the 1st of every month showing the current stats.
Source of truth: This can be verified on-chain on the respective dApp contract addresses for you to check.
Both benchmark and critical milestones can be amplified by a factor of at least 3 if there is additional support from OP’s marketing team as a joint effort to on-boarding developers and users with more joint activities