Synopsis#

It's worth continuing to pay $12,000 per cycle and sending an upfront additional 2,000,000 JBX to Breadfruit for:

1. Jango's continued contributions to the core protocol's stability and extensibility.

   1. Lead co-author of the 3.1.1 and 3.1.2 terminals.
   2. Lead co-author of 721Delegate version 3.2 and 3.3.
   3. Co-author of Buyback delegate.
   4. Reviewer of JBDelegateMetadataLibrary.

2. Jango's continued contributions to protocol education and integration across the ecosystem.

   1. Work with Peel and client teams to help ensure the protocol is being interacted with correctly.
   2. Help with templates and comms that make hackathons more approachable for devs. Lots more I can do here.

3. Jango's being on-call to help lead the DAO through protocol emergencies.

   1. No emergencies lately, but we did have a few postmortems that I contributed quick research, troubleshooting, and sensible solutions to, adopted in 3.1.1 and 3.1.2 terminals and juicebox.money fixes.
   2. It’s still safer to assume that something unexpected is likely to happen, which might require timely attention from people with a wide understanding of how Juicebox protocol and JuiceboxDAO works.

Motivation#

Lots of works-in-progress right now. I've spent the past 4 months trying to understand how to best deploy projects I've been helping build -- like Croptop and Defifa -- as efficient public networks. This exercise kept me tugging at the JB protocol foundation to find designs that give its core levers some meaningful shape.

At the same time, I watched DrGorilla, Viraz, 0xBa5ed, Jacopo, Nicholas, and several hackathon participants give their efforts to create powerful contract stuff, my friends at Peel, Defifa and Blunt give their efforts to create intuitive and welcoming UXs for folks to interact with the powerful contract stuff, Juicecast and Juicenews try to give a personal dimension to what the heck all this powerful contract stuff is all about, many folks try to describe the powerful contract stuff in documentation, and a handful of projects try to leverage all this community effort to give a powerful juicy shape to their projects.

Inso doing, I've helped identify, fix, and navigate the DAO through important bugs, authored core improvements to the core protocol, and have been left with a handful of persisting takeaways.

Technical takeaways:

• BuybackDelegate is crucial for efficient treasury designs. It needs to be lean and mean, and I think it'll be a common feature of treasury designs. This has been a long and delicate body of work by the entire contract crew, and is at the finish line. Special shouts DrGorilla as the lead author.
• Data Sources need to have the ability to pass arbitrary data to the delegates it invokes. This was implemented in terminal 3.1.1.
• Multi-delegate is immediately needed so that delegates like the 721Delegate can be used on a project that also has the BuybackDelegate installed. This standard is currently being applied to the upcoming BuybackDelegate, as well as an upcoming 721Delegate version.
• Treasuries that manage all money access through redemptions are just as interesting as those which rely more on payouts. JuiceboxDAO should align its membership fee with redemption alongside payouts. This was implemented in terminal 3.1.1.
• I'm excited to continue researching and experimenting with unowned project designs. They have intriguing cultural properties and may have solid regulatory standing.
• I'm very optimistic on the Bananapus multi-chain strategy of building organization tentacles across chains. As chains pop up left and right, its increasingly clear organizations need to be able to exist across them. There's been some exciting recent prototype progress.
• The DAO should support getting multi-token projects right. This is an under-used and under-explored, but highly in demand part of the protocol. We should explore product potential in juicebox.money, and also put pressure on the JBPrices contract extensibility to see if there are any improvements to be made that only reveal themselves when putting the code into practice.

Cultural takeaways:

• JB Pipeline:

  • Banny is by far the most effective top-of-funnel – double down.
  • Juicecast + onboarding calls + townhalls + jbdao-as-a-community add the human touch and are great middle chunk of the funnel – we can do more here with events and hackathons.
  • JBM as the iconic application for the ecosystem is a strong bottom of the funnel – continue delightfully teaching the specifics of how the protocol can be used and interpreted.
  • The protocol will always close out the deal at the end of the funnel – keep it safe, open, and well documented.
  • The funnel inevitably leads towards a value set defined by how the JuiceboxDAO treasury and governance are programmed.

• I’m looking forward to experimenting with Retailism, and am curious to study what might be its implications to JuiceboxDAO. What I was previously calling Tend Toward Zero might be shaping up more like Tend Toward Retailism.

• I’m looking forward to being able to work on projects — like Croptop and Defifa — without having to question the efficacy of the JB protocol foundation. There ended up being plenty of core work to do these past 4 months, and there may as well be these upcoming 4, but the goal is for it not to last much longer into the future. Nonetheless, I’m grateful to JuiceboxDAO for affording me a consistent payout as I help it navigate this more-unstructured complicated creative work of the moment.

• I hope my compensation soon reflects a future where I’m working for JuiceboxDAO more through my work on other projects instead of for it directly. I think it’s the most valuable thing I can contribute. Plus, we happen to be stewarding a network technology capable of economically appreciating the contribution of workers, customers, and investors alike.

Personal takeaways:

• I work with brilliant people that inspire me in so many different ways. Thank you all for your leadership helping shape this DAOs direction, and for giving me space to contribute my pieces. Thank you for consistently taking time to give feedback, and for taking into consideration all of the feedback that comes your way. Thank you for your confidence to be creative, to bring your points of view, and to leave things better than how you found them, despite our very delicate and unforgiving onchain environment and amorphous organizational structure. I don't know how we all got here but it's a god damn miracle. 
• Lots to do.

Risks#

Breadfruit is operated by Jango, a fragile human being that could go poof.

Timeline#

Next funding cycle