All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
1.3.0 - 2023-03-23
- Opt-in proxy contract with pausable and ownable functionality
- Support for external key server
- 8mb IPFS file test
- Project renamed to Cartesi Compute
- Updated Rust to 1.57
- Updated arbitration-dlib
- Updated machine-solidity-step
- Updated logger
- Updated machine-manager image to support 2023 Cartesi Machine
- Use replacing memory range facility to insert IPFS drives
- Resolve some race conditions in the integration tests
- Use exact memory range log2 sizes in samples (requirement with new Cartesi Machine
- Use kubo (previously go-ipfs) as a dedicated IPFS node & use ipfs-server that speaks to this over HTTP API
- Use a private IPFS swarm for localhost tests
1.2.2 - 2021-09-29
- Fixed build issue due to changes in Rust Cargo dependencies
1.2.1 - 2021-07-24
- Removed 1K hard limit for direct input drives
1.2.0 - 2021-06-27
- Support for input drives with no assigned provider (a.k.a. "off-chain drives")
- Docker Compose template supporting known networks, which allows testing Cartesi Compute with local nodes pointing at those networks
- Challenger node now by default submits a confirmation transaction when results match, which may incur in additional fees but speeds up execution
- Fixed off-chain support for downloading Logger data from Matic Testnet
- No longer trying to download Logger data from IPFS when no IPFS configuration is specified
1.1.1 - 2021-03-28
- Fixed Docker image configuration so that off-chain dispatcher services can use supported testnet deployments
1.1.0 - 2021-03-26
- Support for Avalanche FUJI C-Chain Testnet
- Fixed handling of WaitingReveals state in CartesiCompute.getResult
1.0.0 - 2021-01-20
- First release
- Multi-party support: now any number of peers can be specified for a Cartesi Compute computation, although it is still strongly recommended to be just a few to avoid risking long periods of time for disputes (e.g., around 6-8 peers, reviously only 2 peers were allowed, claimer and challenger).
- IPFS drives: if parties cooperate, larger volumes of data can now be uploaded only to IPFS (i.e., it is no longer required that data must always be posted on-chain). The drive provider will still need to post the data to the Logger if there is disagreement on the IPFS data.
- Upgraded on-chain code to Solidity 0.7
- Packaging and deployment tooling migrated from Truffle to Hardhat