A Kickback "license"

[julien51]

I recently spoke with @makoto and he we discussed the idea of a Kickback License.
The main goal is for Kickback to fund itself using crypto by charging event organizers when they want to deploy their own kickback contract.

Current flow

As detailed on this page, to deploy Kickback contracts, event organizers go to https://kickback.events/create then the Kickback team uses a backend processor which listens to blockchain. When the event contract is created, the Kickback team joins the contract address with the event data in their backend.

Adding Unlock

Unlock is a protocol for memberships. It lets creators like Kickback deploy their own memberships to grant access to some features to paid members only. Users can then easily purchase access to a given membership by sending a payment to the locks directly. In return their receive a NFT (ERC721) which they can use to gain access to custom features.

The Kickback team wants to provide paid benefits for people willing to deploy their own kickback contract. In order to do that, the kickback will deploy one or more locks (one for each level of benefits).
The front-end form will then ensure that the user owns a key to any of the kickback locks in order to deploy their kickback contract. If the user does not have a key, they are offered the ability to purchase a key to any of the lock (either thru crypto or credit card) thru Unlock.

Later the Kickback team can also verify ownership of a key on their backend service in order to guarantee that only the paying members have deployed a kickback contract.

Locks

The Kickback team will own several locks, with different levels of memberships. Each of these locks should have non-transferable keys, as well as having a short expiration date to prevent someone from deploying too many kickback contracts with a single key.

Front-end integration

Unlock provides a JS snippet to integrate on the frontend: https://docs.unlock-protocol.com/ which should be used to ensure that only members can complete the form.

[julien51]

@makoto indicates that the configuration for unlock should be configurable at src/config/env.json (this should be used to set ​unlockProtocolConfig​ )

[nfurfaro]

@julien51 I deployed some locks on Kovan as requested. I can fine-tune tomorrow if needed, but here are the addresses:

Name: Kickback Bronze Supporter
Duration: 3 days
Price: 2 DAI
Max Number of keys:  2^256-1
address: 0xe61607898287220586abE01b536714d8429f675C

Name: Kickback Gold Supporter
Duration: 3 days
Price: 10 DAI
Max Number of keys:  2^256-1
address: 0x2eD8aD6AA973BEA5D60FA70Eead10F113fb4Dc99

Note that in order to price these locks in SAI on the Kovan testnet, I've used this contract address:
https://kovan.etherscan.io/token/0xc4375b7de8af5a38a93548eb8453a498222c4ff2
I've lowered the lock pricing from 20/100 SAI per key to 2/10 per key on the bronze and gold locks respectively. This is just to make it easier for testing purposes. Please reach out if you need Kovan-SAI tokens for testing.

[julien51]

Regarding the user flow, the best approach is to take an inspiration from what is done on this dashbaord provided by Scout: https://scout.cool/unlockprotocol/mainnet

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

This issue now has a funding of 450.0 SAI (450.0 USD @ $1.0/SAI) attached to it.

• If you would like to work on this issue you can 'start work' on the Gitcoin Issue Details page.
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $99,416.47 more funded OSS Work available on the Gitcoin Issue Explorer

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

Work has been started.

These users each claimed they can complete the work by 2 months, 2 weeks ago.
Please review their action plans below:

1) edsonayllon has been approved to start work.

Kickback's a great platform for event reservations, I've used the platform previously. I'll consult with available participants in the Github issue, Julien or Nick, whichever is more available, to ensure all requested functionality is understood, and created as to Kickback's preference and desired user experience. Julien provided an example of user flow, which will be considered as a reference. Unlock functionality will be tested before final integration. I'll consult with the developers of Kickback to ensure the project is going in a direction their team wants as milestones are quickly reached.
2) prakashandrews has applied to start work (Funders only: approve worker | reject worker).

Hi

I have good experience in html, css, javascript, react js. Kindly let me know if i can join as part of development

Learn more on the Gitcoin Issue Details page.

[makoto]

Hello. here is a few updates from Kickback team.

• We expect that applicant has intermediate knowledge of React and React Apollo
• We added contribution style guide so please follow these standards.
• If anything not clear about the business logic specific, please ask questions at the discord channel or in this thread, rather than you guess.

[edsonayllon]

@makoto I've worked extensively with React, and have experience with GraphQL and React Apollo.

Do you have a link to the Discord incase I'm approved? I'm not sure if you mean a Kickback Discord or the Gitcoin Discord, but from the Gitcoin Discord, I see your username is also Makoto. I can message you there if that's your preference.

[julien51]

@edsonayllon you've been approved! Please let us know if you need any help... you can also join the Unlock telegram group: https://t.me/unlockprotocol

[makoto]

https://discord.gg/5YRnfyW is the Kickback channel within gitcoin discord

[gitcoinbot]

@edsonayllon Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[julien51]

@edsonayllon Any progress on your end?

[edsonayllon]

Just to clarify, will paid memberships be replacing, going along side of, or linked within https://kickback.events/create?

[edsonayllon]

PR #220 should be ready.

[gitcoinbot]

@edsonayllon Hello from Gitcoin Core - are you still working on this issue? Please submit a WIP PR or comment back within the next 3 days or you will be removed from this ticket and it will be returned to an ‘Open’ status. Please let us know if you have questions!

• reminder (3 days)
• escalation to mods (6 days)

Funders only: Snooze warnings for 1 day | 3 days | 5 days | 10 days | 100 days

[gitcoinbot]

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

---

Work for 450.0 SAI (450.0 USD @ $1.0/SAI) has been submitted by:

1. @edsonayllon

@julien51 please take a look at the submitted work:

• PR by @edsonayllon

---

• Learn more on the Gitcoin Issue Details page
• Want to chip in? Add your own contribution here.
• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $68,348.23 more funded OSS Work available on the Gitcoin Issue Explorer

[edsonayllon]

@julien51 @jefflau @makoto Received a notification from Gitcoin warning expiration in 2 days. Are there any issues? PR has been ready for 2 weeks

[julien51]

It looks like @makoto has decided to not pursue. I will close the issue and related bounty, but please do get in toch @edsonayllon as both @makoto and I want to make sure you get paid for this work.

[edsonayllon]

Ok. My address is edson.eth. I will reach out on Telegram.

[gitcoinbot]

Issue Status: 1. Open 2. Cancelled

---

The funding of 450.0 SAI (450.0 USD @ $1.0/SAI) attached to this issue has been cancelled by the bounty submitter

• Questions? Checkout Gitcoin Help or the Gitcoin Slack
• $84,680.69 more funded OSS Work available on the Gitcoin Issue Explorer