Skip to main content

· 7 min read

Town Hall banner by Sage Kellyn
Art by Sage Kellyn

Audit Fund Recap by Nicholas

icholas created the Audit Fund project to raise funds from our community members to pay Code4rena for the NFT Rewards contract audit contest, before the funds were distributed from the DAO. For more details about this project, please refer the summary of Town Hall last week.


On Oct. 22nd, after the grants from the DAO was added to the balance of the treasury of Audit Fund (Add to balance is a method to pay a Juicebox treasury without invoking minting of tokens, which in this case is to make sure the donors can have their full refund), people started to redeem their project tokens to get the ETH they donated a few days ago back in full amount.

Also a total of 9,000,000 JBX rewards (3m JBX by the DAO, and 3m JBX matched by Jango and Peri respectively) for donors to this Audit Fund project have been airdropped by Nicholas today.

It seems that the Code4rena found this crowdfunding project very interesting, which maybe would lead to a future partnership between JuiceboxDAO and Code4rena.

According to Nicholas, this project will probably stay open later on, as there will be future audits, such as the one for veNFT at some point in the future, or even audits of smaller scales in between.

NFT Rewards Audit Update by Jango

The Code4rena Audit contest for our NFT Rewards has finished.

Everything went quite smoothly, we've got a report with close to 200 line items of the findings from Code4rena that catalogued as high severity, medium severity, gas optimization, etc. JuiceboxDAO Devs have spent several days triaging problems found, reading through and getting the gist of issues, while been in touch with a few wardens throughout the week.

The good new is that it looks like no critical timeline-busting issues were found, so we will still be on track of deploying it to the mainnet next week as planned.

Jango thinks the audit is a better process prior to deploying. We've learned from the audit of V2 protocol that even though a project seems like it has been a long while coming and feels ready and well tested, sometimes it still can lead to more annoying stuff later on. So we'd better take the final step of looking at things closely and sharing it with the world and incentivizing folks to poke around.

The next couple days, our contract squad will be getting their test suite up to date with the changes included. If all goes well, we'll probably be aiming for deployment on Mainnet on Monday or early next week. Projects will be able to attach it into their funding cycles and deploy NFT Rewards in less than a week.

New Project Create Flow by Wraeth

Frontend team, especially Strath and Wraeth, has been working on this new create flow for nearly two months. The whole idea is to make this process a lot more simple than what we currently have, in order to make the experience of project creation more enjoyable for users.

Strath has come to the Town Hall on Sept. 13, 2022 and given a preliminary introduction to this project.

Today, this new create flow has been deployed on Wraeth walked us through every steps of the create flow by demonstrating the creation of a project Flamingo Sunday.

Some characteristics of this create flow:

  • This create flow breaks down our current creation process into different steps, so that project creators basically only need to make one big decision every step, so as to alleviate their cognitive load in this process.


  • This new flow tries to simplify the UI and make interface neat and clean, by folding some optional choices or hiding some unselected information away, so that project creators don't need to be bombarded with too much information in their project creation.
  • The create flow supplies some default templates such as Automated Funding Cycle, Default Token Settings, etc., so that project creators can just choose the frequently used configurations instead of having to customize their own every step of the way.


  • It integrates the new NFT Rewards contract, project creators now have more choices to incentive their supporters, though the contract is expansive so a lot of functionalities might need to be added in future iterations.

This product is not yet finished and might need some iterations to improve it a little bit more. Try it out, and if you have feed back, please come to share with us in the Project Creation Feedback thread under the Frontend channel of JuiceboxDAO Discord.

StudioDAO Sesh by Kenbot

Kenbot was very grateful for Jango's encouragement to build in public, which has changed their way to build this project. They have set up a dedicated channel in JuiceboxDAO's Discord to incubate this project, from where it got traction and really moved out into the real world. And Kenbot also expressed his gratitude towards Aeolian especially who heroically helped building some very key feature and energized the whole process.

Kenbot also made a demo on the Town Hall to showcase all the items on the webpage of StudioDAO, which he hoped would become a dashboard of fun things to do and be related to the NFT collection of community members. He thinks that crazy ideas will start from here and will be able to have more and more funding so that things will grow from the bottom up to their brilliant success.


DevCon Casa Event Recap by Bruxa

Bruxa came to the Town Hall, and shared her deep gratitude for what this project has helped bringing forward, both as a personal transformative experience and as a transforming opportunity for the Thirsty Thirsty community.

She also wanted to share that the grant from JuiceboxDAO has not only obviously helped make such a beautiful experience, but also already generated really serious impact for their community. On one hand, some of that grant provides fantastic runway for Thirsty Thirsty as a nonprofit to continue operating, on the other, it also helps individual community memebers in some realistic ways, such as improving their personal life, and renewing their enthusiasm for what's possible in the community.

Jango also expressed appreciation for what Bruxa and the Thirsty Thirsty community have pulled together on this event. He thinks a lot of our community members are pretty narrowly focused and collaborative with folks who share a high bandwidth JuiceboxDAO perspective. And It is very awesome to come together with all kinds of brilliant people in all kinds of brilliant places with different themes.

Bruxa also invited Juicebox community members who happen to attend the SF Blockchain Week 2022 to join the activities by Thirsty Thirsty community in that interval. They are planning to arrange some casual vineyard visit, and would love to meet more Juicebox folks over there.

Bannyverse Comic 2 Teaser and Defifa Press with Felixander

Felixander said he would be putting more effort into the Bannyverse and working on building out Banny with more zany/crazy memes.

Also he is going to work on the Ad page that ComicsDAO provides us in their NounsDAO comic book. He will work with Brutula and set up a thread in the Discord to have more discussion on this matter.

The 2nd edition of Banny comic is coming out soon, here is the teaser of the story of detective Banny.

And about the Defifa press, Felixander has been reaching out to get some press to cover our Defifa project before its launch. He invited any kind of help to that matter and was open to any ideas on getting the ball rolling over there.

Depraved Pictionary with Felixander

On the meeting Felixander asked some DAO members to give him a one-word activity or an item that Banny gets up to on a wild weekend. And he invited some of the members to play a game at, in which one person is to draw a picture from their word while the rest of member are supposed to guess what that word it.


After the game, Felixander set up a poll to see what is the most favorite word/item in the game.


· 10 min read

Town Hall banner by Sage Kellyn Art by Sage Kellyn

Code4rena Audit and Audit Fund Project with Nicholas

The Code4rena audit contest for our NFT Rewards Contract has begun earlier today.


This is a $50,000 audit contest which will last 5 days until Oct. 23rd, 2022. After that, the NFT Rewards contracts will be deployed on Mainnet and attached to around the end of this month.

Although a proposal for the JuiceboxDAO to fund this audit contest has been approved, the grants will not be available until Oct. 23rd due to governance process arrangement, which is at odds with our original plan of starting the audit on Oct. 18th.

So Nicholas created the Audit Fund project to help raising funds for this contest first, the donors to this project can have their full refund by the time the grant from the DAO is added to balance of the Audit Fund project.

Nicholas also launch a 3-tiered (0.1 ETH / 1 ETH / 10 ETH) NFT collection to help boosting the fundraising, with the proceeds of its minting directly routed to the Audit Fund project, so that minters can later on redeem their project tokens to get their refund and get to keep this NFT.


Also the DAO agrees to allocate 3,000,000 JBX rewards to the contributors of the Audit Fund project, which is to be divided into 1,000,000 JBX for each tier of NFT respectively and evenly split between NFT holders of the same tier. Because Jango and Peri decided to match the rewards of the DAO, the rewards finally reached 3,000,000 JBX for each tier of contribution. And the NFTs serve as a ticket to the airdrop of these JBX.


The Audit Fund project turned out to be a huge success, with total funds raised far more than needed to pay the audit contest.


This project may serve as a proof of concept for a possible JuiceboxDAO x Code4rena partnership, to help permissionlessly sponsoring audits for other protocols.

DevCon Casa Update by Jango

The context of this event is as follows:

The proposal of this event by Jango was approved by JuiceboxDAO a little while ago.

“As JuiceboxDAO looks to encourage and support game-changing projects and capital formation schemas to form leveraging the Juicebox protocol, it should consider sponsoring accessible in-real-life gatherings hosted by contributors intimately familiar with the protocol and its potential applications to big-picture ideas, and attended by passionate builders, designers, and capital allocators.

The Thirsty Thirsty community and I are curating programming in a house in Bogota for ceremony, celebration of our agricultural lineage, and design sprints focused around how we might sustainably fund land-based projects using Web3 primitives, around the time of DevCon.“

- Abstract from this proposal

Jango's first-day-back reflections:

  • Our ability to pull multi-disciplinary passionate people together was key to unlocking new creative avenues. Ahead of time, I was less sold on the need for a videographer as a value add to the experience. Turns out the budget wasn't just spent on getting a videographer there, they were spent on a Fernando. Same goes for Juanda, everyone who brought +1's, and everyone folks invited to our space for deliberate design/learning sessions and casual moments. Next time we need to double down on this. It's all about the people, the work orders are just an excuse.

  • Having a few focused scheduled moments around food and ceremony were grounding and set a perfect tone. It wasn't a greasy hacker house, it was a welcoming space where we could be caring, curious, and warm towards one another.

  • It would be nice to have a few more optional excursions planned for people to take part if their schedules allowed, though it seemed most people were happy sitting around the house with laptops out together, exchanging ideas out loud and on notebooks.

  • It was great having an extra house in Guasca. Though we didn't use it to its full capacity each day and had some trouble accessing it at times (dirt roads, annoying hosts), the times we did use it were monumental. The dinner we threw with our friends from Mochi was epic, and it was great to have extra bedrooms for folks who wanted more space for themselves.

  • Epic having Pablo, Alejandro, Thomas, Mark, Steve, Juanda, Fernando and Bruxa there alongside more day-to-day JuiceboxDAO contributors. It was a focused enough group of people where I felt I could build relationships with everyone. I'm more of an intimate 1-on-1, small group, few real friends kind of person, the cadence of this event catered well towards that. Epic group of big-brain big-heart people.

  • Despite spending loads of time online together, getting time to hang and bullshit with peri, zeugh, nicholas, filip, and jmill was necessary to gluing new ideas together. The whole week was high-bandwidth communication with a bias towards doing. big love to the family.

  • One of our super powers is empowering creative and passionate people to pronounce their creative muscle through their own projects, in the way they feel most comfortable, encouraging them to push against discomforts their curious to explore, while helping make connections within our expanding ecosystem of builders who might offer support and specialization to round out a project's needs. It'll be difficult to measure this event's immediate value add to the broader JuiceboxDAO community, but seeds were sown and I look forward to referencing this Bogota week as an origin story for many projects/partnerships that may sprout over the next several months.

  • We need to be aware of people's financial circumstances when inviting multi-disciplinary friends. We did a good job in helping Fernando, Juanda, Bruxa, and Zacharias (didn't make it but we did what we could) arrive by compensating their airline fees, while all others were responsible for sourcing flights themselves. We each have our own accesses and constraints, we have to be comfortable talking about them so we can help one another make stuff happen and leverage what each of us can bring to the table. This is tricky to scale, but important to get right.

  • We could've used more help sourcing ingredients and planning foods. We had this in place with Zacharias, fell apart last minute. Stoked with how we all came together and made it work, but we all spent a grain too much time throughout the offsite week planning meals.

  • I liked over-indexing on supporting Thirsty Thirsty. It allowed us all to problem solve with confidence as the weeks went on. I'm excited to see how we can continue working together to help them raise and sustain funds used to power land-and-people-based experiences, and how they can help JuiceboxDAO bring it's community together around earnest moments alongside neighboring communities.

Frontend Update by Aeolian

  • The site has been deprecated;
  • V3 version of Juicebox contracts have been deployed on Goerli testnet;
  • Mainnet launch of V3 contracts is underway, but the timeline is still TBA due to some recently found complexities with Subgraph.

Visibility Update by Matthewbrooks and Brileigh

A new edition of Juiciness newsletter is released today, covering:

  • Weely recap by 0xSTVG
  • An article by Nicholas about routing funds from an ENS to a JB project
  • An article by Felixander about the history and configuration behind SharkDAO
  • Articles by Matthew and Brileigh about MoonDAO and its project configurations respectively
  • First video interview released on Youtube, with David Phelps from JokeDAO
  • Defifa teaser by WAGMI Studios
  • Town Hall summary for Oct. 11 by zhape

Also they are trying re-render all the past Juicecast episodes with custom 4k waveform visualization and upload them onto the account of JuiceboxDAO in Youtube, in the hope of repurposing the contents and improving the seachability of them, so as to expand the influence of JuiceboxDAO.

Art Apprisal Contest by Felixander

Felixander asked 3 peolple to decribe ''Banny's craziest night" and use those descriptions for purpose of AI drawing on Dall-E. He showed on the town hall one of the drawings and ask people to guess whose description makes this picture.



And the correct answer is ... Jango.

Quick Update of Defifa by Jango

Folks have been pushing stuff out one chapter at a time in this Defifa project.

From a frontend perspective, big shoutout to Blaz and Deviant for getting the site up and hosted, and also starting to prototype the sections. Later on, we can start pointing people to the page, to improve the styling and some final touch-ups towards the end.

From a contract perspective, we have the redemption mechanism working, thanks to Viraz and 0xBA5ED for prototyping some different options we have for the redemption calculation and attestation processes, which are feeling tight right now.

The next step on the contract side is to encode 4 funding cycles into publicly queueable transactions. The project owner will be a contract and it'll initialize rules passed in with the start date of tournament, minting period, trade deadline and the end date. When one funding cycle is in progress, anyone can queue the subsequent funding cycle from these rules.

Shoutout to Mieos for stitching together these artworks for every country, which requires a big chunk of focused time and effort. And thanks to Sage for the iconic Banny design, relentless and incredible as always.

Also shoutout to Tankbottoms for helping out last week, wrapping these in metadata and getting it pushed to IFPS so that we can leverage in the NFTs.

Next week we'll be wiring everything up on Goerli, while Jango has yet to decide whether we will try out minting on Goerli, all the components are coming together and feeling quite good.

Once the game is over, we'll think about how to expand the framework and interface to accommodate a generalized version of the game, so others can play with their own intent.

Question about NFT Rewards from ComicsDAO

Defaulteduser, the founder of ComicsDAO, explained that these days comic books have become a collectible instead of something to enjoy, which is quite annoying for the lovers of comic books. So he thought of taking comic books and putting them onchain, so that they can preserve the books while at the same time allowing more people to enjoy the content. They've been looking at scanning individual pages of rare comic books and essentially putting these pages on chain.

He was wondering if it's possible to scan pages of rare comic books and give them away as NFT rewards in a fashion of randomized distribution to people who will receive them.

Jango thought the randomization would probably be a tricky part of it, because the NFT rewards are designed to be choices that are deterministically made. He suggest that ComicDAO might try to distribute the NFT rewards first, but would then reveal which comic pages are in those NFTs respectively later on with some other randomization process. They can use a specialized URI resolver contract which will actually resolve the image of each NFT in metadata after the distribution. After that, as the owner of that contract, they can eventually renounce their ownership so everything will be fixed in place. And this should be a cool idea to work towards.

· 6 min read

Town Hall banner by Sage Kellyn Art by Sage Kellyn

Tech update with Jango

  • Code4rena audit contest for NFT Rewards contracts is scheduled for next week.
  • NFT Rewards contracts will be finished and deployed on Goerli testnet this Friday.
  • After that, attention will be turned to v1=>v3 and v2=>v3 token migration paths. Hoping to get this done and shipped with full frontend support by December.
  • At the end of the year, there will be some cleanup efforts and supporting the finalization of any loose ends, prepping to make JBX moves in January with publishing the Fee Module and veBanny collection.

L'art pour 'lart with Felixander

Felixander and Burtula made the Banny graphic novel, which he thinks to be a fun little testament to art for its own sake and we should really highlight the artistic endeavors in our community.

Nouns comics Ad page by Gogo

ComicsDAO is going to publish Nouns comics these days, which will be distributed off-chain and be available in bookstores around the U.S.

They have 8 pages in this comic book that going to be used as Ad pages for DAOs or projects related to the Nouns community, and now they want to give 1 page to JuiceboxDAO so that we can promote ourselves by graphic story telling like Felixander just did.

Gogo said ComicsDAO want to do this for gratitude of the supports that JuiceboxDAO has been giving them, which he thinks might help Juicebox reach out to more folks in real life.

NFT Rewards Audit Fund by Nicholas

As our upcoming NFT Rewards contract is pretty complex and full featured, we want it to go through a Code4rena audit contest just like our V2 protocol did couple months ago. We're fundraising for this audit on the Audit Fund project so that people interested in it can pitch in some funds to support.

We are now looking at starting the audit contest on Oct. 18th, in order to do that, we'll need $73,800(Juicebox fees included) in the Audit Fund project by Oct. 17th. Nicholas has submitted a proposal currently for the JuiceboxDAO to fully support the expenses of this audit. If this proposal gets approved, $73,800 will be added to the balance of the Audit Fund project without minting any tokens, which means all the contributors to that project can basically get their full refund minus gas fees.

As the funds from the DAO won't be available until Oct. 22nd, it will be more ideal to crowdfund the whole amount with folks first to get the audit start earlier. So Nicholas also suggested in the proposal that the DAO allocate 3m JBX tokens to reward those support this audit effort. There'll be 3 tiers of donations, i.e. >0.1ETH, >1ETH and >10ETH, and each tier of donations will share 1m JBX. And Nicholas also mentioned that he might want to propose a retroactive NFT Rewards for these 3 tiers of donations in the future.

This Audit Fund project also serves as proof of concept for Code4rena team, as they are exploring the possibility to create projects on Juicebox for smart contract or protocols out in web 3, so that people can sponsor each other's audits permissionlessly.

Finally Nicholas thinks this Audit Fund project might live on to fund future audits, such as that for the VE NFT, and others to come.

Marfa Giant with ONNI

The Marfa Giant project was created with the intent of rolling out a print publication nationwide in U.S., which was thought to be a pretty cool use case of web3 protocols. Since his last update in the JuiceboxDAO Town Hall, ONNI have been faced with a lot of hurdles in their growth in trust and mentality of the community.

So the project began to organically evolve somehow. They built their own website and started reaching out to invite people to write columns, covering real time local news, posting contents and trying to figure out the needs of the community. This is a big shift from their print publication model, though that is still their final goal.

From there they managed to identify a few different objectives.

  1. Buiding a following within the community
  2. Trying to acclimate the community to digital news on websites.

To produce contents for their website, they went to city council covering events in real time, and reached out to artists, poets, writers for their works and published them.

Also ONNI created a data visualiation tool for city budget on the website so that people in town could look at it and click around to check all the details.

They now have a plan to distribute project tokens to every people in the town and make this publication project truly a community-owned one. But in a rural town without web3 or even web2 mentality according to ONNI, they still need to find ways to educate people to adopt this new way of paying or getting paid. And they are also exploring the possibility of issue some NFT with contents like poems or chef's recipes so that the sales of NFT can flow back into Marfa giant and be paid to the content creators.

What they need of help right now is:

  • All contributions are super helpful
  • A lot of design help in their website frontend
  • Tech expertise like system architecture, backend dev, data visualization, etc.

Visibility updates by Nicholas and Matthewbrooks

Matthew and Brileigh have just released their latest episode of Juicenew here

And they also wrote an article about Moondao, with details about the backgroud, the development history, as well as the most recent updates of this community.

In the course of creating the Audit Fund project, Nicholas came up with a cool model to use an ENS name to work with the Juicebox project payer, so that funds like ETH sent to the ENS will be forwarded to this project payer and go into the treasury of that Juicebox project, with project tokens minted to the original contributor in return. Nicholas wrote a blog post as a tutorial in details here.

FORMING updates by Wackozacco and darbytrash from Lexicon Devils

Their next FORMING event will be on the Saturday leading up to Halloween, i.e. Oct. 29th, and the theme for this event will be a little spooky.

Submissions are open at the moment, if anybody wants to do a 10 - 15 mins recording of some live performances, feel free to submit in the Forming webisite. Submission will be closed on Oct. 25th.

Also, Lexicon Devils is going to make a whole new overhaul to the Lexicon Devil's website, as well as that of Forming, to make it very clear what their target is, what their vision is and what they are after with Forming as an entity.

· 16 min read

Town Hall banner by Sage Kellyn
Art by Sage Kellyn

NFT Rewards Strategy with jango

We've been in touch with Code4rena this past week to schedule the review for NFT Rewards contracts.

Since our next governance cycles will only be able to put out funds in two and a half weeks, Nicholas launched a Juicebox project, NFT Rewards Audit Fund to help crowdfunding so that maybe we can get the review started earlier.

  • Jango has been fronting funds for the previous two Code4rena audit contests, it's not sustainable to do it in this way. This project could be an interesting alternative;
  • This will be the first experiment that we do with the Code4rena audit contest, hopefully we will have some model to share with them and they can use it for other projects as well;
  • If we can put the funds down, theoretically we could start the audit contest on Oct. 7th, at the end of this week, although it's not very easy to get some steam up and running for this project in a short period of time.

But there might be another approach to handle this Code4rena audit contest a bit later:

  • A lot of devs who tend to participate in this audit contest are going to be at Devcon Bogotá this next week and a half, and probably on their computer less often than normal, or at least less focused on problem solving;
  • Given that contest will cost us about $70k, and the governance process takes about the same interval of time as Devcon, it seems a decent option to spend this period of time to tighten up some things and keep running more tests before the audit contest;
  • We should be aware of the fact that there are quite a few moving peices right now. So it seems smart to take the next week and a half to make sure everything is in place, so that when we put out the NFT Rewards contract, it has been looked at by as many devs as possible;
  • Once NFT Rewards contracts are out, we'll be working with a new piece of infrastructure which at its core is very crafty in its potential and has pretty compelling customization features, we might want to start to put weight on this one step at a time.

If we take the more prudent approach, we're probably aiming for the Code4rena audit contest starting mid of Oct, and a pretty fixed launch date for contract deployment synchronized with the frontend deploy since there're some Subgraph dependencies. It will be a matter of plugging in the contract addresses and shipping it for the frontend experience also, around Nov. 1st.

No decisions have been made on these time frames yet, but Jango is leaning towards taking the more patient approach. We've been sprinting a lot in the past month and frontend has been doing a lot of stuff with subgraph and frontend versioing. Maybe we should take it easy this month in a sense that everyone feels very good and all the moving pieces are very much in place. We will have all loose ends tied and ready to go by the time we launch.

The NFT Rewards contracts are chunky, which is a design choice in contrast to having many smaller contracts that each has scoped feature specifications. These contracts have serveral flags that project owners can turn on and off on deploy, so it's a little chunkier at the convenience of project owners. Over time if there's a demand for any particular version of these considerations, folks can add similar NFT-Rewards-style contracts to get ride of unused flags they may not want. But at first, similar to Juicebox protocol, we are going to deploy this highly customizable and feature-rich NFT Rewards contracts.

The versioning work in frontend seems to follow along and might be available soon. In that case, we'll do the frontend V3 deploy and flip the project creation to use V3 contracts. We will give the V3 project creation some time on its own before introducing the NFT Rewards as part of the creation flow. So if we take the prudent approach on audit contest, it will allow frontend to deal with any bugs or anything that happens in this period of time, since the NFT Rewards contracts will probably be around end of this month anyways.

NFT Reward Audit Fund by Nicholas and Jango

The NFT Rewards Audit Fund is a Juicebox project that Nicholas created to help funding a Code4rena audit contest for the NFT Rewards contracts. Folks can decide to contribute to it so as to speed things up, even before the DAO decides to support.

Also Nicholas submitted a proposal for JuiceboxDAO to support and fund this audit contest. Once approved, funds will be distributed into the treasury of the Audit Fund project, to be paid to Code4rena later on.

If JuiceboxDAO does decide to fully support the expense of this Code4rena audit, folks who donated to this project before could possibly get their full refund through redemption. This proposal will serve on both edges:

  • paying for NFT Rewards audit contest;
  • pushing forward the partnership petential will Code4rena;

But even if this propoal gets approved, the earliest that the funds can be distributed will be the start of JuiceboxDAO Funding Cycle #33, around Oct. 22nd.

jango thought that it would be more ideal for the audit contest to start on Oct. 17th, but to achieve this goal, we might need to:

  • encourage folks to contribute more funds into the treasury of the Audit Fund project when the proposal has not yet been approved;
  • talk to Code4rena about the precedant that JuiceboxDAO has set funding the previous audit contests, and see if they're comfortable with having the funding proposal in motion and approved, or on pace to be aprroved by the time the contest starts, while the funds will only be available by the time the contest ends.

For context, recently Code4rena is interested in creating some Juicebox projects for any smart contracts or protocols so that anybody can crowdfund and start the audits for them. Hopefully, this Audit Fund project and proposal can help to push forward the JuiceboxDAO X Code4rena integration partnership by discovering a typical JuiceboxDAO dogfooding solution first.

Dr.Gorilla is working on an allocator which would allow projects including this NFT Rewards Audit Fund project to pay out funds in DAI, for the sake of convenience so that projects don't need to distribute ETH to multisig or any other address and then swap on exchanges for DAI. Instead, this allocator will take in the ETH from the treasury, check a few exchanges for the best price, and then swap the ETH into DAI before sending to the beneficiaries.

Concerning the question whether or not early donors of the Audit Fund project can get their 100% refund, Jango thought that it will be very probable, as long as JuiceboxDAO fill ETH in the Audit Fund treasury without minting tokens for itself and the redemption rate is set at 100%, as well as that the Juicebox fees are compensated by JBDAO. Jango also express his interest in seeing if the DAO is willing to put some JBX behind it as well, so that folks contributing and taking on the marginal risk can have a little bit of upside in so doing. Also from a membership perspective, it's another initiative to spread the JBX around from the treasury.

Broader JBX Strategy by Jango

In the past couple months, we've been trying to figure out how to create a system where we can spin up a subsequent version of the contracts, accommodate them in the frontend, feel good about them in the documentation throughout all the contract interactions, which gives us some advantage later on if we were to encounter a situation where we need to move quickly to offer projects a way out of the current version.

But this is a temporary measure, eventually we want to converge our processes on our funds on the V3 treasury. Once everything is in place and we feel good about it, we want to create processes for folks that are currently upgrading from V1 to V2 to go over to V3 and make use of the tools there, and then we can start to build extensions further for projects on V3.

Eventually the JBX token should find some redemption value again on V3, for the time being the funds are somewhat scattered across the multisig and all these versions, although to some extent they'll always be since we might still collect fees on V1 and V2. But the goal, from the perspective of JBX, is to converge on the V3 treasury and allow the frontend to make some cleanup choices that we can re-focus on V3 going forward and be creative there without burdening ourselves with compatibility for V1 and V2 forever. It would take us back to the place where we were maybe 4 or 5 months ago when JBX was more frequently redeemed in the treasury, which is a really cool prove of concept of how all this works in principle and will tend to work in the future. Also it will be where the VE tokens can have their floor value against the treasury. Then the decisions we make spending on treasury directly affect the redemption value of JBX.

As a result, we can then move forward with some of the prototypes that we've been following along with. Extensions such as the JBX fee module would then reference the best price of JBX when someone contributes to the JuiceboxDAO treasury either through fees or whatnot, it would look to the market and swap there if the price is better than issuance, other it will add to our treasury and mint new JBX as it currently does.

That's part of the longer term JBX strategy. Jango hoped that we can find some stability again by the end of this year across all this expansion across versions, and then can start to reduce again and converge on V3 in this dirty JBX mechanism.

Defifa project by Jango

A few governance cycles ago, we got some support to start building this really sick game that is gonna accompany the World Cup that's kicking off on Nov. 20th, and leveraging the NFT Rewards contract and scoping it down to a very narrow specific use case.

Essentially this game is a Juicebox project that's divided into 4 funding cycles enumerated as phases for the game's sake.

Phase I: Mint

There's going to be 32 NFTs which are each different tiers in the NFT tiered reward contract. In the two weeks leading up to the tournament, anyone can mint any team for the same price (currently saying 0.022 ETH). As the mints increase, so does the game's treasury. The NFTs are in turn a claim on the treasury. During these first 2 weeks, you can burn your NFT to get your funds back, with 1:1 redemption.

So you can basically mint at will and then along the way if you no longer like the token distribution, let's say you minted England and then a ton of people also did, you can burn your England NFT and get your funds back.

At the end of the day, we're playing the game by taking the competitions outcome and trying to reflect the results onto this game and then recalibrate what each NFT is backed by, given the IRL outcome.

Phase II: Start

Once the games starts, the treasury is locked and minting ends. There's no more new NFTs, and you can't redeem or refund, the distribution of all tokens are set.

What happens in between the game is open-ended, we can bring whatever rules we want. We can say it's a winner-takes-all situation where the whole treasury will belong to the NFTs of the winner of the last game; or we can do something more interactive, let's say there's a preset amount of the treasury allocated to one specific stage game and the winner of the prediction ends up with those funds or at least has their NFTs backed by those funds.

We're probably going to lean towards doing it in a simpler way at first. Each game of the tournament will have a preset portion of the total treasury:

  • 0.416% for each of the 48 group stage games.
  • 2.5% for each of the 8 first knockout round games.
  • 5% for each quarterfinal game.
  • 10% for each semifinal game.
  • 20% for the final game.

For example, if England beats the U.S., then whoever holds the England NFTs will get 0.416% of the treasury during that group stage game, so on and so forth.

Phase III: Trade Deadline

There will be a trade deadline after the group stage, all the NFTs will be non-transferrable from the trade deadline till the game's end. We don't really know how the game will play out from a bribery perspective, and the bribery certainly is an interesting component that we're not trying to dissuade entirely. We just want to create a mechanism that reflects as much of an expected outcome as we can, which means folks can feel pretty confident that whatever happens in real life will be reported on-chain.

Phase IV: End

Once the game ends, the game is self referee'd.

Someone will upload a scorecard that basically tells the contract how the treasury should be distributed, which is going to take into account every outcome that happened in between from the start to the end. Let's say like England only won that one game and nothing else, then 0.416% of the treasury is going to England NFTs as per the scorecard.

The scorecard can say anything, but then each NFT holders across all teams have to attest to the correct scorecard to ratify it. Each NFT vote is weighted against the total supply of their team, and each team will have collectively 1 vote to attest to the scorecard.

Once the quorum is reached, the treasury is unlocked and anyone at that point can burn their NFT to reclaim ETH from the treasury according to the value determined by the scorecard. No funds will be distributed, just every NFT is now backed by the funds in the treasury in accordance with the team's result and also spreaded across the distribution of all token holders.

The coolest thing is that, you can fork this to run your own version of this whole thing, you can basically repeat this experiment for any tournament or anything you want, where you just basically mint a distribution to fund the game and have the same pieces that you minted also as a function of the outcome.

Roadmap of this Defifa game:

  • We're going to start with the quick website by the end of the week, which just has this header and the rule section;
  • We'll ship it on;
  • We'll add the mint section hopefully by next week;
  • We'll kick off the game two weeks before World Cup openning games, which will be Nov. 05;

The only new contractual component is the attestation scorecard piece, which we've come to terms with the parameters and how it's built, so all is good.

The art is phenomenal, shoutout to Mieos for tuning together each of these teams, all of them have a little aesthetic feel, which is very delicious.

Juice accounting by filipv

Filipv did a demonstration of Juice accounting app, which he made originally for JuiceboxDAO but ended up making it generic for all Juicebox projects.

If you want to get accounting for a certain project on Juicebox, you can input the required parameters and get some information for this project in return, which can be pretty useful for some project creators looking to deal with taxes etc. in a given jurisdiction.

Let's say we want to get accounting for TilesDAO, we put in the project ID, the protocol version and put in the fiat currency that we're using, it will touch things and write to the folders. For example, if we open up payments folder, it gives us the time stamp, ETH amounts, fiat conversion at the time of payment, and the caller.

You can download here and try to run the app if you want.

And also another app to calulate fees in the Juicebox protocol, which is only meant for JuiceboxDAO at this moment.

Juicetool nance update by jigglyjams

If you go to the Juicetool Nance page, it will load the proposals that are currently tagged. Here it shows # TBD, becuase we don't give the proposals any proposal ID until it passes the temperature check.

By clicking the New Proposal, you can have this proposal template: This template allows you to select a payout that goes to an address or a project, and specify the amount and number of cycles. And also it will resolve ENS name in the Receiver address.

Once you finish filling the fields and hit Submit, we get a proposal created. When you submit a new proposal, we'll still push it to Notion at this point.

Longer term roadmap for Nance:

  • migrating JuiceboxDAO off of Notion to Dolt (a SQL database).
  • figuring out the way to host on IPFS.
  • getting version controls for our governance batabase.

Says who? with Felixander

And the correct answer is ... Sage.

MCSA update by 0xSTVG

MCSA(Marin County Swim Association) is a nonprofit providing opportunities for people who can't afford to be in some high level tournaments, camps or clinics. On Oct. 16, 2022, MCSA will be hosting a Shooting Academy with Gold Medalist/NCAA Champion Jamie Neushul and 2020 Olympian/NCAA Champion Hannes Daube. This event will only charge $45 per person and MCSA will cover the balance of around $2,000 total.

OxSTVG would like to thank all the people who have donated and support the MCSA Juiceobx project and want them to know that the funds are being used in a positive way. A lot of people who would not have exposure to this type of high-level talent coaching can get their oppoutuity through the help of MCSA.

Bonus: Juicy Treasure with Nicholas

Nicholas set up a Juicebox project called Juicy Treasure and put the project ownership NFT on auction on Zora, as a nice little experiment to get more people thinking about the different mechanisms of Juicebox.

· 8 min read

Town Hall banner by Sage Kellyn Art by Sage Kellyn

Tech update with jango

V3 Contracts Update

jango: A week ago, we deployed the V3 contracts. We need to set up the juiceboxDAO funding cycles on V3, which will be a transaction that all the multi-signers have to sign for, and we have to synchronize it with the V2 and V1 funding cycles. So we're going to queue up this transaction to kick off V3 funding cycles this Saturday, run a quick 7-day funding cycle and then reconfigure it to align with the 14-day cycles of V2 and V1.

launch of 1st V3 FC

The V3 cycle won't have any payouts from it, nor have any redemptions. It'll basically just be a place for fees to come into from projects operating there. All is looking good.

And then we toss the ball back over to frontend to help with the user journey of versioning, and there's some subgraph related work that peri's working on. Maybe Aeolian can give a few updates on how versioning is going on your end.

Aeolian: Yeah, the codebase is ready for V3, or at least it's being reviewed without something to get merged yet. And peri's working on adding V3 support to the subgraph. Once that's done, we'll merge those two together and then we've got V3 on the frontend. Getting that out of the door, we'll then go full steam ahead on the upgrade path.

jango: Cool! Once the basic stuff is done, we should be able to start launching projects on V3, and then, as Aeolian said, move onto the upgrade paths for v2 projects and V1 projects to move over to V3, which is a pretty big deal. It feels good to finally have this end state of V3 that feels very stable. We've gone through iterations in production the past 3 months or so on V2, and we're looking forward to helping projects make the move over to V3 and helping V3 projects launch.

I spent the last week re-calibrating the NFT Rewards contracts, which were done prior to this versioning PR and just needs a slight API change to how the datasources are being called.

I've been also working on the Defifa game leveraging NFT Rewards contracts, which have been really useful to stress test some concepts that we are incorporating into the base contracts. NFT Rewards redemption is not a feature currently available in, but the NFT Rewards can be used as a redemption token, so that you can mint them and then redeem them to get overflow back, as opposed to your project tokens. We'll just add a few more properties in there to make sure that the tracking of token IDs and burn count of tokens etc. is going through cleanly, which enables the first phase of the Defifa game.

And it's always been useful building on top of the contracts at the time you're rolling them out or you're crossing the finish line, to make sure APIs are tight and some concept steps are extensible enough. But in any case, the NFT rewards contracts will be easier to iterate on than the core protocol, since they're just attached to any funding cycles.

To even prevent the need for that iteration, we're also trying to stand up a Code4rena audit contest for the NFT rewards contracts. There's a pretty cool plan with regards to this in the works stewarded by Nicholas. Maybe nicholas wants to give an update or some insight on what we're thinking there.

Code4rena Audit Contest Game Plan

nicholas: So a couple weeks ago some people from C4A got in touch and suggested that they were interested in creating a Juicebox project for each protocol potentially out there on Ethereum, or at least ones that have created pages with C4A, so that anybody could drop funds into another project dedicated to doing C4A audit contests for other people, because they've observed that DAOs and companies often pay for auditing other software that they depend upon for their contracts or services.

We also feel that maybe individuals would be interested in doing that, too.

It's a little bit slow going trying to figure out how to do that integration with them, so we're thinking of just dangling the carrot by doing it ourselves first. Jango came up with a cool idea to just create a Juicebox project that anybody can contribute to and that will be dedicated to an audit of the NFT Rewards contracts with Code4rena. In the future, we will create a proposal to help fund that. If the DAO decides to support and is willing to pay for the whole amount of the audit, which would be the distribution limit for that project, everybody could potentially be refunded their initial contribution.

This is a little experiment of us and hopefully it'll get C4A to start thinking in terms of how they can receive funds from Juicebox projects.

jango: That's pretty cool if you take into account open source codes that no one is technically responsible for. Although I guess in the sense of Juicebox the JuiceboxDAO has somewhat claimed stewardship over the repo, there are many projects could be more open-ended. So creating a treasury where anyone from the public or anyone who's depending on that piece of infrastructure can contribute to, will help fund the wardens to look over a code, which would be pretty cool. Obviously if an organization wants to sponsor it instead, as Nicholas has said, then the original donors can just redeem their tokens for the proportional overflow which might be the full amount they paid.

nicholas: It's cool, and the partnership potential is actually really exciting because it's basically a win for everybody:

  • New projects could be created if C4A goes forward with this.
  • Code4rena would have all this money essentially captive for their contest audits.

I think this integration has a good chance of happening, even though it's a little bit complicated to imagine getting it rolling at scale permissionlessly for potentially any contract. I'm excited to try it with this audit.

jango: I feel pretty comfortable rolling the NFT Rewards contracts without the audit contest, but since we've already been on this tightening game for so long, it feels worth the extra week to move it past the finish line, and have it looked over by third party wardens as well. So If you see a project in the next couple days that's devoted to funding the audit contest, I may throw in there and others are welcome too. That way, when JuiceboxDAO does come in later, we don't have to do this whole retroactive compensation stuff that we've been doing in the past governance cycles. Let's get this thing through the finish line, we are very close.

Visibility update with brileigh and matthewbrooks

brileigh: New release of Juicenews is out.

We also released a new Juicecast episode today with JuiceboxDAO contributor 0xSTVG, to talk about the Marin County Swim Association, a Non-profit project he created on Juicebox.

And a config article for Lexicon Devils, with another one for FORMING project that Lexicon Devils created incoming later this week.

matthewbrooks: We're making a multi-part deep dive podcast on ConstitutionDAO, so if any of you are able to connect us with people who were closely involved with constitutionDAO or important to that project, that would be awesome.

0xSTVG: It would be interesting to get the perspective of the Chinese Community when it comes to ConstitutionDAO. Maybe somebody can help connect some of those influencers from that side, because I know that was a huge push in the DAO and the Discord when that happened.

matthewbrooks: Absolutely. We're looking to have a very robust overview of ConstitutionDAO, from a lot of different perspectives. It's not going to be one narrative, but we will be pooling together a lot of different folks who will be speaking to all the events that unfolded. We would be super down to talk to folks from that side of things as well.

Update on JB high and new article with Felixander

Felixander: Regarding JB High, I think it will actually be live this week, though still in its very nascent stage. Huge thanks to the Peel team particularly Blaz who has taken the lead on that.

The idea is to create something where project creators can jump in and immediately get a really quick and good understanding for how to launch a project, as well as the different tooling options available in this space. We're going to make the JB high into a educational hub and put in a lot of this leveraging content that we've made.

Regarding the article, I am also working on a config style article that's going to start with ComicsDAO, next probably with SharkDAO. And that's really also going to take a little bit of a signal for what JB high is trying to do and almost be like a Frequently Asked Question for how to deal with projects from a different project's perspective every time. So for ComicsDAO, why did they set their particular configs? when did they change that discount rate? why did they do it? I'll probably publish this article in a form of interview with questions and answers, so that it will be easy for project creators to quickly get the information they want.

Two truths and a lie with Felixander

The correct answer this time is ... kenbot of StudioDao

· 9 min read

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

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. 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 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 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


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 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.

· 13 min read

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 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

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


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 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.

· 5 min read

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.

· 18 min read

StudioDAO updates with @kenbot

kenbot: How can the audience finances the movies they want to watch? How can we really put the audience in charge?

StudioDAO is defining in a different way what a DAO can be.

Problems in the traditional filmmaking industry

The traditional financing for filmmaking is more or less like this:

  1. you go and sell the movie to investors,
  2. investors take the equity, the rights to distribute the film,
  3. investors make 120% on their money and get 50% of everything that the film makes after that.
  4. This is not so great for filmmakers.

The problems that we're think about is:

  • Why is financing a film so hard?
  • Can we make this easier, simpler, more fluid?

The current difficulties are:

  • Filmmaking is a risky market, people are afraid of risk;
  • It's hard to invest in this industry;
  • Film distribution is a mess;
  • Movie theaters are a mess.

These above problems have contricted the people who can actually buy films or TV shows to big streaming companies, which is not great because there're only limited buyers in the market, and will lead to:

  • Filmmakers are not in control of what they're making;
  • Fans essentially become bag holders that are just getting dumped on at the end of the process instead of actually being at the beginning of it.

The solution of StudioDAO

The solution of StudioDAO to these problems and the way it should be at some point in the future, is to turn itself into a new kind of social network that solves the problem of financing premium contents.

  • Members pay to join the DAO;
  • Members get to green-light the films;
  • Members get to be on the inside of this process.

So this is going to create unprecedented freedom and opportunities for filmmakers and fans. It's a new voice at the table in terms of how things get made and a more direct relationship with all the talent they might care about.

The way that this business works right now and what StudioDAO can do in the future, can be really harmonizing. StudioDAO is going to build a system where we can partner flexibly with projects, whether they're just starting or they're finishing and just need a littile more money to get over to their green light.

The relationship between the community and the filmmakers, no matter where the filmmakers might sell the films, to Netflix or to theaters, the community participates in that and gets 30% of the revenue that the film generates downstream. So the community is not just green-lighting movies for their own consumption and enjoyment, they are essentially building the films into a part of the bigger community of StudioDAO.

By this way, it basically leads us to 3 different ways to finance:

  • Sales of the retail NFTs;
  • A community wallet that we're going to be funding at the beginning;
  • Revenues from previous projects.

The film financing fund

When we think about how the business works here in terms of the traditional piece, there's a way for us to actually create a more traditional fund that wants to play nicely with the rest of what we're creating.

You can imagine, if you had a US$5,000,000 film and you can sell $1,000,000 worth of NFTs, that should be a really good signal to people who want to put other money into the project, because it's appealing and there's people who are behind it. So we're trying to create leverage beyond where the retail market is for NFT's right now, because it's still early and the market is small.

There's a 2 trillion dollar entertainment market out there, we think that there's a clear scenario for decentralized studio that can do a billion dollars of production per year in three to four years from now. we're actually talking with some of the people who funded Kickstarter at the beginning and they shared that Kickstarter actually funded 500 million dollars worth of films in the 10 years that they've been in business. We all agreed that with Kickstarter not being focused on films and not having the benefits of everything that on-chain applications might be able to give us, I think we can shoot for 10x that in the next 10 years. Our target is five billion dollars over the next 10 years worth of films and content.

Disclaimer: This is not legal advice, I'm not a lawyer. This is what we're doing, but I don't guarantee that they won't get you in trouble if you do the same thing.

We have 3 legal entities in the US, two of them are Delaware LLCs and one of them is an Unincoroporated Nonprofit Association(UNA) in Nevada.

The StudioDAO UNA is the nonprofit that will become the million-people-green-light committee. This is the true DAO of StudioDAO, the membership of the community. It's the committee that is picking films, working on financing of films, managing the green-light fund and voting in the governance over the protocol. It's also the recipient of 30% of the participation of the contracts that we are sourcing for the UNA right now and we're sort of creating a legal structure to do that.

StudioDAO Genesis is the legal entity that belongs to StudioDAO UNA so that it can have certain kinds of bank accounts that UNA may not be able to have on their own.

The StudioDAO Backlot is a for-profit services company, it mirrors sort of the structure of Uniswap, in terms of Uniswap Labs, and then the protocol being a separate piece. Obviously we're completely different in almost every other direction, but the process of where you do the product development(the StudioDAO UNA), how do you do the things that have to happen in the real world (the StudioDAO Backlot), is how we're splitting at.

Projects on Juicebox

  1. The StudioDAO Backlot.

For the Backlot, the token issuance is 1,000,000 / ETH, while 700,000 goes to the contributor, and 300,000 is reserved for the projects owner.

  1. The Unlikely Love Stories:

This is a real project, and it will probably be the first juice box that goes live when we're ready to go.

The issuance rate is 840,000 tokens / ETH with 50% reserved rate, so contributors will get 420,000 token per ETH.

The funds distribution will be 90/10, 90% of the funds will go to the project itself, and 10% will go to the StudioDAO Backlot juice box and generate more green-light power tokens that go back to the filmmaker in exchange for a 10% fee.

The tokens distribution will be 50% for filmmaker, 40% for the UNA and 10% for the Backlot.

  1. The other two projects are all for educational purposes.

Juice newsletter

matthewbrooks: So this is a really quick preview of the newsletter.

  • Recap by @0xSTVG,
  • Governance cycle recap by @matthewbrooks,
  • Podcast episode by @matthewbrooks and @brileigh (if there's a new one),
  • Tutorials by @nicholas or @filipv or someone else (if there's a new one),
  • Recent articles on the blog,
  • Town Hall recap by @zhape,
  • Some links at the bottom.

So yeah, that's pretty much simple. It's just an easy way to recap everything happening on the content side and also giving everyone a chance to catch up with the basic goings-on. It's just to keep everyone informed and to also repurpose the content that we're making so that we can get more people to see it and hopefully get a better engagement with the content that we're making.

brileigh: Shout at @nicholas for all the feedback as well as @Felixander and @Sage for all the help for putting this together. And just echo as @Matthewbrooks said, a quick easy way to figure out everything that's going on within Juicebox without having to do the manual work to pull all the information together.

nicholas: I think this is gonna be great for getting better distribution or increasing distribution of stuff we're already producing, because I think a lot of people are consuming the Juicebox content that several members of the DAO are producing via Twitter and Discord. But to try to reach people who maybe not on Twitter or not in the Discord regularly, you can imagine, if there was a newsletter sign-up link on the website during ConstitutionDAO or AssangeDAO periods, some number of the people who participated in those fundraisings might have stuck around for the newsletter. So I think a newsletter is a really good experiment to see if it engages people. I really love what you did with the layout and everything, it looks great.

filipv: I can give a brief update on some of the legal stuff that I've been working on with @tankbottoms.

In short, we set up some structures for MovementDAO, PeaceDAO and a few other entities that are building things related to the Juicebox protocol.

We created a number of structures that are similar to what StudioDAO did. We have two different Unincorporated Nonprofit Associations(UNA), one in Delaware and one in Nevada, as well as a few LLCs in Delaware and Washington for different intellectual property. We also put together a number of intellectual property agreements and things like that.

For the short term, we're just using these for these DAOs. If you want to check out these documents you can find where they are now on this website

But what we're working at is templatizing a lot of the things for common use cases for Juicebox projects, and then letting people put in metadata about their projects and then having it spit out nice looking PDFs. There's like a lot of interesting stuff in here if you're interested in this sort of thing that we're hoping to to roll out to more people pretty soon. by @filipv and @peri

filipv: I also want to do an update on

For those of you who didn't see it, it's a rewrite of but completely on-chain, so the algorithm to render the Tiles is completely in Solidity. The website is written in Svelte which is super cool because it lets people compile the components and use it with different frameworks if they'd like to. It's also a little bit more portable, so you could imagine someone setting up an npm package using different components or something else.

This website has NFT minting and mint pages as well as a fully featured Juicebox treasury, it doesn't have configuration yet. So you still need to configure on or another website, but for people who come here to contribute to the project, it's all working on this website. This is all open source and available on GitHub.

peri: I can talk on the Tiles project for a second. Tiles is an NFT art project that I put out about a year ago. It was actually launched on day 1 of Juicebox lifetime, it was Juicebox project No.2, next to JuiceboxDAO. The artwork is rendered using a server, so you can basically buy these NFTs but their artwork is rendered off-chain, which is not as cool as rendering artwork on-chain.

A few months ago @tankbottoms came in and decided to try putting the artwork on chain, and he did. It's amazing amount of work that he did to get that working. I don't even know why he wanted to, he just did. So big shout out to @tankbottoms, I wish he was here now.

And @tankbottoms went ahead and deployed a new V2 of the Tiles NFT contract a couple days ago. So it's live now at the website. There's still some things that are up in the air right now. The main thing that I'm concerned about is that I really want everybody who has the original V1 Tiles tokens can get the same Tiles. Tiles are denoted by a wallet address, a 40 character hexadecimal string. I basically want to make sure that everybody can get the same matching Tiles, and the V2 token that they have for their V1 token. There's a chance that the contract will get redeployed to make sure that we can settle those balances, airdrop tokens to people or make them claimable as needed. So there'll probably be somemore updates coming in the next few days, @tankbottoms and I are chatting on some of that stuff.

filipv: There's a seizing functionality on, so someone mints the Tile that corresponds to your wallet, you can mint that Tile and take it from them. And the same is true for the V1 TILE token. If you own a V1 TILE and someone mints a TILE with the same address, you can mint that TILE and claim it from them, for free. @tankbottoms and @peri are thinking about a new price revolver for the contract, so there might be a new contract soon. Maybe chill out for a few days before minting.

peri: Yeah, I would say hold off on minting any Tiles in the website for now.

filipv: One last thing, the repo has a new license on it which basically says that people can only use it if they're pointing revenues at a Juicebox project. It's a little experimental license, but we're trying out some funky stuff to make licenses for a code to do interesting things.

Protocol data by @twodam

Dune dashboard update

twodam: Here is the main dashboard for the Juicebox protocol.

If you scroll down a little bit, you can see the section called period so you can select different periods.

After you select the period, scroll back up and click apply all parameters, and all the stats will refresh using this new period.

Basically we are using the page to do the weekly reporting, so you can see there is a value new projects and active projects in this period.

There is the trending projects:

You can see many links in blue, if you click the See more, it will take you to the related dashboard of that project, with the overview data, like how much total raise, how many tokens and how many token holders in that project.

And on the right bottom of that project page, there's a small logbook where you can see all the actions taken by people there and all the payment Memos if there is any. And you can click all the links, they will take you to the relevant Etherscan pages of those transactions.

Zeugh: What's the meaning of Fully Diluted Valuation here?

twodam: It's the value that equals to total token supply multiplied by market price.

nicholas: By market price, do you mean AMM price or which price?

twodam: If they have an AMM price then it will be used, if not, redemption price on Juicebox protocol will be used instead.

And back to the protocol overview payge, there is this All users If you click the See more after an ENS/Address, it will take you to the dedicated page of that person/address. Let's take @jango's as an example:

jango: Man, I feel this is full-fledged superpowered graph interface for projects. I wonder if we need to build a documentation on how to navigate this into the info site or Juicebox High or something? maybe in a more tucked away Data section or something?

twodam: Yes! I would love to.

One more thing, if you scroll down to the bottom of the protocol overview dashboard, you can see the the current trend of the ETH in the whole protocol.

Twodam's complete Dune dashboards are here.

Juicetool update

nicholas: Can we also look at Juicetool?

twodam: On the front page, we click the Snapshot Plus at the bottom, we can go to the voting info page. In the middle of this page you can see the Status. That's where you can filter by active, Haven't voted, or Under quorum.

jango: @twodam, the frontend chops are fantastic, this is looking great. You've been constrained by the Dune UI just writing queries, and now actually refactoring the interface elements is a huge unlock, this looks fantastic.

twodam: Thank you, I'm still learning.

On the bottom left of each block, you can see the "jump to" symbol, which is basically the place you can click and do a quick jump to that specific Snapshot page from here.

jango: We need to figure out how to make sure that people starting their projects know this is here, and that they feel good about it. It's obviously useful, but I think most projects starting up need to orient governance around and all the things. What a luxury.

nicholas: You can vote from within this interface also.

Zeugh: Oh and it shows a green active if there is a proposal up.

nicholas:So to clarify, is that the list of spaces to which you are eligible to vote that you have voting tokens?

Zeugh: No, to which I joined. The ones I really enjoyed. I can't vote on Gitcoin, but I follow it to see what's going on, so I get to see it.

twodam: If you hover above active, you can see how many time left for you to vote. And if you have voted for this proposal, you can hover above voted, It will show which option you have voted.

nicholas: There's a feature for whether proposals are have met quorum yet or not, next to where closed. If there were active ones, you can sort, for instance, by haven't voted which means that the connected wallet has not yet voted on, and add Under quorum to see all the proposals that you have not voted on and they have not met quorum yet.

So I think if we zoom out a little bit, like this Juicetool plus what @jigglyjams is doing with Nance and some other initiatives altogether are like a suite of tools. Also think of the on-chaining stuff that we use for multisig. These are like a suite of tools that all the projects on Juicebox probably gonna need, given at least the most popular configuration for multisig, snapshot, DAOs. So I think this kind of stuff would be great in Juicebox High on how to set up. Possibly also build a version of Juicetool that the people down the road could deploy specifically for their project, so it has a dedicated URL and only covers their DAO's needs. It's really cool to see you do this. @twodam, when did you start doing front-end dev? When is your first line of HTML?

twodam: Oh. Maybe a month ago.

jango: The user experience of tying all these tools together, making it easy and obvious for people, giving them the understanding of standard and safe tools that should be used, it's fun to figure that out once all the pieces are in place and work our way to something more optimal over time. But you can just pass around links and they are hosted in all kinds of places for now, it's a good start and so useful, especially for weekly multisig stuff all the way through.

JohnnyD: Yeah, definitely came to figure out how we can to streamline this and connect them all together, so if someone new to start a project, they can have access to all these tools in a seamless environment. But yeah, as you said, it's gonna be interesting to figure out the users experience side of that.

jigglyjams: Yeah, totally. That's been on my mind lately, too. I could imagine, as long as we're still relying on Snapshot, in the project creation UI, you could just check a box and create a snapshot space, and we could send a transaction to create that. Along with that, we can add Nance instance once it's at that level. I'm working on submitting transactions for @twodam's Gnosis Safe payout changes. I want to work with @twodam to have Juicetool be the frontend. if possible. I can see that being really beautiful. It looks amazing, @twodam. It's been super cool. I watch you develop it and excited to see more.

The One Hundred Thousand Million Contest by @Zeugh

Yesterday there was a Hundred Thousand Million project of sustainable City based in DAO structure in Chile in Latin America, reached out to me to do a partnership with Juicebox.

They're trying to get attention of nice projects around web3. Because they're building a city and they think that building a city of the future is supposed to have creative people creating awesome stuff and they see Juicebox as one of those spaces, so they wanted to do a contest for giving a prize for a Juicebox project. They reached out to me to help organize that and we put out a JokeDAO contest which is going to start tomorrow,giving out 1 ETH to a Juicebox project that gets more votes. They're opening the contest tomorrow. Everyone is welcome to submit a Juicebox project and go to their Discord server to get tokens to vote.

Two truths and a lie by @Felixander

The correct answer is ... Zom_Bae The lie is the one about an albino rat.