Commonware's Vision? #237
-
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Our next primitive (commonware-consensus) is the last piece of the "MVP" we've been working on that makes the Commonware Library "integration-ready". At that point, folks can develop a custom execution layer (defining blocks/transactions/etc) or bring one that already exists (like revm). Fortunately, the interface for commonware-consensus looks a lot like a DA layer so many of the rollup execution engines should work with minimal modification (like fuel or sovereign labs). Once we reach this phase, we'll spend a lot more time talking publicly about how to employ Commonware (and apologize for the lack of info available thus far). The company's goal in all this is to help accelerate the adoption of the Commonware Library with useful (optional) products. Imagine something that looks like ~Vercel, not "pro-level" versions of what we are building publicly (anything on GitHub will be the best version of a primitive that we have). Ultimately, we believe the Commonware Library + the products offered by Commonware will empower ambitious developers to create best-in-class experiences that rival those of web2. We think there is a sustainable business (that allows us to maintain the Commonware Library) in supporting those experiences with products that most developers wouldn't want to run themselves (not their core competency) or couldn't do so cost-effectively (don't have access to low-cost infrastructure/engineering team). You, just to be clear, can avoid these products/build them yourself if you'd like to go it independently. |
Beta Was this translation helpful? Give feedback.
-
|
(naturally, all of this is subject to change but that's my focus at the moment...if you see any concern/issue, would love to hear!) |
Beta Was this translation helpful? Give feedback.
Our next primitive (commonware-consensus) is the last piece of the "MVP" we've been working on that makes the Commonware Library "integration-ready".
At that point, folks can develop a custom execution layer (defining blocks/transactions/etc) or bring one that already exists (like revm). Fortunately, the interface for commonware-consensus looks a lot like a DA layer so many of the rollup execution engines should work with minimal modification (like fuel or sovereign labs). Once we reach this phase, we'll spend a lot more time talking publicly about how to employ Commonware (and apologize for the lack of info available thus far).
The company's goal in all this is to help accelerate the ado…