Approved

JBP-465: Fund juicebox.money maintenance

Cycle

65

Requesting

123,500 USD + 10,000,000 TOKEN

loading

Proposed Transactions

Payout action loading...
Transfer5,000,000TOKENto0xE16a...357B
Transfer5,000,000TOKENto0xf0FE...abAd

Synopsis

Pay $6,175 per FC to maintain the juicebox.money website (JBM).

Motivation

JBM is an essential and valuable asset to Juicebox DAO and JBX. It remains the primary gateway to the Juicebox protocol.

But like the Juicebox protocol, JBM has reached a stage where large updates are scarcely needed. We believe that, given the great work done by the JB and Peel teams to date, JBM will continue to serve the DAO mission statement in improving market conditions, as long as it is kept alive and reliable: "help people confidently fund, operate, and scale programmable treasuries on Ethereum."

We propose that 2 developers - aeolian + johnnyd - take responsibility for keeping JBM alive moving forward.

Responsibilities are limited to the following:

  • Fixes to critical JBM bugs. We define a 'critical bug' as a bug with some or all of the following characteristics:
    • Site unavailability/outages
    • Has directly caused (or could cause) loss of funds (project owner or payer)
    • Inhibits the user performing core Juicebox functionality successfully and accurately (e.g. creating a project, paying a project, redeeming tokens).
    • Grossly misleads users (e.g. showing incorrect/inaccurate data)
    • Medium-to-high-severity security vulnerabilities
  • Management of JBM operating expenses, including:
    • Infura ($200/m, varies by traffic, has been as high as $400/m)
    • Vercel ($40/m)
    • Supabase (~$40/m)
    • Fathom ($140/yr)
    • Namecheap ($60/yr)
    • Heroku (~$20/m)
    • Postmark ($25/m, currently on free tier)
    • TOTAL => ~$342/m => ~$175/cycle
  • Communicating with DAO members and users specifically regarding bugs, potential bugs, or security vulnerabilities.

Note that there is no specific feature work being proposed here. Any future feature development will be proposed to JBDAO with scoped budgets.

Specification

  • US$6,175 per cycle for 20 cycles to JB Project#609
  • 5,000,000 (5 million) $JBX to aeolian.eth
  • 5,000,000 (5 million) $JBX to johnnyd.eth

Rationale

  • JBM should be kept alive for as long as possible, to be ready and available for future project creators.
  • Aeolian and JohnnyD are highly knowledgeable and efficient in the JBM codebase, and have a proven track record of timely bug fixes. They are competent across the entire JBM feature set.
  • Have JBM’s frontend devs focus purely on reliability, as opposed to new features. Let the JB protocol and JBM do its thing, reliably.
  • Budget: $3,000 per cycle to each johnnyd and aeolian, + ~$175 per cycle for operating expenses.
  • Reduce JBDAO’s JBM expenditure.

Risks

  • The responsibilities outlined above fail to be met over the next 20 cycles.
  • JBM will become less relevant over time without strategic product investment.

Timeline

This proposal should take effect immediately. It should be active for 20 cycles.

Votes

loading