Pinned Tweet
New month, new website?
Starting today, cartesi.io/ has a fresh look, rebuilt around what matters right now: a cleaner layout, simpler navigation, and a direct answer to what Cartesi is and where it's headed in tech and strategy. What you'll find ↓
It’s Friday, so here comes your Cartesi Weekly 🐧
Work has progressed on our PRT fraud-proof system, and Dave v3.0.0-alpha.6 is out as a new deployment generation. An honest player’s clock now refills (up to a cap) each time they win a sub-dispute. That means attackers can’t use a flood of fake identities to run out the clock on a correct claim. The release also fixes a finding from the latest PRT verification review and works with Cartesi Machine v0.22. As always, props to @GCdePaula_ for shipping it:
→ github.com/cartesi/dave/rele…
Over on the staking side, Explorer v3.13.0 went live. It moves to a new wallet library and adds transaction receipts for anyone using Explorer as a Safe App, which helps if your stake sits in a multisig. Kudos to @brunolmenezes:
→ github.com/cartesi/explorer/…
Short on time for the full Q3 Engineering Report? The tl;dr thread walks through 130 merged PRs, 673 commits, and 58 releases across 13 repos, sorted by the three technical pillars. Two highlights: deposit refunds close the last gap in emergency withdrawals, and Cartesi Machine v0.21.0 makes every input end in a provable outcome, even when the app crashes. Summary here:
→ xitter.cf/cartesiproject/status/…
This week was Open Access Week. Research should be free to read, share, and build on, and so should code. Cartesi is open source and brings Linux onchain with Ethereum settlement, so anyone can check the results for themselves.
→ xitter.cf/cartesiproject/status/…
The timeline had opinions this week too. If your stack won’t let you build with Linux onchain, it ain’t the one:
→ xitter.cf/cartesiproject/status/…
And a reminder to stop designing around an L1 EVM’s single block of compute, shared by every app. Switch to Cartesi for orders of magnitude more compute, a full Linux stack, and a dedicated VM for each app:
→ xitter.cf/cartesiproject/status/…
That’s the week. Building something with Linux onchain, or just want to say hi? Come find us on Discord: discord.gg/cartesi. Enjoy the weekend!
Let’s stop designing around the dot. That’s it. That’s the tweet.
Want the tl;dr on our Q3 Engineering Report? What actually shipped, and where the stack stands after 130 merged PRs, 673 commits, and 58 releases across 13 repos?
Look no further. Here’s the summary, organized around the 3 technical pillars 🧵↓
Easy stack for shipping onchain in a day
The rollups node moved to emulator v0.21 on its dev branch. It gained JSON-RPC batch requests and now runs every service under one supervisor, with clear health signals for Kubernetes.
The TypeScript libraries now use generated bindings, replacing about 1,800 lines of hand-written wrappers. And cartesi/machine runs a Cartesi Machine from Node.js, or right in a browser tab.
Next up: a coordinated public release of node, SDK, CLI, and explorer release that ships all of this to builders.
For the bigger picture behind these pillars, check out our Technical Plan:
cartesi.io/technical-plan/
GM. It’s International Open Access Week. Research, papers, and knowledge should be free to read, share, and build on.
Same for code. Cartesi is open source, bringing Linux onchain with Ethereum settlement, so anyone can verify results.
The ethos holds this week and every week.
Friday today, and here’s your Cartesi Weekly once again 🐧
Cartesi CLI 2.0.0-alpha.39 is out for core developers and testers, supporting the latest Rollups Node release. Emergency withdrawals now configure straight from the machine, so there’s no separate config to keep in sync and fewer ways to get the safety net wrong. Breaking changes included, so check the release notes before upgrading. Kudos to our contributor @brunolmenezes for shipping it:
→ github.com/cartesi/cli/relea…
As the SDK matures, there’s a new way to track progress: Quarterly Engineering Reports, covering every tech workstream, achievement, and milestone. Q3 2026 by the numbers: 130 merged PRs, 673 commits, 58 releases. Months of engineering work, all in one place on our blog, curated by @riseandshaheen and the rest of the DevAdvocacy team:
→ xitter.cf/cartesiproject/status/…
First time on your feed this week: the Cartesi sequencer. It soft-confirms user ops instantly and posts them to Ethereum in batches, so interactive apps feel fast while Ethereum stays the source of truth. It can’t steal funds or forge state, fraud proofs enforce the result, and deposits skip it entirely. Still alpha, with v0.1.0-alpha.10 shipping the sequencer, machine images, and watchdog together. Shoutout to @GCdePaula_ and the other contributors behind it. Check more here:
→ xitter.cf/cartesiproject/status/…
Zooming out, the Technical Plan lays out the three pillars guiding the roadmap: safe infrastructure for real money, economical computation at scale, and an easy stack for shipping onchain in a day. Plus, if you didn’t yet check our new website, now it’s the moment to do it.
→ cartesi.io/technical-evoluti…
Monday’s gm put it plainly: if your code or library already runs on Linux, it runs onchain too. Same tools, Cartesi infra, Ethereum security.
→ xitter.cf/cartesiproject/status/…
That’s the pitch, and that’s the week! As always, keep in touch on Discord: discord.gg/cartesi, and let’s all slide into the weekend. Have a good one!
As the SDK matures, there’s a new way to track Cartesi’s progress.
Introducing the Quarterly Engineering Reports, covering every tech workstream, achievement, and milestone.
130 merged PRs. 673 commits. 58 releases. Get the full Q3 2026 breakdown ↓
blog.cartesi.io/engineering-…
For a bird’s-eye view of Cartesi’s tech priorities, explore the Technical Plan and the 3 pillars guiding our roadmap:
→ Safe infrastructure for real money
→ Economical computation at scale
→ An easy stack for shipping onchain in a day
cartesi.io/technical-evoluti…
First time on your X feed: the Cartesi sequencer! Let’s unpack what it is, why it matters, and how it works. 🧵↓
1/ Interactive apps need speed. Ethereum settlement takes time. Nobody wants to wait minutes for L1 finality on every click. That’s where a sequencer comes in.
5/ The Cartesi sequencer is still alpha, but it’s progressing fast.
It plans for L1 outages, crashes, reboots, long downtime, and hostile mempools. On every startup, it checks its database and Ethereum to identify what needs fixing.
A separate watchdog double-checks its state.
6/ The latest release, v0.1.0-alpha.10, ships the sequencer, machine images, and watchdog together.
New: public fee quotes, app history with replay, C app bindings, a rewritten watchdog, and Cartesi Machine v0.21.0. Breaking changes. Read the notes first: github.com/cartesi/sequencer…







