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/
Reposted from: https://x.com/cartesiproject/status/2112530070510383323
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/
Reposted from: https://x.com/cartesiproject/status/2112530070510383323