Skip to main content

· 4 min read
Matthew
Brileigh

Building a network of projects on Juicebox

StudioDAO is a decentralized movie studio running on Juicebox. To learn more about how StudioDAO is disrupting the traditional film financing model, check out this deep dive on the JB blog as well as episode 9 of the Juicecast with founder Kenny on Spotify and Apple Podcasts.

In this article, we’ll cover how StudioDAO has created a network to fund multiple film projects with a 10% fee going back to an umbrella project, StudioDAO Backlot. Unlike traditional businesses where money moves with little oversight, when you purchase an NFT to support one of StudioDAO’s projects on Juicebox you can see exactly where funds are being distributed.

Please note that all projects mentioned in this article are currently running on Rinkeby testnet before going live on mainnet and therefore configuration settings are not final.

StudioDAO projects live on Rinkeby 🎥

  • StudioDAO Backlot: registered LLC that provides film production services to StudioDAO and takes a 10% transaction fee on all StudioDAO project NFTs sold through Juicebox
  • Unlikely Love Stories: StudioDAO’s first project, a dark comedy anthology by Rosa Tran and Derek Smith
  • Colossi Research Academy: test project with art by Michael French
  • Dickson Greeting: test project, experimental historical short film

StudioDAO Project Map

StudioDAO sub-project map

Case Study: Unlikely Love Stories ❣️

StudioDAO’s first film fundraise is Unlikely Love Stories, a dark comedy anthology by Rosa Tran and Derek Smith that explores finding unexpected love in the most unexpected places. In the screenshot below, you can see that ~ 13 ETH has gone into the treasury, and 10% of those funds will be distributed to “Project 4630” also known as StudioDAO Backlot, the Juicebox project that supports all StudioDAO films through production-related services. The other 90% is distributed to the filmmakers (unlikelylovestories.eth) along with the Backlot tokens minted from the 10% payout.

StudioDAO Funding Distribution

Funding distribution for Unlikely Love Stories on Rinkeby

Understanding the project’s configuration settings 🔎

Digging further into the project’s config, we can see that the following choices were made:

  • With automated funding cycles disabled, funds can be withdrawn at any time. For the project creator this is a very flexible approach but it also presents risks for project contributors.
  • Similarly, an infinite distribution limit was set meaning that the project can distribute freely from its treasury, as much or as little as it likes. Again, this is a very flexible strategy but also means that the entire treasury can be distributed without any limits.
  • Discount Rate is set to 0% which means that token issuance will stay the same over time. In other words, there is no added incentive for early contributors.
  • Redemption Rate is set to 100% which means that they can be redeemed against the overflow of the treasury at any time. In other words, there is no added value for redeeming earlier vs. later.
  • Mint Rate is 840,000 tokens per 1 ETH, with half for project contributors (420,000) and half for addresses on the reserved token list (420,000) 🚬
  • Owner token minting is disabled, so the project owners cannot mint tokens at any time. Only project contributions will mint new tokens.
  • No reconfiguration strategy was set, meaning that a project can be reconfigured at any time without notifying contributors. Again, this is a very flexible approach for project creators but carries risk for project contributors.

StudioDAO Funding cycle configuration

Funding cycle configuration for Unlikely Love Stories on Rinkeby

Reserved token allocation 🪙

We can also take a look at how the Reserved Tokens are split:

  • 50% to filmmakers of the project
  • 40% to StudioDAO Community wallet
  • 10% to StudioDAO Backlot

This cross-pollination of tokens allows each member of the StudioDAO ecosystem to have a stake in one another, creating incentive alignment and building community in the process.

StudioDAO Reserved Token Allocation

Reserved token allocation for Unlikely Love Stories on Rinkeby

As mentioned earlier, all projects discussed in this article are still on Rinkeby testnet and their configuration settings are not final. Once StudioDAO and NFT Rewards are live on mainnet, we’ll update this article with the final configuration details. Stay tuned!

Coming soon to a mainnet near you.

That's all folks!

🎙️ Listen to Kenny tell the story of StudioDAO on episode 9 of the Juicecast on Spotify and Apple Podcasts

🟢 Follow StudioDAO on Twitter: @studioDao

💬 Join StudioDAO’s Discord: https://discord.com/invite/YxPGn9pcdr

🐦 Follow Juicebox on Twitter: @JuiceboxETH

🚀 Trending projects on Juicebox

📚 Project Creator Docs

📹 YouTube Tutorials

· 9 min read
Zhape

Town Hall banner by Sage Kellyn
Art by Sage Kellyn

Capsules project with peri

The Capsules is peri's latest project of on-chain typeface that he launched just one day before this town hall.

This project of on-chain typeface introduces a standard to make it easy to store fonts on-chain. There're a lot of projects that use text in on-chain rendered SVGs these days, but if they want to use a custom font in an on-chain rendered SVG, they need to find a way to store that font on-chain. Also storing fonts on-chain is expensive and complicated, and there isn't a standard way to do it. For this reason, Capsules project introduces a new typeface contract interface in order to standardize storing fonts and make it easier to access.

Together with the launch of this project, peri also put out some NFTs as a Proof of Concept experiment for fonts, by which he tried to educate users how to load fonts from a typeface using this contract and throw them into an SVG which in turn gets rendered on-chain. There're altogether 7,957 Capsules NFTs with each one of them having a unique color, while users can only mint each color once. Users can edit the text of the NFTs and it gets rendered in the Capsules typeface.

People can also download the typeface here for free if they want, together with its variable fonts, which is pretty cool.

The typeface contract allows you to define the typefaces even when you deploy a contract without storing all the data for them, which means anybody else can just come and store the data, provided it matches what you define in the first place.

For this project, there are 7 special pure color NFTs that goes to people who store the 7 fonts 100 to 700. Folks from around the Juicebox ecosystem got news of this launch and stored all of them in just couple of minutes, which is a very decentralized effort to get some new infrasturcture onto the blockchain.

Definitely follow peri on Twitter to get more first hand info and all his genius ideas!

Nicholas also managed to make a prototype using the Capsules typeface to render some active data of a Juicebox project.

And filipv downloaded the Capsules fonts and set his terminal font to them, which is super super cool.

Versioning update with jango

Jango and his team launched the V3 contracts in the morning of this town hall.

In the past week, we had another Code4rena audit contest of mitigation review over the updated V3 contracts. After this contest, the team deployed all the contracts again except for the JBProjects and JBOperatorStotre, which means projects currently have their project NFTs will keep their project IDs and they can choose whether or not to deploy a V3 funding cycle and token that syncs to their V2 versions, while all new projects will be built on V3 contracts.

Dr.Gorilla and 0xBA5ED have done a lot of work for testing and solving some very complicated problems along the way.

V3 contracts are essentially a mitigation of a few bugs discovered in the previous Code4rena audit contest in V2 contracts. The most impactful one of these bugs was that project owners can set a start time of their funding cycle in a certain way to overflow the storage of that piece of data, essentially allowing them to create a funding cycle at arbitrary points of time and mess up the schedule of things. With the assumption that community relies on project owner to be honest, we try to create as many levers as possible to at least give project owners the ability to lock themselves into things, but this bug would in a sense allow some unforseen reconfigurations if for some reason project owner and the community were no longer aligned in interest.

It is just a fringe case, either it could have been patched with a new payment terminal controller, or contract crew could have made edit in the JBFundingCycleStore to fix it. But it makes a lot more sense that people about to build projects on Juicebox want to be building on the best version of contracts possible, so the team did the V3 contracts and made changes in the JBFundingCycleStore.

The next move is to extend what was previously a V1 to V2 token migration terminal to be more generalized, so that projects can deploy a new funding cycle and toke if needed and make the move across as they wish. But the V2 contract will keep working and all the stuff there is solid.

It's really nice to have a versioning pattern ahead of time when things are still pretty slow these days. Both contract and frontend teams were taking this opportunity to create decent standards for projects to use to implement major-version migration in the future if any problem arises.

nicholas: If people have their V2 projects right now, should they be worried about it sitting on V2?

jango: No. We've talked to all projects willing to communicate about it and make them aware that the audit contest has been wrapping up, and the broad base of projects has already had trust vectors established between project owners and the communities, so it should be fine.

nicholas: Is there a timeline for the feature of token swap?

jango: We current have this mental model that people paying ETH and they will receive project tokens, so projects might also use it to receive the old version of their project tokens and then issue a current version of token back out at a rate of 1:1. Under the hood, it looks like a payment terminal, and also in the frontend there's going to be a settings module to make the process easier for projects to do it.

Stay tuned for updates on all the work of the versioning stuff. The next thing for us will be to figure out how to deliver effectively. We have a lot of prototypes of this at the finish line, but given this V3 deployment, we want to make it work from V1 to V3, and from V2 to V3.

And there's some cool stuff we can do with extensions in V3. You can make pay delegates that receive part of the funds before they go into the treasury. This is a new feature that no one has used yet, and we're building the first one with the NFT Rewards, because we found that it would be really useful if some of the payment could be routed directly to a delegate. You can run arbitrary contracts that actually receive parts of the funds paid in, and the same with redemption, in which you can run delegates that receive part of the reclaimed funds automatically.

The GitHub repository of V3 contracts can be found here

Visibility updates with brileigh and matthewbrooks

Juicenews newsletter

The new release of Juicebox newsletter can be found here

Config articles

The config articles are going to run through how a project is configured and some of reasons for those decisions made, to help new project creators understand why certain projects are using a different configurations and why they're making those decisions. So if new project creators want to build a similar project, they can look to that article as a reference point for their own project.

Brileigh and Matthew just launched their first config article here.

Juicecast (Juicebox Podcast)

They recorded a new Juicecast episode with 0xSTVG about his project Marin Swim County Association, this episode will be released later this week.

They also made a video interview with David Phelps, the founder of JokeDAO, which they plan to upload to Juicebox Youtube channel later.

Work Plans

  • Another video interview with Robin from Defiant about creator economy.
  • A retrospective deepdive on ConstitutionDAO.

They also have the plan of making a series of podcast featuring some famous/symbolic projects of Juicebox such as ConstitutionDAO or MoonDAO, coupled with some long articles that go through the history of them, as well as some config articles about how these projects were set up which will certainly be reference points for new project creators.

Interface with sunnndayyy

Interface is a mobile APP that allows you to follow your friend's wallet, lays out all the information in the feed like a social Etherscan and lets you surf Web3 with a better UI.

Interface community has recently transitioned to a DAO, with a hybrid model between the Labs and the DAO. And they want to start doing some interviews and learning about progressive decentralization publicly. So they're looking to hold a series of Twitter Space on the challenges of decentralized coordination and stuff like that over the next few month.

They feel there will be no better community to talk to about these topics than Juicebox, so they want to invite the core contributors of JuiceboxDAO as their first guests to discuss on how to activate participation in governance in the early stage in a project's lifespan.

sunnndayyy also introduced that this APP is still in a closed beta version, so if people want to download it to try using it, they have to go to their website to sign up for early access.

G-Play updates with Sayid

G-Play is a Juicebox project of P2E gaming platform where users can stake $Matics to play with each other on Polygon.

Recently they started their beta testing and onboarded their first users to the platform.

One of the new features they have, is a statistics page that shows how much the users have unclaimed $Matic they can withdraw.

Sayid and Mieos played a game to demostrate how the game goes on the town hall.

As now it seems a little troublesome to buy $Matic on exchanges and bridge it to the Polygon Mainnet, Sayid also announced a 500 $Matic scholarship so that users can use the built-in request function to ask for $Matic from them.

Two Truths And A Lie with Felixander

The correct answer is ... Viraz.

Forming event Vol III with darbytrash

Lexicon Devils are going to host a new Forming Vol. III event, FLOPPY x FORMING, on Sept. 24th 3pm PST, which will have 3 musical performaces and a FLOPPY walkthrough, at the Juicebox HQ in VOXELS.

The stage is set, welcome to join us then!

· 14 min read
Zhape

Town Hall banner by Sage Kellyn
Art by Sage Kellyn

versioning with jango

Contract crew has finished the versioning project, created the Juicebox contracts V3 repository and merged everying inside, before the repo was passed onto some wardens in Code4rena to implement a mitigation review for updates made with findings from last Code4rena audit contest.

Jango said the mitigation review will probably last for a week, and encouraged our community to stay tuned and help out with any questions or feedback that externat auditors might have.

A big work now will be working together with Peel to finalized what UX we should use to get new projects to use the V3 conract.

Projects that are currently operating under V2 will have the choice of deploying a V3 funding cycle and synchronizing, then deprecating their v2 version funding cycle. We will provide instructions for that process. But in this case, the communities of these projects will have to go through a token swap transaction, which isn't entirely ideal. If there are projects that don't want to go through this trouble, we'll deploy an ETH payment terminal and a JBController for them to migrate their current payment terminal and controller to.

For those who want to stay on V2, they're welcome to do so, it'll just be a little bit more follow-on work from contract crew.

Huge shoutout to Dr.Gorilla and 0xBA5ED for coming through and helping out in the last serveral weeks, and big shoutout to 0xBA5ED for a really intuitive solution to a little rounding error that we were dealing with last week.

juicebox.money Next Gen UI with Strath

The frontend team found out that the biggest pain point for our users, which impacts Juicebox most and make it suffer from a very high dropoff rate, is the project creation flow. After some user testing and behavior analytics, our team finally went through the way to simplify this process and make it a more enjoyable experience to get people launch their project on Mainnet.

Strath was sharing his screen and showcasing the improved UI design

The biggest feedback they had was the step 2 of the 3 steps in the current creation flow, the Funding cycles which is some kind of tiered approach and has a lot to go through. current flow

They are trying to break it down to simplify everything, get rid of the cognitive load and give people the ability to make one big decision per page.

Here's what the improved UI looks like: new flow

And Strath was explaining the tabs in the new UI one by one.

Here is the Figma page if people want to leave their comments on this work.

This is not 100% complete and there're some small elements still being worked on. They will do some user testing, so there'll probably be iterations on it down the line.

There will also be some templates, so people can select the template and just go from there, instead of needing to jump into the creation flow.

Q: Do you have any plans or any prototype for allowing a user to launch terminals from there, like custom ERC-20 terminals?

Aeolian: It's quite an easy thing to create, but the main issue is what do we do on the project page, which still need to be conceptualized what it looks like for a project to have multiple terminals. That's probably the next big design project.

Jango: I even wonder if that's in the purview of juicebox.money to experiment with, because there're a lot of ways to go about this. It seems all this stuff is best to serve as an experiment with a juicebox.money fork or something that specifically tailored towards those use cases, and finding out how to fold that in nicely will be interesting.

It gets a little complicated, but it does provide particular accounting niceties if you really want those terminals. I think, from a protocol perspective we can make sense of these logically, but from a UX perspective it will take some work really figuring out what the priorities are.

Two truths and a lie with Felixander

TwoTruthOneLie

The correct answer is 0xBA5ED.

No.3 about the socks is a lie.

MTOTM AMA with epowell101 and Michaelmaher

Background and concept

Epowell101: This concept of MTOTM started with some lived experience and some conversations they had with some early DAOs and DAOs founders, in a sense that there's a need for additional diversification early on instead of waiting untils much later and needing an OTC desk to do the swaps or to negotiate for over months.

What if we, a bunch of DAOs at their very earliest stages, pitch in to a shared pool(Juicebox in this case) and get back a token that represents percentage of the meta DAO that we have just created. So you get some diversification and also some meta governance in which you get certain number of other DAOs who are care about how you're doing and potentially could be an independent voice in your Discord or in your governance to provide an independent perspective.

As we all know, there're a lot of launchpads out there and maybe lots of use cases, but we realized that we should focus on the primitive of DAOs pitching in and getting back while referring to an oracle to get the ratio. That's where we needed a name for this concept and we came up with MTOTM( \ˈemˈtō-təm\ ), which is supposed to stand for Many To One To Many Swap.

jango: To add a little context, we're leveraging these custom payment terminals to basically accept project tokens back into them and issue another project token outwardly, and that's kind of how it ties into the infrastructure that we're working on, the protocol developers are working on. It's cool that it's scoped into its own project and has its own application, but from the primitive perspective, as everyone was saying, it's nice to use these familiar pay functions in token issuance practices.

nicholas: If I'm getting part of the ideas, it's like token swaps between DAOs and also potentially collecting token for many different DAOs and generating one token that is the representation of all those different tokens in one index fund, which allow you to do interesting things and mutually incent each other. Is that the idea?

epowell101: Yeah, that's exactly it.

Explanation of mechanism

michaelmaher shared a GIF file in the town hall channel:

MTOTM animation

michaelmaher: At the base of everything is the extensive use, if we all are using ERC-20 terminals to facilitate this process because what the DAOs pitching in will most likely be ERC-20 tokens, we'll have to navigate the use of these terminals to facilitake DAOs coming into an index, creating that index and spitting tokens back out to them.

With that, there's the ability to use different price feeds, using the Juicebox protocol. If a DAO's ERC-20 tokens coming in and they don't have a current price feed, probably because they are not traded on a DEX, we can set up custom price feeds as well.

But we also want to encompass it in the tradtional Juicebox project architecture, by using a regular project that can receive ETH and manipulate some different split data to send it out to other addresses.

Investors want to come in and spend their ETH to get an index token in the initial raise, and DAOs will also come in and get their DAO tokens in the swap. So all the swap needs to happen under the same umbrella, and that's really what MTOTM is about.

We also don't want to dilute the initial investors either. When they're coming in with ETH expecting some amount of tokens back, we want to make sure that's kept true till when the DAOs are coming in.

We're looking forward to developing some other terminals especially for this use. When you've got multiple projects coming in, you have to launch a terminal per project. Of course, that's not the most gas efficient thing, so we're also looking to help build some multi-token terminals , where you have one terminal and a bunch of tokens can come into it and help facilitate the whole process.

And the final part will be how to distribute everything. ETH will be distributed in a traditional way most Juicebox projects do and routed to the DAOs because it's a way of fundraising.

When you look at that GIF image, the whole point is to make it very simple for the users, and to have all the complexity under the hood.

Community support

jango: Shoutout to you all for really figuring out how all these interfaces work and getting a sense that this can be pulled off with the network's treasuries that we've got going here.

I think there hasn't been full time attention from a lot of the folks that really know the protocol intimately well and have built it, you all really are carrying the load and understanding how things work and prototyping and asking really good questions very frequently, much appreciate it. Hopefully as we wrap up some of the work that we've already committed to, such as versioning, NFT Rewards and stuff over the next few months, we'll be able to be more hands-on and take this through the finish line to some MVP so that we can actually see this animation play out on a website.

michaelmaher: If anyone is interested in the project, you can check out our GitHub repo. And also welcome to join our Discord server and let us know what you think.

jango: There was a grant proposal to help sustain and fund those research this past round, which didn't meet the quorum in temperature check. A lot of this type of research work is more in the background and not really in everyone's face frequently, we are trying to figure out better ways to really highlight developers from around the ecosystem who have been working on it consistently.

I think this is one of the cases that we may not have a full thing ready to go in the near future. There's been a lot of understanding of how things work and prototyping how to really push the limits of how things might work, which is exciting to me. I would love to see it supported, and obviously the best way to support is just being around and helping to answer question and prototype and actually pull the thing off. It does take time and attention, we know that it's hard to prioritize things, but be on the lookout for grants of this nature going forward.

Further discussions

nicholas: Let me run through this once more to make sure I got it clear. So the impetus is twofold:

  1. to allow DAOs to swap tokens with one another, by making contributions of their own DAO's token to another DAO's Juicebox project and receiving that DAO's tokens in exchange
  2. to enable the creation of an index fund and the fundraising for all of the DAOs that contributed their project tokens to this index fund so they can collect ETH.

Is that a good summary of the motivation?

epowell101: The DAOs and investors will all get back the same tokens that created by the meta DAO, but the DAOs will also get the ETH.

jango: I think the main thing from my perspective that is important to note is that right now we have an ETH payment terminal and a generic ERC-20 payment terminal. The ETH payment terminal is deployed and leveraged by juicebox.money. The other one is an ERC-20 payment terminal, let's say DAI, and that would work the same way.

You would issue a rate at which project tokens are issued out when one DAI comes in. If you run both an ETH terminal and a DAI terminal, you want to have the project token issuance rate be only correlated to one of these assets. Let's say 1 ETH comes in 1,000,000 tokens go out, and 1 ETH worth of DAI comes in 1,000,000 tokens go out. Now you can imagine a project token version of the ERC-20 terminal. One project's tokens get issued at some rate of the external project tokens coming in.

The interesting part is the price feeds. At what rate tokens get issued out when something comes in, and how does that relates to other terminals you are also using? That requires you to write price feeds and payment terminals. And then how do you write multiple payment terminals that can generalize this so that you don't have to deploy a new payment terminal for every project that wants to use this? You don't deploy a DAI terminal and then a SHARK, PEOPLE and JBX terminal each time. You can just have a generalized version of this, which is also an interesting problem here.

nicholas: So let's say you have a multi-token terminal that accepts SHARK, PEEL, CANU and WAGMI to create a Juicebox ecosystem index, it would not just have static rates for each of those versus the project's own token, but instead variable rates depending on the value of thos project tokens, right?

michaelmaher: Depending on the value of thos tokens, but some projects might be in their super early stage and we might negotiate a price to start, so maybe they all will have the same price. There're a lot of different ways in basically working with the prices contract set up in Juicebox.

nicholas: So the first step on the roadmap is this multi-token payment terminal to enable some of those ideas we talked about.

jango: I think the multi terminal is how you automate a lot of the operation overhead to set this up manually. I think the manual first step is to have one terminal per project token that's facilitating this, and to have prices feeds and everything plugged in, and the expectations are all set and things are well tested. And then the next step is to automate the operation overhead.

michaelmaher: Yes, we've been trying to develop the multi-token termianl and that's still in progress, so that's more of a future what this can be.

epowell101: We have stood up on testnet versions of this using the single token terminal, it's going to be very simple, because we just want to get to the MVP, but there's some UX work got starting as well.

Kmac: Isn't it an index built on token set?

michaelmaher: Okay, they kind of do this, but the reason that we're trying to be different from them is that they have these certain stipulations within a token set. One is that you have to be listed on a DEX platform or have some type of liquidity, so you have to have a pretty well launched token. Early stage projects are not going to pass that set protocol if they want to join. Also there is no real governance built in with that, you get this kind of index token per se, but the governance of that doesn't really work well. So to us, this is a different niche product that can facilitate a lot more projects out there.

jango: Lastly, just to emphasize is that this is an experiment, and there's a lot of unknowns, a lot of open questions. So let's ask those and let's hypothesize and talk about them. Who knows if it has longevity, but I think it's worth. I think there's definitely applications of this or derivatives of this concept that can be quite powerful.

· 9 min read
Felixander

“Juicebox in the words of” is a series that highlights JB community members in interview form. Learn about members’ roles at JB and what makes them tick.

Matthewbrooks.eth is 1/2 of the Juicecast, and 1/1 a perfect gentlemen who wears many hats at JB. Between tracking payouts and creating governance recaps on a weekly basis, he also fashions a short-form newsletter for JB along with his other half, Brileigh.eth. This unassuming and kind contributor joined me for a talk about all things JB. The only downside of this article is that the written words strips Matthew of his silky smooth voice, which has been known to melt hearts and ears alike. Read to the end for a big surprise ; )

So tell me your Juicebox origin story and what appealed to you about JB?

Basically, as usual it was a nicholas origin story, as it always seems to be. I knew nicholas several years ago, before crypto, and I was following him on twitter Then maybe a year and a half ago I got into the space. Nicholas was involved with Juicebox at that time and I saw him tweeting about it. I bought a tiny bit of JBX but I was a bit too green to really be involved with a DAO or contribute for one, so I was mostly a spectator.

Then Briliegh and I started working for DAOs in like Feb/March of this year, and we noticed that nicholas was no longer running the JB podcast. We thought it would be fun to pick up the mantle, ie take the baton of the JB podcast relay race, so we did a test episode and did some trial payouts, and now we’re doing that full time, and writing on the blog, and doing the newsletter.

You’re also getting into some record keeping work, between the gov recaps, payouts tables, etc. Not the same skillset as podcasting at all, and you’re crushing it. Where did that come from?

Hmm.. I have to say, gulan and twodam are doing the heavy lifting on that stuff. I’m a very small cog in that machine. In terms of where it came from, when we stated working for RawDAO in March, we did bookkeeping, which was way less complicated than what JB does. Over there we were just managing a spreadsheet. One day aeolian posted that it would be helpful to have a notion table of all contributors currently being paid with a link to snapshot/discord handles etc., and we started doing that just to help out.

The governance recap I feel like is kind of a selfish thing. I just found that I needed a one-stop shop summary of all the proposals. I was gonna do it anyway, since I needed to vote, so I figured if I was doing that for my own purposes, then I might as well just tweet that out as a useful thing that I could do for the community. It’s a small gesture but I enjoy doing it!

It’s much appreciated! Regarding your personal projects, I know you’ve got an extensive background in photography. What are you working on, if anything at the moment?

Yeah, I studied photography and got a degree in it, and right now I teach photography at university, but to be honest I don’t want to keep doing it. I signed a contract and will finish it out, but I’m not passionate about it anymore.

Both me and Brileigh have backgrounds as practicing artists/fine art photographers. We’ve both made projects and minted NFTs (which we’ll continue doing), but I think our relationship to photography used to be one where we did photography for a living, and I think we both got frustrated working in an art context for many different reasons. One is the type of people who work in art and culture, and one is, to put it bluntly, the type of money you can make in those fields as well.

So we’re both kind of moving on from that as a sector that we want to work in. But we’re still gonna keep making work that we wanna make. We’re just gonna do other things for work, which is why we’re trying to get more involved with JB. We’re also both learning to code and hope to take on more technical roles over time.

In terms of a project I’m working on, while I’m not actively working on a project at the moment, I do have a lot of things I need to scan from my archive, like I have a lot of negatives that I have to scan before my tenure is over at the Uni. So I look forward to releasing some of the work I’ve made over the past few years before the pandemic as I get to scanning it.

Gotta make the most out of that lab access. Are they tracking your scans or can you just go to town while you’re there.

The way uni’s work, you either have access or you don’t, and right now fortunately I have access, so I gotta make the most of it. So yeah, we’ve been drum scanning all of our film. Basically it would cost 100 bucks per scan otherwise.

One scan is one image?

Yes.

Jesus, that’s insane.

Yeah, no way to do it on our own with that kind of cost. So we’re just trying to jump on it before I lose my access when the term ends.

With universities it’s almost like a breakup. I used to work in a lab and it was the same way. Full access, no questions asked, then the second my term ended, it was like the lab and I were perfect strangers. Are there any things you’re looking forward to photographing after you’re done with all your scans?

I have a couple projects I’d like to do. I want to photograph quantum computers. They look like these really crazy scifi gizmos—

Gizmos is a technical term, right? Trying to remember it’s latin counterpart.

Gizmodus.

Gizmodus, haha, of course. How could I forgot. So what’s the deal with these quantum computers?

They’re really unique looking, like a prop made for a sci-fi movie or something. They have these weird fucking tubes everywhere. There’s a quantum computing research program happening a few hours from where I live and I think the images would be an interesting mix of documentary and fiction.

Very cool. Which JB contributor would you want to do a portrait of?

Like a photography portrait?

Yes. If you had to Anne Leibowitz the shit outta somebody at JB, who would it be?

I’ll give multiple answers. I think tankbottoms for sure because… well, I love tank, I wanna be tank when I grow up. I would love to have a beautiful portrait of tank in natural light, like a Vermeer painting.

What about tank in the clamshell, Venus De Milo style?

That could work too, definitely.

What other contributors do you think you’d zero in on?

Hmm… That’s a tough one. After meeting so many in NYC—

You were uninspired?

No I was very inspired! A lot of people were dressed differently than you might have imagined. I’m thinking of jango and his flip flops... this guy doing all this smart contract development, very technical, and just so laid back in flip flops hanging out. So maybe a super serious Rineke Dijkstra style portrait of jango in his flip flops and tank top is one I’d love to do.

Amazing. Who’s your favorite contributor and why is it jigglyjams?

Oh jigglyjams, he’s awesome. The nance bot, all that shit, is so good. I have a ton of respect for jigglyjams, he has a good vibe. Every time he talks he has such a pleasant voice. All that automation he’s working on is incredibly important for JB. Big shotout to jigglyjams and nance for sure.

What should we keep an eye on about you? What’s on the horizon?

You mean like at JB?

Not even just JB. We can get personal. Wedding? Kids? This is a safe space to share.

I have… okay, I’ll just say it, we have actually discussed this. It would be very cool for there to be a JB wedding at some point. I think it would be a wonderful get together that could be very weird. So def stay tuned for that.

Whoa! That’s a huge thing to say. For real?

Yeah, for real, stay tuned! Also I do think that using JB as a wedding registry would be an amazing use case. Like a 2-in-1 way to use JB and also throw a banny themed wedding.

You’re giving me the scoop here man, this is big news. It would be bonkers to have a JB wedding.

I think it would be amazing, I know at least for us the NFTNYC event was something very special, and I think linking up the discord and twitter PFPs with the people was a particularly bizarre experience, but very good. We could take that one step further and introduce a lot more alcohol and speeches and formal dress.

That’s awesome. As far as I know wedding registry project has never happened?

I don’t think so, but I think it makes a lot of sense. Even just the wedding itself could be a JB project.

Thinking out loud, I like the idea of the redemption rate changing the longer the marriage is successful, like a wild kind of way to reward contributors who staked in your relationship success longer.

Haha, yeah that would be wild. Who knows?

Oh man, well this is super exciting. Thank you for the time Matthew and I’m def down for a JB wedding!

For sure, take care!

· 6 min read
Matthew
Brileigh

How StudioDAO is building the first million person green-light committee on Juicebox.

🥱 Prequels, sequels, reboots

If you’ve streamed movies recently, you might have noticed that everything is starting to become homogenized. Superhero mix and match, cinderella with the latest celebrity, maybe an apocalypse or two. It’s becoming increasingly clear that we are no longer paving new roads but rather returning to the same old well-trodden paths. The traditional studio model behind film production is, at least, partly to blame for this. And StudioDAO is trying to fix it.

These constant reboots are often favoured over new ideas that seem like too much of a risk to investors. And to make matters worse, the filmmakers don’t reap nearly as much profits as the financiers. Here is how films are funded in the traditional studio model:

  • Filmmakers create a budget and pitch their film to financiers
  • Financiers provide funding, get repaid once the film is made, and get an extra 20-30% of the films profit
  • Financiers then receive ~ 50% of all revenue going forward and the filmmakers the other 50%

Other than the exorbitant take rates (50%? hmmm…), the problem is that financiers are assuming the risk of the success of the film. In other words, they are not incentivized to invest in new films without a proven track record and are much more amenable to franchises with successful past releases. This has lead to the franchise overload that we are currently experiencing where every movie in theaters or on streaming platforms seems to be a prequel, sequel, or reboot.

🟢 Enter StudioDAO, stage left

StudioDAO

Rather than relying on a centralized financier, StudioDAO is a decentralized movie studio working to become the first million person committee of fans green-lighting movies. By combining the power of collective action with NFT sales to fund films, anyone can participate regardless if they have 0.01, 0.1, or 1 ETH to contribute. For the first time ever the audience will have the opportunity to decide which films they want to fund and watch, all while building community and gaining behind-the-scenes access in the process.

Our goal is to have a million people come together to fund a movie for the price of a movie ticket

— Kenny

💸 StudioDAO’s hybrid funding model

While the idea behind StudioDAO is simple—fans coming together to fund films—their innovative funding model is complex, so let’s break it down. StudioDAO has three methods for funding films:

1) Retail NFTs

Using Juicebox’s new NFT rewards feature (coming soon to a mainnet near you), anyone can support projects at three different price points: 0.01, 0.1, and 1 ETH. These NFTs help fund the film’s production budget and are also collectibles that grant governance rights to the StudioDAO community wallet.

2) Community wallet

The StudioDAO treasury receives 30% of profits from projects. This community wallet is controlled by members of the DAO and can help fill in the gaps for films in the StudioDAO network that are raising funds for production. This process democratizes the experience of movie production by allowing DAO members to vote on which films should receive treasury funds.

3) Film financing fund

Last but not least, this method opens the door to the traditional financing world outside of NFTs and the crypto community. This fund requires investors to KYC and work together with the StudioDAO community to reach an agreement.

🎬 How does this work for filmmakers?

  • Filmmakers receive 70% of all profits made from their films;
  • Retain ownership of their film;
  • Control the distribution of their film

A DAO member will act as a filmmaker’s representative, make a pitch to the DAO on their behalf, and seek approval via governance. All DAO members are able to create and vote on proposals, allowing the community to curate content and vote on which films they want to see come to life. Once the vote gets approved, the DAO opens a new Juicebox project with three funding tiers and fundraising begins.

Unlikely Love Stories

❤️ StudioDAO’s first project: Unlikely Love Stories

Unlikely Love Stories is a dark comedy animated anthology that explores the highest highs and lowest lows of unexpected love in the most unexpected places. The anthology is inspired by the real life love story of Oscar-nominated producer Rosa Tran (Anomalisa, Robot Chicken) and Emmy-winning VFX artist Derek Smith who met at the 2010 Emmy awards and fell in love 7 dates later. Part 1: Tender Vittles tells a hilarious, slightly fucked up story about love when a sweet mouse falls in love with a dangerous yet delicious gingerbread cookie.

The first goal for Unlikely Love Stories is to raise $305,000 USD for the pilot episode Tender Vittles. To continue the anthology, the project will be aiming to raise $2,000,000 USD to produce a half season and $5,000,000 USD to fund the entire season. 90% of proceeds go towards funding the project and 10% goes to the StudioDAO community fund governed by DAO members.

Unlikely Love Stories NFT reward tiers

🧃 A transparent way forward

The idea of crowdfunding films isn’t new: Kickstarter has helped raise $500M USD for films over the last ten years, including 5.7 million for Veronica Mars in 2019. Fast forward to 2022, crowdfunding on Ethereum has opened up new ways for fans around the world to support films, like filmmaker Miguel Faus who crowdfunded his film Calladita with tiered NFTs. Going one step further than a one-time fundraise, StudioDAO is building a regenerative model in which project creators get to make their dream projects while fans get unprecedented access to the green-lighting process. And all of this magic happens transparently and out in the open on Juicebox.

There is a two trillion dollar entertainment market and there is a clear scenario for a decentralized studio to do one billion dollars of production 3-4 years from now.

— Kenny

🎙️ Listen to Kenny tell the story of StudioDAO on episode 9 of the Juicecast on Spotify and Apple Podcasts

🟢 Follow StudioDAO on Twitter: @studioDao

💬 Join StudioDAO’s Discord: https://discord.com/invite/YxPGn9pcdr

🐦 Follow Juicebox on Twitter: @JuiceboxETH

🚀 Trending projects on Juicebox

📚 Project Creator Docs

📹 YouTube Tutorials

· 13 min read
Zhape

Town Hall banner by Sage Kellyn
Art by Sage Kellyn

Versioning with @jango

This versioning project is a prerequisite for almost all the other protocol things, and mostly everything of it is complete now.

After the Code4rena auditing contest, there're a few changes need to be made to the protocol to ensure the protocol's risk aversion and longevity. Jango is leading the work now instead of waiting and patching problems that might rise later. A lot of the changes don't really affect the V2 features set, and everything is pretty much finalized at this moment.

The next step is to run another Code4rena contest on the updated repo. Jango is trying to get a mitigation review for the past Code4rena audit, which is to check the changes to the codes from the results of that audit, hopefully by same group of wardens from Code4rena.

The Juicebox projects contract won't be changed. This version won't be a requirement for all existing projects, which mostly won't ever run into some of the inefficiencies discovered. But new projects going to be build will use this new version.

Frontend has deployed a new settings page, a revamped and powerful settings page for Juicebox projects in the juicebox.money site last week, we'll leverage that to give project owners some confidence over how they're managing their treasuries across versions.

New settings menu on juicebox.money

In our chats, we're calling this contracts update V3 but it shouldn't be taken as another major version as V2 was to V1.

@nicholas has been exploring, with as @trebien our main contact to Code4rena, a longer term cooperation with them, by which we can get preferable rates and more flexible contests.

Nicholas has put up a proposal for a larger budget for six months or a year for Code4rena contests, if passed, we can do many smaller contests as necessary for things like the NFT Rewards or small updates to the protocol.

The draft of this proposal can be found here, and the Discord discussion happens here.

NFT Rewards might also be rolled out at the same time, unless the community insists on having it go through Code4rena as well. The NFT Rewards is something that the devs can propose new ones at any time and projects can use updated version for their subsequent funding cycles.

Immunefi bug bounty

@filipv wondered if we have a timeline for the Immunefi auditing and testing for the updated contracts. @jango thinks the Immunefi is less about auditing and testing, but more about bounties for hackers to choose to report vulnerabilities instead of exploiting them. He thinks what we offer most projects to build using Juicebox is the infrastructure as a service with the security model coming with it, but as the protocol grows and our day-to-day operations decreases, there might be a need to designate someone as an insurance mechanism.

@nicholas explained that the proposal we approved before to create a $100,000 Immunefi bounty has expired, for the reason of not implementing it within the contraints of that proposal which had a deadline. He also thinks we might consider change a service provider other than Immunefi, because they charge a 10% fee even though we are the one to custody the funds and triage the bug reports and payouts. He also suggested that the timing for a possible bug bounty should be after the mitigation review and deployment of the updated contracts to Mainnet, for we might need to make any bugs outstanding out of scope thereafter.

Devcon programming with @bruxa and ThirstyThirsty

"Thirsty Thirsty is an ancestral remembrance project disguised as the coolest food and wine club on Earth. "

@bruxa is the founder of Thirsty Thirsty DAO, this community has been in existing since 2014 and set foot into Web3 in November 2021. They are a community of food and natural wine lovers, enthusiasts, experts and Earth stewards focusing on the cultural restoration and ancestral agricultural practices which they see as a really critical component to mitigate climate crisis.

Last week, @jango talked with @bruxa, @Zom_Bae and a few other folks about how we could partner with other communities who already have a leg up on creating events and bringing people together, and how we actually could partner from a funding perspective to do things like during the Devcon Bogota.

Oct. 10th, during the Devcon week (Oct.7-16) in Bogota, will be the indigeous people's day of the Thirsty Thirsty community, @jango and @bruxa are having the idea of creating an event that's Dev focused and bringing people together in an open-ended forum just similar to how JuiceboxDAO did on NFT NYC where people can come together and share ideas and be inspired by whatever happens. Also projects running on Juicebox or leveraging Juicebox can use this space to create a space for their own community to come together, while the JuiceboxDAO can partner with Thirsty Thirsty to provide food and dirnks to accompany this event.

Thirsty Thirsty NFT membership

Thirsty Thirsty Membership NFT

The Thirsty Thirsty is a 501(c)(3) entity that can accpet crypto donations.

Currently Thirsty Thirsty has their own membership NFT minting, with which on one hand they are trying to bring people together to experience the power of nature through food and wine in the cities and land, on the other to empower and share what this tooling is with their community some of which have been left out of financial sovereignty.

They're pretty interested in how Web3 tooling can help remedy a lot of issues with the labor chain and create equity in their communities all along.

They're also very excited to play with some smaller limited edition airdrops through Juicebox as a fundraising mechanism, especially tethered to some event that they're planning.

K.Group DAO with @Jermaine.A

K.Group DAO is an affordable housing DAO, they have a unique solution to solving a housing shortage and trying to combat the affordable housing crisis in the U.S.

K.Group DAO

Solutions to housing for low-income

The house below is an actual one in Houston, Texas, which was 4 bedroom house origially (left), and they converted it into a 12 bedroom one and added another bathroom. By this moment, there are 12 people staying there already.

12-bedroom floorplan in Houston, Texas

You can also take a look at what the house is and its renovation by scrolling down to the bottom of their homepage and explore their first home.

Virtual tour of K.Group DAO's first home

What they are doing right now for this solution to house low-income individuals are:

  • rents are between $650(small room) and $800(large room)
  • all the rooms come fully furnished
  • free internet, free laundry and all the utilities taken care of
  • no first month's and last month's rent and no security deposit
  • leases are on monthly basis so tenants can move if they wish

@Jermaine also said this housing model could be used for anything anywhere in the world, for the conversion that was done is just unversal.

Goals of the DAO

The reason why they set up a DAO is that they think the DAO will be better to upsolve this housing issue with affordable housing.

When it comes to the project token $KDAO, they try to keep it as simple as possible, just strictly a governance token. Decisions to purchase any house or pull equities back into the project treasury will need to follow a governance procedure and be voted on with governance tokens.

They are an LLC entity licensed in Wyoming, so they can purchase physical assets and have bank accounts, etc.

The governance of this DAO will not only be about real estate, it might include the following according to @Jermaine:

  • house purchasing
  • renovaton
  • marketing (local churches, community centers, online housing platforms)
  • management
  • maintenance

Eventually they want to create an online platform to where those rooms are listed and anyone can access them anywhere in the world.

Their ultimate goal is to house at least 10,000 migrant families within 2 years, and be the first DAO to sign a government contract as a contractor for Department of Homeland Security to help and house people.

Two truths and a lie with @Felixander

Two truths and a lie

The correct answer is @gulan

Defifa with @jango

Defifa

With the World Cup Qatar 2022 upcoming in November this year, and being one of the first global events after Covid, @jango thinks this could be a meme shilling point in some way. And he landed on a mechanism, a self-governed game system, facilitating the incoming NFT Rewards and the NFT voting system. (If you are interested in this project, you can read the Defifa specs here, and join the discussion in this Discord thread)

Essentially it'll be a bit hard to really wrap your head around it, unless you really know how the NFT Rewards system works and how it can be extended to support this. A surface perspective the community understands the NFT Rewards contract is just 3 NFT tiers that project owners can put up on the juicebox.money site, and the price thresholds that contributions need to cross so as to get the NFTs minted to contributors' wallets. That's very much the basic case of this contract.

But this contract can do a lot more.

A winner-takes-all scenario as an example

Imagine like two weeks prior to the first day of World Cup, November 20th, someone deploys a treasury that doesn't have an owner. He can preprogram the rules upfront and the game will play itself out and end in a certain date. There is no funds in the treasury to start out, and there's zero tokens minted.

There will be 32 NFT tiers representing each of the teams in the competiton. It's a open mint, so anybody can mint any number of any of the tiers.

After two weeks when the first game starts out, minting will be closed. So everyone has their NFTs, which are all transferable and regular type of NFTs.

Let's say, we have 100 Brazil's NFTs minted and 10 Japan's minted, which will give you a sense of people's confidence of which team is going to win the competition. Now we have these outstanding NFT tokens and a loaded treasury which is the funds of the game.

At the end of the game, let's say Japan wins the competition, there'll be a self-governing process to submit a scorecard on the contract. Then all the NFT holders attest to the scorecard which they deem is correct, via a mechanism that will hopefully keep the result honest. Let's say someone submits the Japan scorecard and someone submits the Spain one, it'll be all the participants' responsibility to attest to the correct result.

Essentially all the scorecard at the end is a redistribution of the game's total funds. During the first two weeks open mint window, anyone can burn their token and get their funds back. The redemption rate is 100%, all NFTs are worth what was put in. But at the end of game, all the scorecards are the redistribution of this redemption rate. So basically a redemption delegate can be created to make all of the treasury now back the Japan NFTs instead of all other NFTs. The funds don't need to be distributed to the winners, instead they are reorganized to back the winning NFTs. Although now you can burn 1 Japan NFT to get 10% of treasury, but that'll be just the floor price of that NFT at the very least.

More complesx version for intra competition game

You can also extend this mechanism to take into account intra competition matches.

Let's say if your team makes it out of the group matches, your NFT will be backed by 5% of the treasury,if you make it to the Top 3, it can be like 3rd place gets 15%, 2nd place gets 20% and 1st place 40% of the redemption.

All the scorecards at the end are basically the resulting redistribution of what back each NFT, then everyone holding the NFTs has on-chain vote from each tier to attest those results. And you should create the value of each vote so that people can't game the system in an obvious way. Let's say 51% of all NFTs minted are Spain, if you do 1 NFT 1 vote for attestations, Spain can just say it won and then vote itself in. So you have to spread out the weight of each tier's vote across the teams based on team's total supply, or something like that.

Actually this NFT Rewards contract that we built is a version of a governor contract that lets each tier have independent voting utilities, you can create votes that recognize a particular voting weight of tier, as opposed to just one NFT in the context of the whole system. All NFTs of all teams are in the same contract, but they often have different voting capacity for attestation, they can be backed by different redemption values given the end state of that scorecard.

Other thoughts

You can also pre-allocate like 10% of the game's treasury to be shared by people who voted for or attested to the correct results, giving people an incentive to participate.

@jango thinks we should play it really simply here at first, and if it works out, it could be a cool thing that scales, you can have this play itself out in different athletic competitions and etc.

This is something that's been on his mind, and it's an extension of the NFT Rewards work that's slated to come out soon.

And there's for sure some cool game theory to tease out. Let's create something that encourages an honest attestation process. Everyone knows the real result and it's black and white, but will anyone defect? or is everyone incentivized to report correctly?

Sayid: Concerning the attestation, couldn't we bpass it by making some kind of API or using existing API to check the scores of the games?

jango: You could maybe pull in an oracle that's attesting to that result, but I don't think that's necessarily the goal here though. It will also be really interesting for the purposes of this being a generalizable Juicebox project that we can create a mechanism where the game theory works itself out, and the participants are encouraged to report correctly. That way, anyone can deploy a treasury in a game and it can load itself up and then be resovled all in a self-contained format.

I think this is also maybe an invitation to brainstorm other World Cup related shindigs that people want to stand up. I think this is maybe something worth doubling down on, and also we can get other Web3 projects in on it. I don't think this is a Juicebox specific thing that we do and try to get an edge on other protocol. This is a pretty cool coming-together celebration of the world through sport.

· 2 min read
Felixander

Want to raise funds with a Juicebox project? There’s a few important decisions you should make so that your project does what you want it to.

You should figure out if you want to raise money indefinitely or only for a certain amount of time. You can set your “duration limit” to specify this. Only want to raise money for a week? Set a duration limit for 7 days and you’re all set.

Have a certain amount of money in mind that you want to raise? You can set that with the distribution limit. If you want to raise money as much as possible, you can also leave your distribution limit off. Careful though, this may scare away contributors.

Let’s look at some examples of successful Juicebox fundraisers.

ConstitutionDAO - Total raised: 11,613 ETH (Approximately $47 million USD at time of fund raise)

This project raised funds so that it could bid on a copy of the US constitution. They wanted to raise as much money as possible leading up to the auction. They didn’t set a “Distribution limit” or a “Duration” because they needed to deploy their project as quickly as possible and stay flexible. They were able to do this because the communtity trusted them and they had a multisig. Because of these settings, the project was able to accept as much money as possible on an ongoing basis.

AssangeDAO - Total raised: 17,422 ETH (Approximately $56 million USD at time of fund raise)

This project had a deadline to raise funds by. For this reason the project opened up accepting funds for a period of 3 days, leading up to an auction that they hoped to bid on. They did not have an upper limit of funds that they wanted, so they kept their “Distribution limit” off, but they did set a 3-day duration during which they accepted funds.

MoonDAO - Total raised: 2,623 ETH (Appoximately $8 million USD at time of fund raise)

MoonDAO raised money to send a guy to space. They did it in 30-day fundraisers, so they set a “Duration” of 30 days with an open “Distribution limit”. This was to create a donation-window, and when they determined they needed more funds, they created more donation windows in 30 day durations. They succeeded and sent a guy to space.

· 3 min read
Felixander

Governance can be fun

And funny. As Sean McCaffery, Co-Founder of JokeDAO and seanmc.eth#0163 will tell you, governance doesn’t have to be a somber affair. Along with their co-founders they’ve built JokeDAO, a DAO tooling option that can run everything from on-chain governance to shitpost popularity contests with ease.

JokeDAO 🃏 An open-source, collaborative decision-making platform.

Enter JokeDAO

The schema is simple: create a contest, and deploy it. Users on the platform can then vote on your contest with tokens that deploy for just that contest (if you wish). The platform can handle anything from “What color birthday cake should we choose?” to “Tell me the best joke about hamsters” to “Which workspace tooling should our DAO be using day-to-day?” It does so on-chain and transparently, so you and your community can track progress, previous votes, and run a decision-making platform that’s open and honest.

https://twitter.com/jokedao_/status/1549053077046472705?s=20&t=F1--BE4uL7TiocEVd1EluA

Disposable tokens and their utility

Central to JokeDAO’s platform is the unique way that tokens are used. That is, they are quite literally used. In many cases they are disposable and unique to a specific contest. This has some strong benefits, and is a facet that many other DAOs could learn from.

Token-voting mechanisms suffer a lot from the question of why. Why should some people have some much more voting power than others. Reasons abound. Maybe it’s because somebody was an early contributor. Maybe it’s because somebody contributed a boatload of funds to a project. Or maybe— bear with me here— a person has a really nuanced understanding of the topic at hand.

But that last case is a bit less common. After all, it would be nice to say, “You know what, we’re voting on solidity devs, so let’s give all the solidity devs a bit more voting weight for this proposal,” but current mechanisms make this difficult and cumbersome, and certainly not scalable.

JokeDAO, by employing tokens which expire with a single contest or vote, can easily address this issue. And this is just one of many use cases where it’s a potential game-changer.

https://twitter.com/jokedao_/status/1562100521334341633?s=20&t=BvRz0K1QwJE8AK5695G2AA

The future of JokeDAO

Where JokeDAO will go is anybody’s guess, but current sentiments seem to point moonward. The platform has shown new ways to approach governance for DAOs, and offers tooling that is unique and easy to employ. What more could an anon ask for?

To follow JokeDAO, check them out on twitter. To learn more about co-founder Sean, find their twitter here.

· One min read
nnnnicholas

In this video, I'll show you how to:

  • Create a list of addresses that hold your project's tokens using Juicebox.money
  • Create a list of addresses that have voted in your project's Snapshot
  • Create a JokeDAO contest
  • Airdrop voting tokens using Coinvise

The Snapshot GraphQL query used in the video:

query {
votes (
first: 1000,
skip: 0,
where: {
space_in: ["jbdao.eth"],
},
orderDirection: desc
) {
voter
}
}

For support, visit discord.gg/juicebox.

· 5 min read
Zhape

Town Hall banner by Sage Kellyn
Art by Sage Kellyn

Business dev with @0xSTVG

0xSTVG has been actively reaching out to some blockchain and web3 clubs at universities. The responses were quite warm, and they have been setting up talks with Juicebox, as well as having some in-person presentations and possible hackathons.

He plans to submit some proposals in the upcoming months, trying to help onboarding students and web3 enthusiasts in colleges and universities. He is gearing some of his efforts towards recruiting those types of builders.

Gplay studios with @Sayid

@Sayid came to the Town Hall 3 weeks ago, did a demo with some preliminary designs of his platform. He founded this P2E(Play To Earn) arcade platform called Gplay Studios where uses can make profit by staking $Matic and wagering against each other in classical games on Polygon.

Except for the Tic-Tac-Toe he showed last time, recently he has added another 9 games to the platform.

New features developed:

  • Game invitation link, which can automatically connect the person to a game someone else created,
  • Rematch function, which player can use to request a reset of game and changing the opponent

The Discord server of Gplay is here, anyone who is interested in his project can join and have fun over there. @Sayid also said he would be hosting some gaming nights once all the bugs were fixed.

Nance Funding cycle configuration demo with @jigglyjams

@jigglyjams did a demo on how he runs the Nance script to query from a Notion database of payouts and use those data to submit a Gnosis transaction to reconfigure the parameters of a new funding cycle.

His next step is to query payout addresses and payout amounts from proposals that have been approved and get them merged into those databases for reconfiguration of funding cycles.

Also he is going to work with @twodam to set up a frontend to configure Nance the Gov Bot in a Juicetool page. But he's also a bit concerned about where to store all the configs of Nance at this stage.

Banny drawing contest on JokeDAO with @nicholas

@nicholas was hosting a Banny drawing contest using the JokeDAO voting machenism, in order to help showcasing the JokeDAO V2 new feature of uploading images as contest submissions. Everyone could submit a Banny/Bannyverse drawing in a submission period for others to vote, and the voting would be open once the preset submission period was up.

@nicholas minted the voting tokens and distributed them by airdropping to whoever has taken part in the JuiceboxDAO governance voting on Snapshot before. People receiving this token can vote for whatever images they like, and the image that gets highest votes win the contest.

And @nicholas also made a tutorial about how to create JokeDAO contests for Juicebox projects, which can be found here.

The winner of this contest was @brileigh, and the image that got the highest votes is:

Another upcoming new feature that JokeDAO will be developing, which is also funded by JuiceboxDAO, is the executable contest, in which projects can signify winning conditions so that the winner can be executed on-chain after the contest.

@filipv suggested that JokeDAO can also set up some thresholds, such as top 3 or top 4 in the contests win. This can be useful in application scenarios such as different prizes to Top X winners, or Top X winners get to be qualified as a member of a multisig, etc.

And @seanmc also said that they're talking with IPFS about image uploads within the website, which will be an amazing integration to it if implemented.

PeelDAO updates with @Aeolian

PeelDAO recently onboarded 2 very awesome designers, @Strath and @Lawrence, respectively working on the redesign of the project creation UX and an update to the homepage. Hopefully these two efforts will reduce our currently high bounce rate for the website.

And other big frontend projects underway are:

  • NFT rewards, this is already on Rinkeby so people can play with it already.
  • Settings page, which @Jmill is currently working on and hopefully will be ready by the end of this week.
  • Versioning, a strategy to manage multiple versions on the frontend.

Some features that have been shipped:

  • CSV imports for payouts;
  • CSV exports for payouts and reserved tokens;
  • Juice SDK, which is a toolkit that makes it easier for people to set up frontends on Juicebox protocol.

Also they have been finetuning a lot of dev performance security work, running through all the dependencies and upgrading them.

One thing they are planning to implement is the Twitter verification, currently people can put anyone's Twitter into their Juicebox projects.

Juicenews newsletter new release and Juicecast new episode by @matthewbrooks and @brileigh

A new release of the Juicenews newletters on Aug. 30.

And a new episode of Juicecast featuring @seanmc of JokeDAO. And @matthewbrooks urged us to at the very least listen to the first 10mins, which should be very great!

Two truths and a lie with @Felixander

The correct answer is @Gogo, and he's a great story teller, try to tune in to his story of being surrounded by "Shark DAO" in Australia at 35'37" of the Town Hall recording.