Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Protico: Web3-Powered Community Success for Web2 brands #2025

Closed
wants to merge 3 commits into from
Closed

Protico: Web3-Powered Community Success for Web2 brands #2025

wants to merge 3 commits into from

Conversation

howieyoung
Copy link

@howieyoung howieyoung commented Oct 1, 2023

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 (bank details via email or Polkadot (USDC & USDT) or BTC address in the application).
  • 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 1, 2023

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

@howieyoung
Copy link
Author

I have read and hereby sign the Contributor License Agreement.

Copy link
Collaborator

@Noc2 Noc2 left a comment

Choose a reason for hiding this comment

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

Thanks for the application. Could you add more technical details to the specification of the milestone tables? For example, are you going to use ink! smart contracts? What exactly are you planning to implement for the Auto-Reward System? How do you prevent Sybil attacks, etc.?

@Noc2 Noc2 added the changes requested The team needs to clarify a few things first. label Oct 2, 2023
@howieyoung
Copy link
Author

howieyoung commented Oct 2, 2023

Thanks for the application. Could you add more technical details to the specification of the milestone tables? For example, are you going to use ink! smart contracts? What exactly are you planning to implement for the Auto-Reward System? How do you prevent Sybil attacks, etc.?

Thank you for the questions @Noc2
Considering our team's capacity, we will initially build the smart contracts with Solidity since it is the programming language we are most familiar with. However, we are open to using ink! if we can secure a higher grant level of 3 and obtain more full-time equivalents (FTE).

The auto-reward system will be implemented through our Web3 Lobby, which focuses on user engagement with brands' websites and apps.

Here will the flow be like:

  1. Brands integrate the Web3 Lobby into their products.
  2. Users engage in the lobbies.
  3. Brands use the auto-reward system to reward users based on their engagement in the lobbies.

Regarding the issue of sybil attacks, we will handle each case individually based on the brands' goals and the rewards they set. The rewards will not be in the form of real money, but rather things like memberships or coupons that brands aim to issue as much as possible. However, we will provide brands with options to define rules for how they want the auto-reward system to operate for them. Since these rules will vary widely for each case, we have not included them in the milestone tables. Hopefully, this explanation makes sense to you.

(btw, if we need to dive deeper into the technical part, hopefully we can discuss them in a private space, including this one. Thanks!)

@dsm-w3f dsm-w3f self-assigned this Oct 4, 2023
@dsm-w3f
Copy link
Contributor

dsm-w3f commented Oct 4, 2023

@howieyoung thank you for the grant application. If you want to discuss this application in private, you can select the option "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)" in the PR, and provide a matrix handle, in this way, we can create a channel to discuss this properly. I noticed that you made this same application in private, we can discuss it by e-mail as well. Let us know what is your preference for communication about this grant proposal.

@dsm-w3f dsm-w3f added the discussion private Discussion of application happens in private. label Oct 16, 2023
@github-actions
Copy link
Contributor

The applicant has requested the discussion of the application to happen in a private chat room.

Copy link
Contributor

@dsm-w3f dsm-w3f left a comment

Choose a reason for hiding this comment

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

Changes requested by e-mail.

@dsm-w3f dsm-w3f removed their assignment Oct 27, 2023
@keeganquigley keeganquigley self-assigned this Oct 31, 2023
@keeganquigley
Copy link
Contributor

pinging @howieyoung are you still planning to make the requested changes?

@howieyoung howieyoung closed this by deleting the head repository Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
changes requested The team needs to clarify a few things first. discussion private Discussion of application happens in private.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants