Author: Zeugh
Date: (2022-08-12)

Thesis

What’s the idea?

**Context:**


	
	[**EthSafari**](https://ethsafari.xyz/)**:** 

	- will be the first event of it’s size, focused on Ethereum in Africa
	- It’s happening in Kenya focusing in bringing local and international communities together to strengthen the African web3 Ecosystem.
	- They’ve already launched a Juicebox project to get donations and issue tokens for special benefits in the event.
	- Now there’s the possibility of JB being one of the sponsors in the hackathon.

	
	**The Hackathon:**

- is organized by [Encode](https://www.encode.club/), a web3 education community that works with courses, bootcamps, hackathons and accelerator to onboard more builders into web.
- They have done more than 20 hackathons before, with hundreds of people and a community around itself.
- The hackathon will be online and start three weeks before the physical event and end on it’s first days, it will be done with Encode standard structure of mentors and support during their other online hacks.

**My proposal is that we sponsor the hackathon on the value of :**
- 2000 pounds (around 1.26 eth) for a silver sponsorship (see deck [here](https://drive.google.com/file/d/1SH5Xff23u4xwJEsDPjnSUZ4CjX4_SqmS/view?usp=sharing), consider we can change this value for 3000 to get gold and get 2x60 min workshops instead of 1x30min, but it also brings more dev time needed.)
- extra 2500 pounds in DAI and 2500 pounds in JBX(about 900k) as prizes to be split between good projects building with JB

	**Execution:**

- One 30 min workshop to give
- Challenges to choose, which I think will be better thought through in open discussion through this proposal and can be added here in the next 48 hours.
- My suggestions for challenge areas are:
	- Alternative front-end products that can be built over the protocol to offer different specializations to the users.
	- Extension terminals, allowing for different currencies or alternative logics for payment.
	- Integrations from JB to external services, building the composability.
	- General improvements/additions to the current structure that can make JB more efficient to a given public or in a given way.

It’s not mandatory to have our developers on the hack’s server to support hackers, but I think we should have our hackathon channel in the server up again if we do it, or keep using the telegram one.

Motivation

Why now? What problems does this solve?

tl;dr I believe it can bring JB in touch with a nice community of devs and show participants a little bit of JB. Also I see big potential for community funding in crypto when looking beyond the US-Europe axis.

I think Juicebox is super exciting as project, with a strong culture and an amazing team building it. I really believe it can be amazing to present it as a challenge to work with in spaces where hackers new or old to web3 have incentives to take a look on how to work at that and what they can create on top of it.

At the same time EthSafari will have both the local community and Encode communities, bringing a mix of people with different levels of knowledge and experience that can come up with new interesting things.

It also adds for visibility to interesting publics, as the encode hackathons usually have some presence of the sponsor communities (and all of our community is welcome to apply for hacking here if they feel like it). Those communities in the latest hacks include Algorand, Starknet, Chainlink, Wintermute, Ledger, Urbit, Arweave and others. In my perspective it shows a potential interesting community of hackers to be part of us and to be talking our challenges and workshops with.

Specification

How exactly will this be executed? Be specific and leave no ambiguity. This proposal shall be canceled if until the end of temperature check there’s not anyone from the dev team willing to give a workshop for a hackathon about Juicebox protocol in the second week of September.

Make a payout from Juicebox v1 treasury of 7000 pounds worth of ETH(after fees) to Zeugh.eth
Zeugh.eth will swap it for stable coins and cover gas/slippage costs and makes the payment for Encode.
Payout $1000 worth of ETH and $1000 worth of JBX to the wallet of contributor giving the workshop(s)
Zeugh will provide support to the encode team and hack participants on whatever is needed on the side of JuiceboxDAO that is not developer specific.
Juicebox uses the JokeDAO system to vote on their winners on the end of the hack.

Rationale

Why is this specification the best way to address this thesis?

Transfering the sponsorship costs to Zeugh makes it easier to execute the payments, given that we don’t have an LLC nor a formal legal structure, the process of payment with Encode will be a little different than usual so agility and flexibility to trade this value on a individual wallet instead of the multisig will make it easier. It adds risk and is based on trusting Zeugh to execute, but it also leaves them the downside of small sidecosts for it.

To respect everyone’s autonomy and not make a proposal that can’t deliver value properly, this proposal will be cancelled if until the end of temperature check there’s no one interested and capable of giving the workshop.

Risks

What might go wrong?

The hackers might not find juicebox interesting and no one builds anything, in case we get the prize money back.

Zeugh can do whatever he wants with the money when transferred to him and not follow the proposal.

Timeline

When exactly should this proposal take effect? When exactly should this proposal end?

August

Week 3 - Voting of proposal Week 4:

Bounty announcements
Payment of Sponsorship
Payment of Workshop Contributor

September

Week 1 - Hacking Begins Week 2 - Sponsor Workshops Week 3 - Evaluation + Demo Day Week 4 - Payment of Prizes

Thesis#

Motivation#

Specification#

Rationale#