Erick de Moura (Cartesi): “Blockchain development is hard, it is our responsibility to make it easier.
In an opinion piece, Erick, co-founder of Cartesi, believes that the industry needs to collaborate more to make the work of blockchain developers easier. Cartesi is a second-layer protocol based on Ethereum that is committed to simplifying blockchain development and promoting the development of modular blockchain infrastructure.
The blockchain industry is at a critical inflection point. Web3 lacks consumer applications that can achieve mass adoption, but new infrastructure projects continue to emerge. We have to face an unpleasant reality: 15 years later, our dream of a decentralized web has not yet been realized.
Earlier this month, we released a new version: Dave 3.0.0-alpha.4. Let’s take a closer look at how it works under the hood.
First, if you’re not yet familiar with what Dave is—and feel awkward asking—here’s a brief overview. ↓🧵
1/ Our fraud proof system—the “Permissionless Arbitration Tournament” (PRT)—is a mechanism that allows anyone to challenge incorrect computations on-chain without trusting any single validator.
Optimistic Rollups compute by default as if they’re correct, so there’s a challenge window—and PRT is the mechanism that resolves those challenges.
2/ New in version 3.0.0-alpha.4: PRT settlement is now split into two phases—“staged” and “accepted”—giving the network a time window to catch errors before the result is finalized.
If all sentry nodes (sentry) approve the staged result, that window is no longer needed, enabling faster finalization.
3/ Prototype nodes now have a name: Sling. It provides persistent storage and event tracking.
The original temporary tournament view of PRT has been replaced with “typed projections,” which can directly show the current actual stage without rolling back state.
In addition, this release includes: fairer distribution of tournament winner rewards, deployment files converted to plain text format, upgrades to the Cartesi Machine and Rollups contracts, adoption of an updated Foundry version, and more comprehensive test coverage.
4/ Thanks to the partners who contributed to this. For the full changelog, see: https://github.com/cartesi/dave/releases/tag/v3.0.0-alpha.4
If you have any questions or feedback, feel free to join the Discord discussion: https://discord.gg/cartesi
Last month, we released brand-new alpha versions of Rollups Contracts, Sequencer, and Machine browser bindings, and the Machine Emulator was also updated to v0.21.0. In addition, we celebrated 35 years of the software stack that underpins all of this—Linux.
Read the full update to learn about all the highlights ↓
Great to see the Cartesi community continue to grow on CoinMarketCap! We’ve just officially surpassed 90,200 followers, and we’d like to sincerely thank every partner who has joined us.
If you haven’t joined our CoinMarketCap community (CMC) yet, here’s a great platform to break out of the traditional CT information bubble, get official updates, use the $CTSI tag, and connect with other developers and supporters.
Come say hi here: https://coinmarketcap.com/community/profile/cartesiproject/
Contributors have released a new alpha version of the Cartesi Machine bindings library, making it easier to run a machine in the browser 🐧
You can try it on its dedicated Playground: no installation required—configure, create, and run machines directly, including the terminal: https://cartesi-playground.vercel.app/
As Danilo emphasized, this simulator is powerful, runs on WASM, and includes TypeScript bindings for use in the browser. In addition, this alpha version adds the following features: the machine can connect to the network, run and be controlled from a remote server, and display real-time terminal output—everything can be done within a browser tab.
Also, comprehensive browser support documentation has been published at https://cartesi.github.io/rollups-ts/machine/
Feel free to ask any questions or share feedback on Discord: https://discord.gg/cartesi
We are once again inviting you to join us in working together to drive the thriving development of the computer vision field, and to build on Linux, on-chain, and on Ethereum.
August is coming to an end, but product releases are still ongoing. Good morning!
Another week of burying our heads in hard work finally brings us the Cartesi Weekly Report—and this issue is even more celebratory 🐧 https://fxtwitter.com/cartesiproject/status/2093323347832807597
This week marks Linux’s 35th anniversary. How could we miss such an important day? We sent birthday wishes to the operating systems running on Cartesi machines, and our tweets expressed our feelings just as they should. Linus Torvalds released Linux in 1991 and called it “just a hobby,” but fortunately, the rest of the world doesn’t see it that way. Many members of the ecosystem joined in the celebrations, proud to be part of the big Linux family:
In “Throwback Thursday”: Linux has more than 35 years of battle-tested software history, yet DeFi has been repeating the wheel. We explain why we should stop re-inventing the wheel now and instead build DeFi on top of Linux. For details, see the referenced post:
This week, we’d like to give a special thanks to Alchemy. Cartesian João Garcia appreciates our team’s report on intermittent failures of the eth_estimateGas function on the OP Sepolia server. The report includes reproduction steps, A/B/C tests, and comparisons across different providers. Alchemy tracked down the issue, fixed it, and confirmed that the fix is effective.
Uttam from Alchemy praised their support as top-tier in the industry. A full discussion thread explains what excellent developer support looks like. We’re happy to recognize great practices:
This week’s theme is “set the tone from the start”: Cartesi’s infrastructure is built from the ground up, made for developers—providing more tools, more libraries, stronger programmability, and more powerful compute so developers can fully leverage these resources. If you missed it before, take a look at this short article:
If you haven’t celebrated Linux’s 35th anniversary yet, go celebrate it now! Read the full case to learn why DeFi needs Linux, and submit your questions on Discord: discord.gg/cartesi.
Next week, we’ll directly publish an ecosystem update blog—stay tuned. Have a great weekend!
GM, Cartesi is a bottom-layer architecture built specifically for developers. It starts from scratch and offers more tools and libraries, stronger programmability and expressiveness, and more powerful computing capabilities.
Now, let’s begin building and putting these features into real use.
Cartesi Weekly Report has been published. The week flew by—yet it was packed with excitement 🐧 https://fxtwitter.com/cartesiproject/status/2090786513579913225
We’ve taken a deep dive into the updates to the Cartesi Machine Emulator v0.21.0. The game documentation has been completely rewritten. The CLI can now run the full anti-fraud program independently. Improvements have also been made to the underlying state layer—resulting in faster performance and greater stability. Thanks to Eduardo Bart (https://x.com/edubart) for the release. If you’d like to learn more, please check out the tweet we shared:
But that’s not all—Cartesi Rollups Contracts 3.0.0-alpha.9 has also been released. This version fixes issues with the Cartesi Rollups PRT contract, improves contract import functionality, updates dependencies, and provides more reproducible release artifacts. Thanks to Guilherme Dantas for the hard work! GitHub release link:
This week, House of Chimera published an in-depth review of Cartesi, showcasing the features of the Cartesi Machine and discussing DeFi applications and unique prototypes. It clearly explains how the PRT reduces disputes down to a single RISC-V instruction, as well as the lifecycle of the honeypot, and more. Want to learn about our technical specifications? Feel free to share:
Also gaining a lot of traction is Bhavya’s discussion: he talks about what makes Linux great and the wonders of building on-chain with Linux. Thanks for the video, Bhavya:
Our TikTok account is getting more and more active too. Take a look at this great clip from Diego Nehab, the founder of Cartesi Machine. Follow us and help us grow the channel:
We’re continuing to move the project forward. The motto we proposed earlier this week remains unchanged: DeFi is just the starting point, not the endpoint.
That’s it for this week’s content. For the latest updates, if you have any questions, feel free to join our Discord server: discord.gg/cartesi. Have a great weekend!
Let’s take a deeper look at the Cartesi Machine Emulator v0.21.0 release. This update is packed with new features, including brand-new documentation for the “verification game,” a CLI tool for running the fraud proof flow on your own, and infrastructure improvements designed to boost the state layer’s speed and persistence. Here are the details:🧵↓ https://fxtwitter.com/cartesiproject/status/2089698617829597516
1/ The documentation has been completely rewritten and moved into the emulator’s code repository, with a new step-by-step walkthrough chapter on the “verification game.” Want to understand the underlying mechanics of Cartesi fraud proofs? Start here: https://github.com/cartesi/machine-emulator/blob/v0.21.0/doc/README.md
2/ The CLI can now compute computation hashes, track output Merkle trees, and generate proofs for a single output as well as output Merkle root proofs. This means you can perform most of the steps required to run the fraud proof flow directly from the command line.
3/ The NVRAM address range feature allows applications to map their state directly into a physical address range via the Linux UIO driver. The state remains persistent during the advance state process, without the overhead of kernel page cache synchronization—so even as application state keeps growing, write performance stays efficient.
4/ Rolling stored machines: The CLI now supports advancing using machine states stored on disk, and rolling back (revert) via cloned stored snapshots. These operations can be done locally or against remote servers. This provides a persistent state solution for applications that don’t want to keep the entire machine state resident in memory.
5/ Enhanced state advancing mechanism: Each state advance now ends with a clear and provable result—namely “accepted,” “rejected,” “halted,” or “out of cycles.” This is crucial when disputes enter the “verification game” phase, because in that stage every outcome must be provable, not merely observable.
6/ A heads-up for developers: This version includes some breaking changes, including renamed public header files, a refactored revert flag, and an upgraded JSON-RPC protocol. These changes don’t alter the emulator’s core behavior; they only mean you’ll need to update some calling code. For full details, see the changelog. 7/ This release also includes: new Lua helper tools (including a hash tree library for building fraud proof protocol prototypes), RISC-V Zcb compressed instruction support (needed for a kernel built with GCC 14), bash auto-completion for the CLI, and stronger guarantees for snapshot persistence.
8/ Full release details: https://github.com/cartesi/machine-emulator/releases/tag/v0.21.0
Developers, this update is made for you. Dive into the new verification game documentation, try the CLI proof tools, and ask questions or share feedback on Discord: https://discord.gg/cartesi
Cartesi weekly roundup is here as promised, bringing you the latest highlights 🐧 https://fxtwitter.com/cartesiproject/status/2088249805483147641?s=20
Cartesi Rollups contract v3.0.0-alpha.7 has been released. If an application is forcibly terminated (foreclosure), not-yet-finalized compliant ETH, ERC-20, ERC-721, and ERC-1155 deposits can now be refunded to the sender. In addition, for the submission process of claims, an extra machine-check mechanism has been added to identify invalid claims earlier.
The toolchain has also been further streamlined: after alpha.5 removed a dependency, this release removes another dependency as well, enabling simpler configuration and reducing the number of components you need to manage. For full details, see this feature post: → https://x.com/cartesiproject/status/2087161705415811160
Right after that, v3.0.0-alpha.8 has also been released. This version improves the process of verifying contract source code on public blockchain explorers by migrating the core verification components to the stable versions and changing the storage format of deployment information, making it easier for tools to read automatically. It also provides a clear migration path to ensure the system keeps running smoothly during the transition.
Devnet has also introduced a more realistic test token, making it easier for users to test the withdrawal flow using the actual production logic. Click here for the full release details: → https://github.com/cartesi/rollups-contracts/releases/tag/v3.0.0-alpha.8
But that’s not all: Cartesi Machine Emulator (virtual machine emulator) v0.21.0 has also been released. The documentation has been restored and expanded, adding detailed explanations of how the emulator executes fraud proofs. Now applications can persist state more efficiently; the CLI (command-line interface) can independently handle more stages of fraud-proof workflows; and each state transition will produce a clear, verifiable result. → https://github.com/cartesi/machine-emulator/blob/main/doc/README.md
This release includes many other updates as well—more in-depth explanations will be covered in upcoming articles. Stay tuned to this channel; if you’re a tech enthusiast, you can also check the updates directly on GitHub: → https://github.com/cartesi/machine-emulator/releases/tag/v0.21.0
Let’s recap the Dar Blockchain X Space livestream: listen to Shaheen Ahmed’s excellent talk to learn how Cartesi uses Ethereum as a trust anchor for off-chain execution, and why “provable Linux” is its real differentiating advantage: → https://x.com/cartesiproject/status/2087886429913551165
This week, we especially recommend our Reddit channel. Visit r/cartesi to get the latest updates, deep technical breakdowns, release information, and community Q&A. You can also tag u/cartesi in the relevant discussion threads, and we’ll jump in promptly. → https://x.com/cartesiproject/status/2087524807911079981
Without a doubt, all these developments confirm the idea we introduced at the beginning of this week: Ethereum provides security, fraud proofs ensure verifiability, and Cartesi makes it all possible. → https://x.com/cartesiproject/status/2086799493459230844
That’s everything for this edition. Keep building, and don’t forget to get outside, connect with nature, and enjoy a wonderful weekend.
At this very moment, somewhere on Reddit, someone is enthusiastically discussing the Rollup architecture at 2:00 a.m. The good news is: they don’t have to fight it alone.
Just tag u/cartesi, and we’ll join the discussion; or head straight to r/cartesi to explore in-depth technical breakdowns, detailed version updates, and Q&A interactions: https://www.reddit.com/r/cartesi/
Original post: https://x.com/cartesiproject/status/2087524807911079981
Last week, Cartesi Rollups Contracts version 3.0.0-alpha.7 was officially released. This version introduces a safer deposit mechanism, stricter claim validation, and a more streamlined toolchain. https://fxtwitter.com/cartesiproject/status/2087161705415811160
Let’s dive into the underlying changes in this update and why they matter.🧵↓
1/ Introduces a deposit refund feature. If an app is forcibly terminated (foreclosure), compliant deposits that have not yet been finally confirmed can now be refunded to the sender. This feature covers deposits of types ETH, ERC-20, ERC-721, and ERC-1155, reducing the risk of losing funds due to unexpected events.
2/ Tracking for the final confirmation status of deposits is made clearer, and the system also rejects ERC-20 tokens that use a “fee-on-transfer” mechanism. These improvements optimize the accounting for deposits and refunds, helping prevent situations where the app’s funds become insufficient or insolvent due to mismatched data.
3/ The claim submission process adds an additional layer of machine checks. This strengthens the security of critical steps—where correctness is crucial—and can identify and block invalid claims earlier.
4/ The toolchain has been further streamlined. Following the deprecation of Cannon in alpha.5, we have now also deprecated the cartesi/rollups npm package. The rollups-contracts now only depend on Foundry and POSIX utility tools. This means integrators need to manage fewer dependencies, and potential failure points are reduced.
5/ Build artifacts and deployment addresses are still published on GitHub Releases for easy access. Source code continues to be distributed via Soldeer: `forge soldeer install 'cartesi-rollups-contracts~3.0.0-alpha.7'`
6/ This update also includes: type-checked deployment scripts (to catch deployment errors before deploying on-chain), a streamlined release artifact set (reducing redundant content), unifying foreclosure into a single event trigger (to make on-chain tracking easier), and upgrading the Foundry version to 1.5.1. 7/ Full changelog: https://github.com/cartesi/rollups-contracts/releases/tag/v3.0.0-alpha.7
Developers, welcome to go to the Rollups channel on Discord to try this release, test all the changes, and share your feedback: https://discord.gg/cartesi