Synopsis
Fund the Sphinx open source multichain devops stack that Juicebox V4 uses, using a $SPHINX revnet that will soon be deployed alongside the Juicebox v4 stack.
Motivation
The developer operations of deploying the Juicebox v4 ecosystem across currently supported chains with the expectation of potential new chain deploys in the future, is hard. We want to make sure we maintain common addresses for common components across chains, all contracts have the correct safety/ownership implications, and that we can conveniently maintain regular testnet deploys alongside eventual production deploys. Juicebox v4 is made of up 5+ repositories, making matters more difficult.
As 0xBa5ed was researching options for how we might orchestrate the deployment process, he determined an open source project called Sphinx was the option that best solved our requisite feature needs with our requisite value set -- mainly the idea that we would not be introducing vendor lock-in or bloated sphinx-specific code into our projects. Though Sphinx was a nascent project, it was being led by two strong developers who were actively helping us get everything set up and working, while also providing timely bug fixes as inconveniences arose. They had told us that we would have to subscribe to their fee model as we approached production, awkwardly charging an ongoing fee in USD despite deploys only being a common thing pre-production.
About a month ago, the Sphinx team reached out to us letting us know they were not able to validate a big enough market and strong enough business model to justify continuing to support the Sphinx project. We asked if they could document the project well and make sure it was open source so that we can run it ourselves. They generously agreed. (I attached screenshots of the convo at the bottom).
They've since delivered, and 0xBa5ed and I have gotten Sphinx working on our local machines.
In my mind, supporting the Sphinx open source project is potentially a perfect use case for Juicebox and revnets. Here we have a powerful piece of devops software with strong developer interest that suffers from being uninvestible and unrewardable using traditional business models. This proposal aims to do this.
The primary goal is support Juicebox contract devs to make sure we can still use Sphinx to get Juicebox V4 out the door without delays due to switching devops providers. The secondary goal is also dogfooding a $SPHINX revnet to support further contributions to the open source software and community of users.
I do not have specifics of the $SPHINX revnet in mind, but i hope it will reward developers who support its usability inso far as it helps Juicebox v4 operate smoothly, including Juicebox devs and former Sphinx devs.
The open source repo can be found here: https://github.com/sphinx-labs/sphinx-platform
Specification
JuiceboxDAO should fund the $SPHINX revnet with $15k worth of ETH once it has been deployed.
Rationale
This gives us motivation to deploy the stack before receiving funds, while having some guarantees that JuiceboxDAO supports the strategy and effort.
Risks
The revnet's specifications are not known. JuiceboxDAO should assume the least favorable specification that would mean $15k donated for nothing in return.
Timeline
When the $SPHINX revnet launches.