Should we think of the whole thing as a Rust-first cosmos-sdk alternative? #232
-
![]() Source: https://x.com/mhluongo/status/1821635684849090772?s=46&t=eGRNsJ9UUBdKbeXgtcMh9A |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
TL;DR yes and no! Like the Cosmos-SDK, the Commonware Framework (once further along) will enable a developer to launch their own blockchain. Unlike the Cosmos-SDK, the Commonware Framework (CF) will not wrap the underlying network, consensus, and storage primitives behind a unified interface (like ABCI) nor will it define a standard block, transaction, or state/trie format. Everything released by Commonware will be built in Rust and should be easy to extend/modify with your Rust (unless I really fuck something up lol). The primitives produced by Commonware will predominantly be tailored for throughput and will make unique tradeoffs. There are some new complexities that come from this approach (which we’ll address in the coming months) but the idea in a nutshell is that developers will commonly “specialize” their stack for an application by composing primitives provided by Commonware and some of their own (especially on the execution layer) via layers of well-defined interfaces. All this being said, Commonware clearly has a long way to go and the Cosmos-SDK has attracted incredible mindshare over the last few years with their approach (me included). There are definitely a large number of talented developers who prefer their abstraction and the tradeoffs they’ve made. Looking forward to getting your feedback as we release more primitives! Source: https://x.com/_patrickogrady/status/1821722302830276991?s=46&t=eGRNsJ9UUBdKbeXgtcMh9A |
Beta Was this translation helpful? Give feedback.
TL;DR yes and no!
Like the Cosmos-SDK, the Commonware Framework (once further along) will enable a developer to launch their own blockchain.
Unlike the Cosmos-SDK, the Commonware Framework (CF) will not wrap the underlying network, consensus, and storage primitives behind a unified interface (like ABCI) nor will it define a standard block, transaction, or state/trie format. Everything released by Commonware will be built in Rust and should be easy to extend/modify with your Rust (unless I really fuck something up lol). The primitives produced by Commonware will predominantly be tailored for throughput and will make unique tradeoffs.
There are some new complexities that come from this appr…