Remember the earlier OpEd we did on @CoinMarketCap . Here's pt 2 coming through.
24 Oct 2023, 10:05
Remember the earlier OpEd we did on @CoinMarketCap ? Here’s pt 2 coming through!
Explore why design flexibility is a necessity for developers to build dApps that prioritize software functionality and user experience, free from infrastructure constraints.
Same news in other sources
5CartesiCTSI #305
24 Oct 2023, 15:46
The exploration of Cartesi Rollups continues 🚀
Part 2 of our deep dive into “Grokking Cartesi Rollups” is live! This time, we’re exploring the vast potential and design space enabled by app-specific rollups. 👇
🔄 ICYMI, in the first part of our rollup series, we discussed the evolution of rollup technology and its contributions to scaling web3 applications.
We introduced how Cartesi’s app-specific rollups in particular help alleviate congestion and give dApps access to much more computational power.
In part 2, we ask the question: what else can Cartesi dApps do with more computing power? 🤔 In particular, we break down the missing piece of web3 scalability alongside computing power: design flexibility.
🔴 The Problem … design flexibility
Gas wars and computing power are only one part of the scalability equation. Web3 developers today are limited in “design flexibility” - or, the ability to easily build applications with a variety of tools and resources available to them.
💡The Idea … EVM-alternatives
Many L2s have tried to tackle this developer pain point by supporting EVM alternatives, such as EVM+ and WASM. These projects allow devs to code in more traditional, familiar languages.
But … 👇
🟡 The (Second) Problem … operating systems
Being able to write in a familiar language is different from being able to benefit from decades of existing open-source libraries and tooling.
These open-source libraries give devs reusable pieces of code that give more flexibility and ease to builders.
These open-source libraries depend on powerful operating systems (OS) for key services like memory management, security, and information access.
But … EVM+ and WASM projects can’t fully support an OS infra, and L2 devs are stuck yet again with limited options.
🟢 The Solution … Cartesi Virtual Machine
The Cartesi Virtual Machine (CVM) is a custom execution environment designed to integrate with OS. Specifically, CVM emulates the RISC-V ISA (the rulebook defining computer hardware & software interactions).
RISC-V (and thus Cartesi) integrates easily with Linux, the most widely adopted and familiar open-source OS in the world.
CVM can boot an entire Linux OS, giving Cartesi dApp developers access to decades of rich code libraries and open-source tooling.
With CVM, web3 devs can evolve from developing in siloes with limited resources and no shared tooling, to developing in a vast, collaborative, and resource-rich environment. 🤝 ⭐
All this and more in the second part of our series: “Grokking Cartesi Rollups, Part 2”
Retweet:
The exploration of Cartesi Rollups continues. Part 2 of our deep dive into "Grokking Cartesi Rollups" is live.
The exploration of Cartesi Rollups continues 🚀
Part 2 of our deep dive into “Grokking Cartesi Rollups” is live! This time, we’re exploring the vast potential and design space enabled by app-specific rollups. 👇
https://cartesi.io/blog/understanding-cartesi-rollups-pt2
🔄 ICYMI, in the first part of our rollup series, we discussed the evolution of rollup technology and its contributions to scaling web3 applications.
We introduced how Cartesi’s app-specific rollups in particular help alleviate congestion and give dApps access to much more computational power.
In part 2, we ask the question: what else can Cartesi dApps do with more computing power? 🤔 In particular, we break down the missing piece of web3 scalability alongside computing power: design flexibility.
🔴 The Problem … design flexibility
Gas wars and computing power are only one part of the scalability equation. Web3 developers today are limited in “design flexibility” - or, the ability to easily build applications with a variety of tools and resources available to them.
💡The Idea … EVM-alternatives
Many L2s have tried to tackle this developer pain point by supporting EVM alternatives, such as EVM+ and WASM. These projects allow devs to code in more traditional, familiar languages.
But … 👇
🟡 The (Second) Problem … operating systems
Being able to write in a familiar language is different from being able to benefit from decades of existing open-source libraries and tooling.
These open-source libraries give devs reusable pieces of code that give more flexibility and ease to builders.
These open-source libraries depend on powerful operating systems (OS) for key services like memory management, security, and information access.
But … EVM+ and WASM projects can’t fully support an OS infra, and L2 devs are stuck yet again with limited options.
🟢 The Solution … Cartesi Virtual Machine
The Cartesi Virtual Machine (CVM) is a custom execution environment designed to integrate with OS. Specifically, CVM emulates the RISC-V ISA (the rulebook defining computer hardware & software interactions).
RISC-V (and thus Cartesi) integrates easily with Linux, the most widely adopted and familiar open-source OS in the world.
CVM can boot an entire Linux OS, giving Cartesi dApp developers access to decades of rich code libraries and open-source tooling.
With CVM, web3 devs can evolve from developing in siloes with limited resources and no shared tooling, to developing in a vast, collaborative, and resource-rich environment. 🤝 ⭐
All this and more in the second part of our series: “Grokking Cartesi Rollups, Part 2” https://cartesi.io/blog/understanding-cartesi-rollups-pt2
Retweet: https://x.com/cartesiproject/status/1716820063892967932
CartesiCTSI #305
24 Oct 2023, 14:12
🔎 The exploration of Cartesi Rollups continues 🚀
Part 2 of our deep dive into “Understanding Cartesi Rollups” is live! This time, we’re exploring the vast potential and design space enabled by app-specific rollups. 👇
🔄 ICYMI, in the first part of…
The exploration of Cartesi Rollups continues. Part 2 of our deep dive into "Understanding Cartesi Rollups" is live.
🔎 The exploration of Cartesi Rollups continues 🚀
Part 2 of our deep dive into “Understanding Cartesi Rollups” is live! This time, we’re exploring the vast potential and design space enabled by app-specific rollups. 👇
https://t.co/eKYQmytsAg
🔄 ICYMI, in the first part of…
CartesiCTSI #305
24 Oct 2023, 10:16
Remember the earlier OpEd we did on CoinMarketCap? Here’s pt 2 coming through!
Explore why design flexibility is a necessity for developers to build dApps that prioritize software functionality and user experience, free from infrastructure constraints.
Retweet:
Remember the earlier OpEd we did on CoinMarketCap. Here's pt 2 coming through.
Remember the earlier OpEd we did on CoinMarketCap? Here’s pt 2 coming through!
https://coinmarketcap.com/academy/article/design-flexibility-the-new-pinnacle-of-web3-development
Explore why design flexibility is a necessity for developers to build dApps that prioritize software functionality and user experience, free from infrastructure constraints.
Retweet: https://x.com/cartesiproject/status/1716757819884499270
CartesiCTSI #305
24 Oct 2023, 10:15
Awesome conversation with @epicweb3 @felipeargento @ayyyeandy on alt VMs!
Listen here or via your podcast app:
Awesome conversation with @epicweb3 @felipeargento @ayyyeandy on alt VMs. Listen here or via your podcast app:.
Awesome conversation with @epicweb3 @felipeargento @ayyyeandy on alt VMs!
Listen here or via your podcast app:
https://t.co/RoaBfWjKRU
CartesiCTSI #305
24 Oct 2023, 10:05
Great piece from Cartesi contributors @felipeargento @ERC_Brandon in @CoinMarketCap on how app-specific rollups are opening up a broader design space for Web3 devs 👇 twitter.com/CoinMarketCap/…
Great piece from Cartesi contributors @felipeargento @ERC_Brandon in @CoinMarketCap on how app-specific rollups are opening up a
Great piece from Cartesi contributors @felipeargento @ERC_Brandon in @CoinMarketCap on how app-specific rollups are opening up a broader design space for Web3 devs 👇 twitter.com/CoinMarketCap/…