Approved

JBP-470: Seed Juicebox V4 frontend public goods

Cycle

66

Requesting

10,000 USD

loading

Proposed Transactions

Payout action loading...

Synopsis

Provide $20,500 initial funding for Juicebox V4 frontend public goods, including an SDK and barebones source-of-truth interface.

Motivation

A number of dapps are set to run on Juicebox v4, including revnet.app, defifa.net, one day juicebox.money, and likely more.

When developing dapps, two sets of tooling are useful:

  • a source-of-truth interface, that accurately presents all of a Juicebox project's information. This allows developers to cross-check their own apps against a trusted source.
  • an SDK, to maximise time-to-market and developer efficiency.

These both exist for Juicebox V3: juicebox.money is the source of truth, and we now have a V3 SDK used in production by juicecrowd.gg. These will not support Juicebox V4 for the forseable future.

I propose we build similar tools for Juicebox V4.

Tooling specification

  • Develop juicescan.io, a barebones, feature-minimal browser for Juicebox V4 projects. It will show every possible detail about a Juicebox project, intended to be a source of truth for developers and analysts. It will only support the core juice-contracts-v4 and no extensions for the initial build.
  • Develop juice-sdk-v4. An SDK comprised of 2 packages:
    • core, a thin wrapper on viem that provides utilities for working with Juicebox in any Javascript environment (server or client-side, any framework)
    • react, a set of React hooks and components that make building a Juicebox dapp in React easier.

Can we do without these tools? Without these tools, the following outcomes are likely:

  • if there's no way to check if a dapp is presenting accurate information, developers will be using Etherscan, which is very tedious when working with Juicebox contracts.
  • without an SDK, developers must learn the Juicebox contracts deeply. Aside from the extra time required, there's a risk of incorrect implementation, leading to bugs down the road.

It is possible to proceed without these tools. But we aren't setting ourselves up to win.

Specification

Allocate US$20k to this project, across the following payout schedule.

- US$10,000 to codalabs.eth (aeolian) up-front - US$5,500 to codalabs.eth (aeolian) upon release of SDK - US$5,000 to codalabs.eth (aeolian) upon release of juicescan.io

SDK release criteria Must be feature-parity with juice-sdk-v3 and support all features reasonably required for a general juicebox Dapp.

juicescan.io release criteria - must show all the juicebox project info, accurately - must support all networks that the juicebox v4 contracts are deployed on - no juicebox extensions required initially (buy-back-delegate, NFTs, etc)

It will be the discretion of the JuiceboxDAO multisig to determine if these criteria are met.

Rationale

Milestone-based payout is to incentivize successful delivery of the project.

NOTE: these are estimates. A base rate of $2,500 per week for initial development, and $500 per week for minor fixes and improvements yields the following:

  • Juice-sdk => 2500 * 3 + 500 * 8 = 11,500
  • Juicescan => 2500 * 2 + 500 * 8 = 9000

Total = $20,500

Risks

- Without ongoing funding, tooling may not have long-term support (both tools will be free and open-source, however) - Tooling may not provide developers with all the resources they need initially.

Timeline

Immediately.

Votes

loading