frankchen07

Keybase proof

I hereby claim:

• I am frankchen07 on github.
• I am frankchen07 (https://keybase.io/frankchen07) on keybase.
• I have a public key ASDeuhlwMeopcg0kP98IkaXLTy-I5JvoygTD9XhEf_7tiAo

To claim this, I am signing this object:

frankchen07

onboarding performance with regards to day over day retention

if we first look at the retention curve, from day 0 all the way to day 20-ish, which represents the full time that we've had the new data collecction onboarding up. Based on all actions, we can see that even on the first or second day, the number of people who come back and retain on our platform drops precipitously to about 20%, and only tapers off from there.

splitting it out by cohort, we see the same. Each set of numbers from left to right is a retention curve.

frankchen07

Do hackathon cohorts who take the time to fill out the intro yield better short and long term retention?

https://metabase.gitcoin.co/question/779

There doesn't seem to be a significant difference between the intro and non-intro cohort. However, that doesn't discount the qualitative benefits of filling out introductiory information (bio) either through the hackathon or within our onboarding. In both cases, it would still enhance our data moat.

There doesn't seem to be enough evidence to suggest that it would massively and directly increase engagement.

frankchen07

Product Epic: Decoupling Projects

Market Networks

Let's start off with what market networks are. From this article, there are several key points and relationships that we can establish. Below are several highlighted passages and how they are critical to Gitcoin:

"Market networks use SaaS workflow software to focus action around longer-term projects, not just a quick transaction."

This essentially is Gitcoin, as we've definitely extended past the transactional relationship of a bounty, and more into relationships centered around communities and projects, which inherently are more collaborative.

frankchen07

Gitcoin Hackathon Retention Analysis

Month over month, we expect our retention curves to move up. This means with every new cohort, we're doing a better job of retaining them on Gitcoin.

We're investigating the lows and highs of our hackathon cohorts, specifically the bright green line, which was our June 2020 hackathon registrant cohort. For 1-month retention, we hit the all time low in this specific cohort. This took place during the Protect your Privacy hack, which was correlated to some of the co-marketing that we did with AngelHack. We got quite a few signups, but our start and submit work conversion rates were low (~10%), which could have been an explanation for low engagement.

Taking the opposite view, we can see that back in 2019, we were doing much better in terms of retention. What changed?

frankchen07

Hey everyone!

Gitcoin Grants Round 7 is coming up. It kicks off on September 15, 2020, and will run for 2.5 weeks, ending on October 2nd, 2020. This will be our biggest round yet, with matching commitments that go beyond $350k!

Here are several of our sponsors:

• $150k from the EF
• $50k from @Arthur_0x
• $100k from yearn
• $50k from #FerretPatrol

frankchen07

Summary of Improvements

1. Grammar update.
2. Added a section to fill out an introduction / bio.
3. Added general interests section.
4. Distilled alot of information about the usefulness of in-depth work profile questions.
5. Removed in-depth work profile questions, simplified multiple questions to one question.
6. Re-ordered profile creation, then interest in developer products, interest in sponsor products.

---

frankchen07

currently, our verified users are determined by these factors:

criteria # 1

sms_verification = true and e.grant_contribution_amount > 1000 then 'verified'

1 makes sense to me as it tells us that you're willing to be "verified" or "identified" by SMS means, and that you're serious about funding open source. The only feedback here is we can figure out the best cut-off threshold for the grant contribution amount and how we want to divvy it up between rounds, or of all time.

criteria # 2

frankchen07

Gitcoin Job Recruitment Feedback

Main Takeaways & Agreements

1. We actually don't have 40k developers, only 2-3K are active at one time.
2. Agree that our data moat is the real way to sustainability monetize, not hackathon deals.
3. Agree with the assessment that hackathons bring in developers.
4. Agree that we hold a unique way of verifying users based on ACTUAL work done, not just resumes and what people can say they do, but ACTUAL actions on our platform, and work that is done.
5. Needed convincing, but can see that building a job portal serves a dual function of organization branding on Gitcoin's site, an incentive for even more developers to come onto our platform to actually create AND populate a legit profile on our site.
6. Re-iterating that our core competency is not only having user data, but being able to build a "project" portfolio on our site (like a LinkedIn + Github that people actually look at wrt live projects and demos).

frankchen07

Gitcoin Hackathon Sponsor Feedback & Conclusions

Problem(s)

1. Paying sponsors don't feel exclusive & special, and feel like they're competing with other sponsors.

   • PoolTogether: "We will use bounties for sure, but probably will post our own hack on Gitcoin."
   • ETC: "I feel like our bounties got croweded out by other sponsors. Aave seemed to have alot of activity."
   • Blockstack: "We're price conscious, that does come into play, if we increase prize and cost of the hackathon, moving forward, if there was a way to host a hackathon, and not partake in the majority of the marketing (2k price tag, vs 6-8k), we would definitely return to Gitcoin."

• Zcash/ECC: "There were so many sponsors in one hack, the ROI was not worth it. What do we actually get at each tier? I expected analytics with the tier we had. The event planning and execution felt adhoc based on the level paid. The event started off strong with customer service, but it petered off hard, it felt like we got less and less servi