Synopsis#

JuiceboxDAO ($JBX holders) should fund a 30 day go-to-market of the new $NANA (Juicebox v4) omnichain system during the month of April 2024, including audits, bug bash contests, a hackathon, and stress test for the revnets and bannyverse ecosystems built on the Juicebox core foundation. Meanwhile, we'll be driving traffic to testnet web client experiences and APIs as we begin marketing what we've been up to and as we prove out a bug-free dress rehersal of production environments across chains. Committing time and budget now will turn out cheaper than risk-mitigation on the fly over time.

It will do so by allocating a basket of Banny NFTs, $BANNY and $NANA tokens, ETH, and $JBX.

Authored by Jango.

Motivation#

Many long standing JB ecosystem research, prototyping, and implementation are about to set sail. It's a great time to recruit cross-functional staff from active DAO members, and committed auditors, hackers, and users from outside, to get everything ready to ship.

Goals#

• Run $NANA and $BANNY omnichain testnet revnets for 7 consecutive days bug free.
  
• Get people to play with omnichain revnets and bannyverse mints on testnets through clients such as the revnet app, juicescan, and the bannyverse minter, and through contract APIs directly.
  
• Spend a month code complete, focusing entirely on security, risk mitigation, documentation, and stress testing integrations with audits, a bug bash contest, and a hackathon soliciting hooks and peripheral components that may inform the core hook design tweaks.
  
• Grow the launch anticipation through distribution of cherished cultural Bannys to those who're putting in the love.
  
• Actively communicate the extent of what is being deployed to the outside world, in thoughtful ways with stories that resonate.
  
• Complete a thorough subgraph database for applications to use.
  
• By giving away a chunk of JBDAO's assets to folks who will steward their narrative, it's doing a service to the portion of the assets it's keeping.

We will fund this effort with a few different asset types. Remember that once the $BANNY revnet is deployed in production, JuiceboxDAO will use 40 ETH to buy Naked Bannys from it and will receive $BANNY alongside.

Budget#

• 16 Alien Bannys (out of 30 Alien Bannys it will have, costing 30 ETH of the 40 ETH JBDAO will spend.)
  
• 48 Pink Bannys (out of 80 Pink Bannys it will have, costing 8 ETH of the 40 ETH JBDAO will spend.)
  
• 92 Orange Bannys (out of 200 Orange Bannys it will have, costing 2 ETH of the 40 ETH JBDAO will spend.)
  
• 40m $BANNY tokens (out of 60m $BANNY tokens it will have, from premint of 20m and from contributing 40 ETH)
  
• 79k $NANA tokens (out of 37,000,000 $NANA it will have from the premint)
  
• $151k USD of ETH
  
• 16.5m $JBX

We will use this budget to compensate security and marketing efforts.

Staffing & Allocation#

• 4 Alien Bannys, 12 pink Bannys, 12m $BANNY, 32k $NANA, $24k of ETH, 12m $JBX split to contract crew (jango, DrG, 0xBa5ed, nowonder) to manage the month of stress tests – bug finding contest, test writing, and a hackathon. We'll be full throttle for the month. The NFTs, $BANNY, and $NANA assets are only cherished if the infrastructure being tested holds.
  • Auditors and hackathonists will be asking questions about how things work, and throw potential findings are us all month. We need to be responsive to these and make adjustments on the fly if needed.
  • We need to continue throwing everything we've got at the codebase, including more edge case unit testing and integration testing for each component.
  • We'll be putting up new deploys weekly that reflect that week's findings.
  • $24k of ETH and 12m $JBX paid upfront to Emergency Devs multisig (0xd0a12b8279614A46b75Dc23DBB3245094a3f2A49) for further distribution amount stated participants. Bannys, $BANNY, and $NANA allocated to this same multisig once acquired after a successful deploy.
    
• 2 aliens, 2 pink Bannys, 2m $BANNY, 4k $NANA, $8k of ETH to great documentation for those learning, auditing, hacking, and otherwise using the core omnichain stack and peripheral components (filip, jango).
  • API docs for each component
  • Overview doc for each component
  • Multichain architecture docs
  • Integration guides
  • New user docs
  • Update the old docs
  • $8k of ETH to 0xb9459B4248f585909EA6fB9E91C4576A84750fC2. Bannys, $BANNY, and $NANA allocated to the same address once acquired.
    
• 3 aliens, 6 pink Bannys, 3m $BANNY, 6k $NANA, $9k of ETH to help collect/organize client-side bugs, tell the story of whats going on with $NANA and $BANNY, the Banny NFTs' underlying infra, and making internal happenings accessible to the outside world (matthew & brileigh & sage). Ramp up content production, maybe quick hitting interviews with builders, etc. Lets make sure everyone knows what's happening, and the public's interaction points work beautifully.
  • Attract hackers and testnet users to come play on the new omnichain infra.
  • Explain wtf $BANNY and $NANA are and how they fit into $JBX, using visuals and narratives.
  • Help inwardly focused developers and community members share their POVs on the systems with the outside world, making the project more relatable.
  • Help collect bugs on the UI/UX side of things as users play with it all.
  • $6k of ETH to Juicecast JB project, and $3k of ETH to sagekellyn.eth upfront. Bannys, $BANNY, and $NANA allocated 2/3 to Juicecast, 1/3 to Sage once acquired.
• 4 aliens, 14 pink Bannys, 50 orange Bannys, 5m $BANNY, 5k $NANA, $70k of ETH as rewards for bug bashers, auditors, and hackathonists managed by contract crew. Contract crew is assessing auditors and will be responsible for allocating these funds, while contract crew also manages the hackathon. We will pay auditors 70k (50%) upfront and give them an option of 70k after their work is complete OR receiving a basket of assets listed above. If ETH is chosen instead of the assets, we're proposing JBDAO contribute another 70k worth of ETH and take back the allocated basket of assets into its treasury. Part of the fun for bug hunters is learning how all these assets fit into the stack they're auditing.
  • ~8800 lines of code, done by 2-4 indy auditors separately (we'll post info about who they are asap), with mitigation report deliverables and a commitment to work with contract crew to revise anything that needs love. Auditor candidates include: vnmrtz (https://github.com/Elpacos/audits), 0xWeiss (https://github.com/maarcweiss), Chimay (https://github.com/chinmay-farkya), Nirlin (https://code4rena.com/@nirlin), and 33Audits (https://github.com/leeftk).
  • $70k of ETH upfront to Emergency Devs multisig (0xd0a12b8279614A46b75Dc23DBB3245094a3f2A49). Bannys, $BANNY, and $NANA allocated to this same multisig once acquired after a successful audits and deploys.
    
• 1 Alien, 3 Pinks, 20 Oranges, 10m $BANNY, 10k $NANA, $15k USD of ETH, and 1m $JBX as a raffle/airdrop or other recruiting/growth effort by brileigh and matthew.
  • testnet + social incentives e.g. add 🍌 to your display name, follow /banny channel, complete testnet transaction
  • meme incentives e.g. share your custom banny, share your banny meme
  • edu incentives e.g. share a thread and/or infographic on how revnets and/or $BANNY works
  • $degen in-app tips for completing testnet transactions, share your banny meme or art
  • interface bugs and UI/UX incentives e.g. find a bug on revnet.app or banny minter
  • hackathon recruiting/rewarding, running ads for examples of stuff that can be built. even if people dont join the hackathon, it shows what JB is to people.
  • $15k of ETH and 1m $JBX upfront to juicecast.eth
• 2 alien Bannys, 5 pink Bannys, 10 orange bannys, 2m $BANNY, 10k $NANA, $16k USD of ETH, and 2m $JBX split to Revnet implementers (aeolian, jango) for tightening the omnichain revnet experience, which are heavily depended on for the financial aspects of $NANA and $BANNY. Revnet already has a milestone based budget that stays in effect, with next milestones being after production deployment.
  • Revnet.app currently works well for single-chain revnets (dash and create flow). we need to extend this to omnichain revnets.
  • As testnet feedback rolls in, we need to iterate and tighten.
  • $8k of ETH to Breadfruit JB project, and $8k of ETH to aeolian.eth upfront. 1m $JBX to breadfruit.eth and 1m $JBX to aeolian.eth upfront. Bannys, $BANNY, and $NANA allocated to this spread after a successful deploys.
    
• 6 pink Bannys, 12 orange bannys, 6m $BANNY, 12k $NANA, and $9k USD of ETH, and 1.5m $JBX split to omnichain interop builders (0xBa5ed, Jango, and filip). The bulk of the omnichain components have already been built and funded through the most recent bananapus proposal, however the odds and ends of the omnichain components are proving demanding and require more funding to get stuff across many chains.
  • We've currently got a working prototype of merkle proof generation server that allows users of a revnet on one chain to suck into another chain. We need to tighten this server for production and include it into revnet and juicescan interfaces in a way that is smoothbrain for casual users who'll be testing during the month.
  • $4k of ETH to 0xba5ed.eth, $2.5k of ETH to Breadfruit JB project, $2.5k of ETH to filipv.eth upfront. 0.8m $JBX to 0xba5ed.eth, 0.35m $JBX to breadfruit.eth, 0.35m $JBX to filipv.eth upfront. Bannys, $BANNY, and $NANA allocated to this spreadafter a successful deploys.

Contract repositories being audited#

NANA CORE#

https://github.com/Bananapus/nana-core Juicebox core contracts, where projects can describe what happens when they receive funds, under what conditions a project’s tokens can be redistributed, and at what cadence can the rules change over time.

NANA SWAP TERMINAL#

https://github.com/Bananapus/nana-swap-terminal A terminal that accepts payments for projects in various tokens, swaps into a token the project is willing to store, and forwards to the next relevant terminal.

NANA PROJECT HANDLES#

https://github.com/Bananapus/nana-project-handles A contract allowing a project owner to link their project to an ENS name of theirs.

NANA ADDRESS REGISTRY#

https://github.com/Bananapus/nana-address-registry A contract that stores a reference to the deployer contract for hook instances.

NANA 721 HOOK#

https://github.com/Bananapus/nana-721-hook A hook that triggers when a project receives a payment, minting 721’s in consequence.

NANA BUYBACK HOOK#

https://github.com/Bananapus/nana-buyback-hook A hook that triggers when a project receives payments, routing the payment to buyback a project’s tokens from a uniswap AMM if the quoted price is better than the price the project is willing to issue new tokens for.

NANA SUCKERS#

https://github.com/Bananapus/nana-suckers Cross chain infra for juicebox projects, allowing holders to bridge project tokens while also bringing the project’s treasury funds alongside.

NANA OWNABLE#

https://github.com/Bananapus/nana-ownable An extension of OZ Ownable that can also specify ownership as the current owner of a Juicebox project.

CROPTOP#

https://github.com/mejango/croptop-core
 A utility that allows a project owner to let the public post new NFTs to its project on the owner’s behalf, so long as preprogrammed criteria are met.

REVNET#

https://github.com/rev-net/revnet-core A contract design to own a Juicebox project to enforce a sequence of money rules over time.

BANNYVERSE#

https://github.com/mejango/bannyverse-core A project that ties all the above repos together to sell Banny NFTs with revenues going to a $BANNY revnet.

Clients#

REVNET.APP#

https://revnet.app Interact with $NANA and $BANNY revnets financially across chains, and allow anyone else to deploy their own omnichain revnets.

BANNYVERSE MINTER#

https://banny-minter.vercel.app/mint Buy and dress Banny NFTs.

JUICESCAN#

https://www.juicescan.io/ Raw Juicebox data to cross reference configurations.

Specification#

Total budget#

This budget is the full lushness. I'm asking the community to help refine and reduce from here, though the "audits & contests" cost will be harder to save on while still getting great attention.

The $221k would be spent if auditors prefer their ETH option over their $NANA+$BANNY+naked bannys, which would then return the cultural assets to jbdao.

The only caveat to this budget is that we will provide auditors with half of their compensation up-front (the USD worth of ETH), and the other half will be an option we will give folks to either take the cultural assets OR more USD worth of ETH. We need JuiceboxDAO to be comfortable allocating another $40k worth of ETH and taking back the 4 aliens, 14 pinks, 40 oranges, 5m $BANNY, and 5k $NANA. We believe the auditors will all take the assets after having audited the stack.

The allocations are as follows, repeating from the Allocations section:

• $24k of ETH and 12m $JBX paid upfront to Emergency Devs multisig (0xd0a12b8279614A46b75Dc23DBB3245094a3f2A49) for further distribution amount stated participants. Bannys, $BANNY, and $NANA allocated to this same multisig once acquired after a successful deploy.
• $8k of ETH to 0xb9459B4248f585909EA6fB9E91C4576A84750fC2. Bannys, $BANNY, and $NANA allocated half-and-half once acquired.
• $6k of ETH to Juicecast JB project, and $3k of ETH to sagekellyn.eth upfront. Bannys, $BANNY, and $NANA allocated 2/3 to Juicecast, 1/3 to Sage once acquired.
• $70k of ETH upfront to Emergency Devs multisig (0xd0a12b8279614A46b75Dc23DBB3245094a3f2A49). Bannys, $BANNY, and $NANA allocated to this same multisig once acquired after a successful audits and deploys, if that option is chosen over another $70k from jbdao.
• $15k of ETH and 1m $JBX upfront to juicecast.eth
• $8k of ETH to Breadfruit JB project, and $8k of ETH to aeolian.eth upfront. 1m $JBX to breadfruit.eth and 1m $JBX to aeolian.eth upfront. Bannys, $BANNY, and $NANA allocated to this spread after a successful deploys.
• $4k of ETH to 0xba5ed.eth, $2.5k of ETH to Breadfruit JB project, $2.5k of ETH to filipv.eth upfront. 0.8m $JBX to 0xba5ed.eth, 0.35m $JBX to breadfruit.eth, 0.35m $JBX to filipv.eth upfront. Bannys, $BANNY, and $NANA allocated to this spreadafter a successful deploys.

Rationale#

This may feel like a bunch of separate proposals bundled into one. I think this is the best way to do this one, we need to come together and act in sync with clear understanding of everyone's roles and compensations along the way. JBDAO should want to commit to the full extent of this proposal, or none of it. It all needs doing if we're to come out of the gates in full swing while minimizing risk.

Risks#

There are moving parts. Jango will do his best to manage the whole month-long effort

Timeline#

The ETH and JBX should be allocated right away. The naked bannys, $BANNY, and $NANA will only be allocated after all networks have been deployed to production.