Cartesi

New week at the Cartesi camp.

Builders in orbit. Linux onchain. Ethereum settlement. Mainstream tools. The stack is ready.

What are you shipping?

Repost: https://x.com/cartesiproject/status/2066508093656383699

Our technical milestones are making it into L2BEAT monthly recaps, the go-to source for onchain transparency across the ecosystem. Worth reading through. ↓
https://l2beat.com/publications/monthly-update-2026-05

Repost: https://x.com/cartesiproject/status/2064362640026296577

GM.

A reminder that every contribution matters, whether you’re building, researching, testing, creating content, engaging with the community, or simply asking thoughtful questions.

Open-source software is built together. So is Cartesi.

Repost: https://x.com/cartesiproject/status/2063966773993672844

Last month brought a lot to catch up on. Dive into the latest ecosystem updates for tech releases, agentic dev tooling, DeFi demos, media highlights, and community news. ↓

https://cartesi.io/blog/ecosystem-updates-may-2026/

Repost: https://x.com/cartesiproject/status/2062881629421641784

Name one thing Cartesi can do that EVM can't.

Drop your comments in the chat or in the replies to this X post. Go ↓

Repost: https://x.com/cartesiproject/status/2062504137410183587

Name one thing Cartesi can do that EVM can't.

Drop your comments in the chat or in the replies to this X post. Go ↓

Repost: https://x.com/cartesiproject/status/2062504137410183587

GM. June 1. New month, same mission: bring 30+ years of software progress onchain and power the compute layer DeFi actually needs.

Future-compatible, open, and ready. Let's ship something.

Repost: https://x.com/cartesiproject/status/2061432630344855693

Food for thought and good reading for the weekend.

Cofounder Erick de Moura on why Ethereum's real crisis isn't organizational but mythological, and what that means for every builder who has ever asked whether the hardship is worth it. Dive in ↓

https://erickdemoura.substack.com/p/the-two-gods-of-ethereum

Just in: contributors shipped an MCP server for Cartesi development. If you build on Cartesi with AI tools like Claude or Cursor AI this changes your experience.

Pair it with the skills and you have no excuses not to start vibe-coding today.

With the MCP server connected, your AI agent gets the right CLI commands, step-by-step skills for local dev, frontend, backend, asset deposits, L1 interactions and onchain deployment, plus docs, repos and articles by topic. All inline, no external fetches.
https://server.mcp.mugen.builders/mcp

Time has come to say goodbye to hallucinated CLI commands, missed version details, and gaps in Cartesi-specific knowledge.

Resources are live and growing. Building on Cartesi has never been easier.
Explore here: https://github.com/Mugen-Builders/MCP-Server

Repost: https://x.com/cartesiproject/status/2059983780191089146

Our DevAd Lead Joao Garcia will be joining a panel on the House of Chimera space this Friday, May 22, to unpack AI beyond the hype alongside other industry players.

Expect sharp takes on where AI x Web3 is going.

Activate notifications and tune in:
→ https://x.com/i/spaces/1nGeLydoVzvKX

Repost: https://x.com/cartesiproject/status/2057084687647179015

GM from the compute corner of blockchain where Linux meets Ethereum security.

Time to build.

Repost: https://x.com/cartesiproject/status/2056359924591198266

GM community! A new Cartesi Weekly recap has just landed. Dive in and let us know if you ha

Friday again, so Cartesi Weekly is up. Five things worth knowing:

Cartesi is a long-term game. A Linux-powered verifiable compute layer takes time to build, and patience and persistence are part of the work. Building continues strong. From co-founder Erick De Moura:
→ https://x.com/erickdemoura/status/2052755679396364703

The value of Cartesi for the DeFi infra space keeps showing up. Risk modeling for DeFi positions usually means moving the math off-chain. Shaheen Ahmed kept it on and vibe-coded it for everyone to follow suit. His latest demo runs a risk prediction model for lending and borrowing positions on Aave and similar protocols, built inside Cartesi with a Python + NumPy stack. Real utility for anyone managing onchain exposure.
→ https://x.com/riseandshaheen/status/2054821391795675142

The cartesi-skills file behind that demo is also open and reusable. Plug it into Cursor, Claude, or your favorite AI assistant and ship a Cartesi app from a spec. The vibe-coding floor just dropped for everyone in the penguin community. Find all the resources here:
→ https://skills.mugen.builders

Cartesi has teamed up with ChainPatrol to make the community safer. ChainPatrol is now watching for impersonators, phishing attempts, and scam links across the project and the appchain ecosystem. Builders stay focused on building. Users and community members move through the ecosystem with more ease and confidence, while ChainPatrol keeps the noise out.
→ https://x.com/ChainPatrol/status/2054245330560979226

If you don't already follow Cartesi on YouTube, you're missing out. Shorts, demos, and new tutorials drop there constantly, plus podcast appearances and media talks. Worth the subscribe.
→ https://youtube.com/@Cartesiproject

And before you go: follow our contributors Joao Garcia and Claudio Silva for more content bites about shipping in the infinite garden. Have a great weekend!

Repost: https://x.com/cartesiproject/status/2055273057129058719

GM from the infra that optimized for the developer. The missing layer between web2 and web3.

Week's open. Let's ship.

Repost: https://x.com/cartesiproject/status/2053823262422077851

Friday again, so Cartesi Weekly again 🐧

We opened the week with a Star Wars nod and a wish: "May the 4th be with you. And verifiable compute guide you." Then we followed with a deep dive into the latest tech release and it felt earned.

Cartesi Rollups Contracts v3 alpha is live, and the headline is emergency withdrawals. The core question: if a rollup goes dark, can users still exit? Now the answer is yes, by design. In case of emergency, users can now withdraw directly against the last accepted claim, validated onchain against the Cartesi Machine state. No operator, no multisig, just the chain. Live for USDC apps. Plus: a new circuit breaker, safer validator protections, and full machine-state fingerprints for verifiable claims. Read more:
→ https://x.com/cartesiproject/status/2051664240482963497

But that's not all, Rollups Contracts 3.0.0-alpha.4 followed next, continuing the emergency withdrawal work. Claims now stage before being accepted, so users get a fixed window to react. Account validity proofs are smaller, so emergency withdrawals cost less gas. Plus typed errors, per-app claim queries, and version metadata on every contract.
→ https://github.com/cartesi/rollups-contracts/releases/tag/v3.0.0-alpha.4

And on the fraud-proof side, Dave 3.0.0-alpha.1 also shipped this week. Mostly housekeeping: Rollups Contracts, Machine Solidity Step, and Machine Emulator bumped to keep everything in sync, plus error handling now matches the rest of the Cartesi factory stack.
→ https://github.com/cartesi/dave/releases/tag/v3.0.0-alpha.1

Dev Advocacy lead Joao Garcia joined Satoshi Sean's podcast to talk all things DeFi on Cartesi's Linux-powered execution environment:
→ https://www.youtube.com/watch?v=fG77I1gXS2E

Our ecosystem articles are also live on Paragraph. Subscribe and catch up on the April recap if you haven't:
→ https://paragraph.com/@cartesians

Building continues. Want to keep the conversation going or have any questions? Join our Discord:
→ https://discord.gg/cartesi

Have a good weekend!

Repost: https://x.com/cartesiproject/status/2052736717283819562

Friday again, so Cartesi Weekly again 🐧

We opened the week with a Star Wars nod and a wish: "May the 4th be with you. And verifiable compute guide you." Then we followed with a deep dive into the latest tech release and it felt earned.

Cartesi Rollups Contracts v3 alpha is live, and the headline is emergency withdrawals. The core question: if a rollup goes dark, can users still exit? Now the answer is yes, by design. In case of emergency, users can now withdraw directly against the last accepted claim, validated onchain against the Cartesi Machine state. No operator, no multisig, just the chain. Live for USDC apps. Plus: a new circuit breaker, safer validator protections, and full machine-state fingerprints for verifiable claims. Read more:
→ https://x.com/cartesiproject/status/2051664240482963497

But that's not all, Rollups Contracts 3.0.0-alpha.4 followed next, continuing the emergency withdrawal work. Claims now stage before being accepted, so users get a fixed window to react. Account validity proofs are smaller, so emergency withdrawals cost less gas. Plus typed errors, per-app claim queries, and version metadata on every contract.
→ https://github.com/cartesi/rollups-contracts/releases/tag/v3.0.0-alpha.4

And on the fraud-proof side, Dave 3.0.0-alpha.1 also shipped this week. Mostly housekeeping: Rollups Contracts, Machine Solidity Step, and Machine Emulator bumped to keep everything in sync, plus error handling now matches the rest of the Cartesi factory stack.
→ https://github.com/cartesi/dave/releases/tag/v3.0.0-alpha.1

Dev Advocacy lead Joao Garcia joined Satoshi Sean's podcast to talk all things DeFi on Cartesi's Linux-powered execution environment:
→ https://www.youtube.com/watch?v=fG77I1gXS2E

Our ecosystem articles are also live on Paragraph. Subscribe and catch up on the April recap if you haven't:
→ https://paragraph.com/@cartesians

Building continues. Want to keep the conversation going or have any questions? Join our Discord:
→ https://discord.gg/cartesi

Have a good weekend!

Repost: https://x.com/cartesiproject/status/2052736717283819562

Our ecosystem articles are also live on Paragraph!

Monthly news, releases, builder work, technical highlights, community moments, all in one feed. No scroll lottery.

Subscribe and catch up on the April ecosystem updates if you haven't yet: https://paragraph.com/@cartesians

Repost: https://x.com/cartesiproject/status/2052011057795981343

When DeFi protocols face stress events, one question resurfaces: what happens to user funds if the core infrastructure is disrupted? If your favorite rollup went dark tomorrow, could you still exit?

Cartesi Rollups Contracts v3 alpha makes this scenario survivable by design:

1/ Let’s break down the emergency withdrawals added to the fraud-proof system.

Key signal: production readiness. For DeFi builders evaluating Cartesi as their infrastructure of choice, emergency withdrawals are a must before shipping anything with real TVL.

Here’s what shipped.

2/ User balances can be made available on the dApp's accounts drive, validated against the Cartesi Machine state onchain. If the operator goes dark, users withdraw directly against the last accepted claim. No operator, no multisig, just the chain.

Now live for USDC-backed apps.

3/ New circuit breaker: a guardian can foreclose an app. After foreclosure, no new inputs or claims. Withdrawals stay open by design.

Plus: rollups can't launch with a broken validator set, and every claim publishes a full machine state fingerprint. Anyone can verify it.

4/ In a nutshell: DeFi infrastructure has to survive operator failure. Users need to be able to exit even when nothing is working as intended.

This is an alpha release under testing, but it’s one to read if you’re building DeFi on Cartesi. Check it out:
→ https://github.com/cartesi/rollups-contracts/releases/tag/v3.0.0-alpha.3

Repost: https://x.com/cartesiproject/status/2051664240482963497

GM, builder! Run any code onchain, you must. Reinvent the wheel, you must not.

May the 4th be with you. And verifiable compute guide you.

Repost: https://x.com/cartesiproject/status/2051286495491977342

It's a wrap on April, and one of the most loaded engineering months for Cartesi.

From the Machine Emulator hitting v0.20.0 to Dev Advocacy doubling down on DeFi accessibility and practical resources, every layer of the stack moved forward. Full updates:
→ https://cartesi.io/blog/ecosystem-updates-april-2026/

Repost: https://x.com/cartesiproject/status/2050199567900246507