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.
It’s the weekend again, which means it’s time for the Cartesi weekly roundup 🐧
We asked everyone to name the most underrated open-source library they’ve used, and the community delivered: Nexa suggested DuckDB, saying it couldn’t run on Cartesi. Challenge accepted: Joao Garcia got DuckDB 2.0 running on a Cartesi machine on the spot. Check out the demo: → https://x.com/cartesiproject/status/2120631461502218358
Who else wants to suggest a challenge? Leave a comment under this post: → https://x.com/cartesiproject/status/2120515892882874685
Rollups Node 2.0.0-alpha.14 is out, and the engineering team has been busy. When fees spike, nodes now replace pending transactions with higher-fee ones, up to a configurable cap. PRT has moved to contracts 3.0.0-alpha.6, with two-stage tournaments. Emulator 0.22.0 is live, and new warnings explain why things get stuck—from insufficient balance to nonce stalls. For testing only, not for production. Read the full recap: → https://x.com/cartesiproject/status/2120879592198291563
On the governance front, consultation is ongoing on the proposal for the Foundation to renounce its $CTSI MinterRole, with voting about to begin. 234.13 million $CTSI have been staked, and stakers will vote on Snapshot next week. Make sure you’re ready to have your say! → https://x.com/cartesiproject/status/2120155271574245607
There’s still time to share your thoughts, just like other community members: → https://governance.cartesi.io/t/new-notice-and-proposal-mine-reserve-completion-and-ctsi-minterrole-renunciation/523
Monday’s gm once again laid out our argument plainly: Yes, it’s real Linux. Yes, in a rollup. Yes, settled on Ethereum and supporting permissionless fraud proofs. → https://x.com/cartesiproject/status/2119792651029664079
That’s all for this week! As always, if you have questions, you can find our technical contributors on Discord: discord.gg/cartesi. Have a great weekend!
Rollups Node 2.0.0-alpha.14 is out. See what's new 🧵↓
1/ Transactions are more reliable. When fees spike, the node now replaces pending transactions with higher-fee ones, up to the optional limit. If another participant completes the action first, the node will try to cancel its own transaction.
2/ PRT moves to contract 3.0.0-alpha.6, with support for two-stage tournaments. Before joining, advancing stages, or accepting, the node confirms that the contract uses its machine.
JSON-RPC and CLI now show staking, match deadlines, leaf sealing, and historical rankings. Sending dispute moves is next.
3/ Emulator 0.22.0 is out. The node checks the emulator at startup and the machine identity when loading a template, so a mismatch prevents it from making an incorrect claim.
Claim checks now cover Authority and Quorum claims for empty epochs and after execution stops.
4/ If input stops being applied, previous epochs are still claimed so users can execute their outputs.
Also: validator memory no longer grows with epoch size, log queries support more providers, and keys no longer appear in help text or configuration errors.
5/ Lost an RPC response? The node resends the same signed transaction instead of sending a second one. Temporary acceptance failures no longer mark the application as FAILED; the reason is logged instead.
New warnings explain what's stuck: insufficient balance, fee cap, nonce stalled, frozen head, or nearing the join deadline.
6/ Upgrading to Rollups Node 2.0.0-alpha.14? A few changes need attention, so contact the technical contributors on Discord before getting started: https://discord.gg/cartesi
For testing only; not for production. Feedback is welcome. See the release on GitHub: https://github.com/cartesi/rollups-node/releases/tag/v2.0.0-alpha.14
What’s the most underrated open-source library you’ve used?
Because Cartesi brings a full Linux VM on-chain with Ethereum-level security, you’re not confined to a restricted smart contract environment. You can run real-world C++, Python, and Rust libraries directly.
Today, we’re challenging developers on X: leave the name of a library in the replies, and we’ll tell you whether it can run on-chain inside Cartesi.
Head to the thread and leave your answer. Tell us what you’d like to see running on Linux rollups: https://x.com/cartesiproject/status/2120515892882874685
It’s the weekend again, and the Cartesi weekly roundup is here right on time 🐧
Your AI agent has “mastered” Linux. And Linux is just as essential for building on Cartesi—with a complete Linux environment that includes the programming languages, libraries, and tools developers already know and use. Worth revisiting: → https://x.com/cartesiproject/status/2117979454312210915
On the governance front, the Cartesi Foundation has put forward a proposal to permanently renounce the “minting authority” (MinterRole) in the $CTSI token contract. The proposal is currently in the pre-vote discussion phase. If passed, no new CTSI tokens could be minted, and the total supply would be fixed at 1 billion. Any future projects needing CTSI funding would use existing tokens. Community members are welcome to join the discussion and share their views: → https://governance.cartesi.io/t/new-notice-and-proposal-mine-reserve-completion-and-ctsi-minterrole-renunciation/523
This Thursday, we took another deep dive into the Cartesi Machine through a thread by longtime contributor and current Knoss co-founder Felipe Argento. It gave us a closer look at the research and engineering behind running a complete Linux computer on-chain in a verifiable way. If you missed it, check it out here: → https://x.com/cartesiproject/status/2118341816261177762
Meanwhile, Shaheen Ahmed traveled to Mumbai for Devcon, representing Knoss—a platform for trading options and derivatives built on Cartesi Rollups. He invited market makers, DeFi builders, and traders to get in touch, and offered early access to “Knoss”: → https://x.com/riseandshaheen/status/2117314361899516379
A post published on Monday set the tone for November: developers don’t have to give up the tools they love when building on-chain. Keep the Linux stack you know and bring it straight to Ethereum. → https://x.com/cartesiproject/status/2117254678006432206
That’s all for this week’s roundup! Are you building with Cartesi, or looking for a place to get started? Join us on Discord: discord.gg/cartesi. Have a great weekend!
“Throwback Thursday”: Felipe Argento explains the Cartesi Machine in detail in a series of tweets. Felipe is a longtime Cartesi contributor and is now also a co-founder of Knoss, building on Cartesi.↓ https://x.com/felipeargento/status/1765944110270341434
As Felipe emphasizes, building this execution environment has taken years of in-depth research and engineering effort.
It remains a real software environment with Ethereum-level security—and it’s now more mature, developer-friendly, and robust.🐧
【Recap】The Cartesi Foundation has proposed permanently renouncing the “MinterRole” in the $CTSI token contract.
If approved, no new CTSI tokens could be minted, and the token supply would be fixed at 1 billion. Any future projects funded by CTSI would use the existing tokens.
You’re welcome to share your thoughts before the vote: https://governance.cartesi.io/t/new-notice-and-proposal-mine-reserve-completion-and-ctsi-minterrole-renunciation/523
October was packed with noteworthy developments: with staking rewards set to end around July 2027, the community is being consulted on the $CTSI MinterRole; new versions of Node, CLI, Sequencer, and Machine were also released, along with the Q3 Engineering Report, Foundation support for the Knoss project, and more.
All substance, no gimmicks ↓ https://blog.cartesi.io/ecosystem-updates-october-2026/
Friday is here again, and the Cartesi weekly roundup is right on time 🐧
Our PRT (fraud-proof system) development has made progress, and Dave v3.0.0-alpha.6 is now available. When an honest participant wins a sub-dispute, their timer is now automatically replenished, up to a cap. This means attackers can no longer exhaust the timer for a correct claim by flooding the system with fake identities. This release also fixes issues found in the latest PRT verification review and is compatible with Cartesi Machine v0.22. Thanks to Gabriel Coutinho de Paula for his contributions: → https://github.com/cartesi/dave/releases/tag/v3.0.0-alpha.6
On the staking front, Explorer v3.13.0 is now live. This release introduces a new wallet library and adds transaction receipts for users who access Explorer as a “Safe App” (Gnosis Safe app)—especially useful if your staked assets are held in a multisig wallet. Thanks to Bruno Menezes: → https://github.com/cartesi/explorer/releases/tag/v3.13.0
No time to read the full Q3 engineering report? This concise thread recaps 130 pull requests (PRs), 673 commits, and 58 releases across 13 repositories, organized around three technical pillars. Two highlights: the emergency withdrawal flow now has its final piece with “deposit returns”; and Cartesi Machine v0.21.0 ensures every input eventually produces a verifiable result, even if the application crashes. Check out the summary: → https://x.com/cartesiproject/status/2112530070510383323
It’s Open Access Week. Research should be freely readable, shareable, and buildable upon—and so should code. Cartesi is open source, brings Linux onchain, and settles on Ethereum, so anyone can independently verify computation. → https://x.com/cartesiproject/status/2112167301844009259
There was also some discussion on social media this week. If your tech stack can’t run Linux onchain, it might not be the right choice: → https://x.com/cartesiproject/status/2112891152445894867
And a reminder: don’t limit yourself to the L1 EVM model, where every application shares the same block’s computational resources. Make the switch to Cartesi—it offers orders of magnitude more computational power, a full Linux tech stack, and a dedicated virtual machine (VM) for every application: → https://x.com/cartesiproject/status/2113254324134678943
That’s all for this week’s roundup. Are you building with Linux onchain, or just stopping by to say hello? Come find us on Discord: discord.gg/cartesi. Have a great weekend!
Stop designing around that “dot.” It’s that simple.
Why can’t most DeFi projects deliver real innovation? That “yellow dot” represents the computational limit of an L1 EVM block. It forces developers to squeeze their logic into a single block, resulting in financial apps with limited functionality.
The “blue grid,” on the other hand, is the Cartesi VM, which offers several orders of magnitude more computing power. Once you see the gap, you can’t ignore this limitation anymore.
If your tech stack doesn’t support running Linux environments on-chain, it’s not the ideal choice. 🐧 https://x.com/NewAgeRetroNerd/status/2110402168272355555
No need to rewrite code from scratch or compromise on your choice of libraries. With Cartesi, we’ve brought a complete Linux runtime environment directly to Ethereum and the Web3 ecosystem. If it runs on Linux, it can run on-chain.
Help spread the word: https://x.com/cartesiproject/status/2112891152445894867
Want to see the condensed version of our Q3 engineering report? Across 13 repositories, with 130 merged PRs (pull requests), 673 commits, and 58 releases, what did we actually ship? And what’s the current state of the entire tech stack? https://x.com/cartesiproject/status/2111808242502254714
The answers are here. Below is a summary across our three technological pillars 🧵↓
Secure infrastructure for real funds
Deposit refunds complete the final step in the emergency withdrawal process. Once an application is foreclosed, anyone can return unfinalized ETH, ERC-20, ERC-721, and ERC-1155 deposits to their original depositors.
The Claims mechanism has also become stricter. Now, every claim must prove that its corresponding machine completed the current epoch successfully. If a machine is halted, throws an exception, or rejects its final input, that state cannot be finalized.
Dave (PRT) introduces claim staging and improves the deposit recovery process, making it harder to manipulate maliciously. Sling Node is now the first PRT validator node that can be run, and is currently in testing as it nears the end of its Alpha phase.
Making computation at scale economically viable
Cartesi Machine v0.21.0 ensures that every input produces a provable result—even if the application crashes. Rejected inputs roll the system back to its previous state, while inputs that exhaust the cycle budget leave it in a fixed state. The emulator and on-chain execution follow exactly the same rules.
Applications can now preserve state across multiple inputs using NVRAM (non-volatile random-access memory), reducing the cost of passing state between inputs.
The sequencer introduces a fee oracle that ties user fees to L1 publication costs. The oracle sets prices based on Uniswap V3’s time-weighted average price (TWAP), aiming to limit price manipulation. Next up: launching on testnet.
A developer-friendly tech stack for fast onboarding
The Rollup Node has upgraded to emulator v0.21 on its dev branch. This version adds JSON-RPC batch requests, brings all services under a single supervisor, and provides clear health signals for Kubernetes. The TypeScript library now uses auto-generated bindings, replacing around 1,800 lines of hand-written wrapper code. In addition, `cartesi/machine` supports running the Cartesi Machine in Node.js, and even directly in a browser tab.
Next, we’ll coordinate the release of Node, SDK, CLI, and Explorer tools to make these features available to developers.
For a deeper look at the bigger picture behind these core components, see our Technical Plan: https://cartesi.io/technical-plan/