# Cartesi PRT Honeypot Markdown version of https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot ## Summary **Warning:** This project is archived and no longer maintained. **Warning:** The chain deployment is permanently frozen after the team managed to find a bug in the PRT contracts.[Read more](https://x.com/cartesiproject/status/1970902442259685855) - Total Value Secured: $526.76 (-7.37% compared to seven days ago; canonically bridged $526.76, natively minted $0.00, externally bridged $0.00; 0.00% with additional trust assumptions compared to the tokens involved and the Stage assigned to the project's canonical messaging bridge) - **Warning:** The CTSI token associated with Cartesi PRT Honeypot accounts for 100% of the TVS! (sentiment: bad) - TVS by asset: Other $526.76 (100%) - Associated tokens: CTSI: $526.76 (100% of TVS) - Past day UOPS: No data - Stage: Stage 2 (Appchain: The Cartesi PRT Honeypot is a minimal appchain (running a Cartesi Machine / dApp) for the purpose of incentivizing the testing of the Cartesi PRT proof system. Inputs/actions in the appchain are limited to deposits of CTSI by anyone and withdrawals by a single user.) - Type: Optimistic Rollup - Purpose: Bug bounty - Host chain: Ethereum ### Risks - Sequencer failure: Self sequence (sentiment: good) - State validation: Fraud proofs (INT) (7d 1h challenge period; sentiment: good) - Data availability: Onchain (sentiment: good) - Exit window: Not applicable (sentiment: neutral) - **Warning:** Bug bounty Appchain: The single hardcoded address can withdraw all funds. (sentiment: bad) - Proposer failure: Self propose (sentiment: good) ### About Cartesi PRT Honeypot is an application-specific Stage-2 rollup that stress-tests Cartesi Rollups’ security. Protected solely by Cartesi’s PRT (Permissionless Refereed Tournaments) fraud-proof algorithm, it turns its locked funds into an open bounty for anyone who can break the system. Users should not deposit unless they are willing to donate their funds to the Honeypot. ### Links - Website: https://cartesi.io/ - Docs: https://docs.cartesi.io/cartesi-rollups/, https://github.com/cartesi/honeypot/wiki/ - Explorer: https://cartesiscan.io/, https://explorer.cartesi.io/ - Repository: https://github.com/cartesi/honeypot, https://github.com/cartesi/dave - Social: https://twitter.com/cartesiproject, https://discord.gg/G2tCH5KkcM, https://cartesi.io/blog/, https://reddit.com/r/cartesi/, https://youtube.com/@cartesiproject, https://t.me/cartesiproject, https://linkedin.com/company/cartesiproject, https://instagram.com/cartesiproject/, https://medium.com/cartesi - Contracts explorer (Disco): https://disco.ethbeat.org/ui/p/cartesi-prt-honeypot ### Badges - Application-specific chain: This project is built to operate a specific application - CartesiVM: This project uses the Cartesi Machine to run its smart contracts and supports any programming language that can be ported to RISC-V architecture - Ethereum with calldata: This project is posting its data to Ethereum as calldata - Built on the Cartesi stack: The project is built on the Cartesi stack ## Value Secured The interactive TVS charts are shown on [the HTML page](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot#tvs). Token by token: [TVS breakdown](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot/tvs-breakdown). - [TVS chart (JSON)](https://ethbeat.org/api/scaling/tvs/cartesi-prt-honeypot?range=max) - [TVS breakdown by token (JSON)](https://ethbeat.org/api/scaling/tvs/cartesi-prt-honeypot/breakdown) ## Onchain costs The section shows the operating costs that L2s pay to Ethereum. The interactive costs chart is shown on [the HTML page](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot#onchain-costs). ### Tracked transactions #### Batch submissions - functionCall: 2025-06-09 23:07 UTC - now; currently used; address: [0xc70074BDD26d8cF983Ca6A5b89b8db52D5850051](https://etherscan.io/address/0xc70074BDD26d8cF983Ca6A5b89b8db52D5850051); selector: 0x1789cd63; signature: `function addInput(address appContract, bytes payload) returns (bytes32)` #### State updates - functionCall: 2025-06-09 23:07 UTC - now; currently used; address: [0x6CE590b9F0697327f18c601DF6f0baE4a0801B68](https://etherscan.io/address/0x6CE590b9F0697327f18c601DF6f0baE4a0801B68); selector: 0x8bca2e0c; signature: `function settle(uint256 epochNumber, bytes32 outputsMerkleRoot, bytes32[] calldata proof)` ## Liveness This section shows how "live" the project's operators are by displaying how frequently they submit transactions of the selected type. It also highlights anomalies - significant deviations from their typical schedule. The interactive liveness chart is shown on [the HTML page](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot#liveness). ### Tracked transactions #### Batch submissions - functionCall: 2025-06-09 23:07 UTC - now; currently used; address: [0xc70074BDD26d8cF983Ca6A5b89b8db52D5850051](https://etherscan.io/address/0xc70074BDD26d8cF983Ca6A5b89b8db52D5850051); selector: 0x1789cd63; signature: `function addInput(address appContract, bytes payload) returns (bytes32)` #### State updates - functionCall: 2025-06-09 23:07 UTC - now; currently used; address: [0x6CE590b9F0697327f18c601DF6f0baE4a0801B68](https://etherscan.io/address/0x6CE590b9F0697327f18c601DF6f0baE4a0801B68); selector: 0x8bca2e0c; signature: `function settle(uint256 epochNumber, bytes32 outputsMerkleRoot, bytes32[] calldata proof)` ## Milestones & Incidents - 2025-10-21 (incident): [Cartesi PRT Honeypot postmortem](https://cartesi.io/blog/prt_honeypot_postmortem/). Postmortem of the fail-stop incident. - 2025-09-24 (incident): [Cartesi PRT Honeypot reached a fail-stop state](https://x.com/cartesiproject/status/1970902442259685855). The chain is permanently frozen after the team managed to find a bug in the PRT contracts. - 2025-06-09: [Cartesi PRT Honeypot deployed on Ethereum](https://etherscan.io/address/0x4c1e74ef88a75c24e49eddd9f70d82a94d19251c). Cartesi PRT Honeypot deployed to Ethereum mainnet. - 2025-05-09: [Dave: decentralized, secure, lively fraud-proofs](https://dl.acm.org/doi/10.1145/3734698). Dave paper published on ACM DLT, a peer-reviewed journal. - 2024-11-13: [The Dave Algorithm](https://youtu.be/dI_3neyXVl0). Devcon 2024 presentation introducing the Dave algorithm. - 2023-09-26: [Honeypot Authority launch](https://x.com/cartesiproject/status/1706685141421047982). Honeypot Authority launched on mainnet. - 2023-04-11: [Honeypot Authority announcement](https://medium.com/cartesi/cartesi-ecosystem-update-2023-124b384401cc#:~:text=Honeypot%20DApp%20on%20Mainnet). Honeypot Authority first announced to the community. - 2022-12-23: [Permissionless Refereed Tournaments](https://arxiv.org/abs/2212.12439). PRT paper published on arxiv. ## Risk summary **Warning:** The challenge protocol can be subject to delay attacks. ### Funds can be stolen if 1. there is no one that checks the published state. Fraud proofs assume at least one honest and able validator. ## Risk analysis **Warning:** The challenge protocol can be subject to delay attacks. ### Sequencer failure Self sequence (sentiment: good) Users can self sequence transactions by sending them on L1. There is no privileged operator. ### State validation Fraud proofs (INT) (7d 1h challenge period; sentiment: good) Fraud proofs allow actors watching the chain to prove that the state is incorrect. Interactive proofs (INT) require multiple transactions over time to resolve. ### Data availability Onchain (sentiment: good) All of the data needed for proof construction is published on Ethereum L1. ### Exit window Not applicable (sentiment: neutral) **Warning:** Bug bounty Appchain: The single hardcoded address can withdraw all funds. (sentiment: bad) Users cannot exit their funds as all deposits are considered donations. ### Proposer failure Self propose (sentiment: good) Anyone can be a Proposer and propose new roots to the L1 bridge. ## Stage Cartesi PRT Honeypot is a Stage 2 Appchain Optimistic Rollup. **The project does not pass the walkaway test**: users are not able to exit in the presence of malicious operators if the Security Council disappears. ### Scope of assessment #### In scope - Ability to deposit and withdraw CTSI by the permissioned address - L1 core contracts - Derivation logic spec - Permissioned Withdrawal logic in the offchain application #### Not in scope - Published offchain Cartesi Machine source code - Cartesi Machine source code to onchain template hash mapping Rollup operators cannot compromise the system, but being **application-specific** might bring additional risk. Users can deposit (donate) CTSI tokens to the Honeypot. The funds can only be withdrawn by the Cartesi Multisig to its own address. The appchain has the very specific purpose of a bug bounty on the proof system, incentivizing security researchers to break it and claim the deposited funds. **Note:** We're still in the process of formalizing how to properly integrate appchains in the Stages framework. ### Stage 0 6 requirements met. - Met: A complete and functional proof system is deployed. - Met: There are at least 5 external actors who can submit fraud proofs. - Met: The project calls itself a rollup. - Met: State roots are posted to Ethereum L1. - Met: Inputs for the state transition function are posted to Ethereum L1. - Met: A source-available node exists that can recreate the state from Ethereum L1 data. Please note that the ETHBEAT team has not verified the validity of the node source code. [View code](https://github.com/cartesi/dave/tree/main/cartesi-rollups/node) ### Stage 1 1 requirement met. **Principle** - Met: Compromising ≥75% of the Security Council is the only way (other than bugs) for a rollup to indefinitely block an L2→L1 message (e.g. a withdrawal) or push an invalid L2→L1 message (e.g. an invalid withdrawal) with a <7d exit window. **Guidelines** ### Stage 2 1 requirement met. - Met: Fraud proof submission is open to everyone. [Learn more about Stages](https://ethbeat.org/stages). Please keep in mind that these stages do not reflect project security, this is an opinionated assessment of project maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal. ## Data availability ### All transaction data is recorded on chain All executed transactions are submitted to an on chain smart contract. The execution of the rollup is based entirely on the submitted transactions, so anyone monitoring the contract can know the correct state of the rollup chain. **References** - [InputBox.sol#18 - Etherscan source code, addInput function](https://etherscan.io/address/0xc70074bdd26d8cf983ca6a5b89b8db52d5850051#code#F1#L18) Learn more about the DA layer here: [Ethereum](https://ethbeat.org/projects/ethereum) ## State derivation ### Node software The source code for the Cartesi node software is available [here](https://github.com/cartesi/dave/tree/v1.0.0/cartesi-rollups/node). ### Genesis state The genesis state comes from the Honeypot Cartesi Machine template included in the [Honeypot v2 release](https://github.com/cartesi/honeypot/releases/tag/v2.0.0). Alternatively, you can recreate it by following the build steps in the [Honeypot GitHub Repository](https://github.com/cartesi/honeypot/tree/v2.0.0?tab=readme-ov-file#building-the-application). ### Data format The reference implementation for ERC20 deposits can be found [here](https://github.com/cartesi/rollups-contracts/blob/v2.0.0/src/common/InputEncoding.sol#L38). To learn about the withdrawal request format, please refer to the documentation [here](https://github.com/cartesi/honeypot/wiki/Requesting-withdrawals). ## State validation **Under review:** The information in the section might be incomplete or outdated. The ETHBEAT Team is working to research & validate the content before publishing. ### Fraud proofs After some period of time, the published state root is assumed to be correct. For a certain time period, usually one week, anyone can submit a fraud proof that shows that the state was incorrect. **Risks** - Funds can be stolen if there is no one that checks the published state. Fraud proofs assume at least one honest and able validator. **References** - [Permissionless Refereed Tournaments](https://arxiv.org/abs/2212.12439) - [MultiLevelTournamentFactory.sol#L37 - dispute resolution factory](https://etherscan.io/address/0xA31C2aCfF3464658866960c0fBD3d798310272D7#code#F1#L37) - [DaveConsensus.sol#L149 - application consensus](https://etherscan.io/address/0x6CE590b9F0697327f18c601DF6f0baE4a0801B68#code#F1#L149) ### Program Hashes #### Cartesi Honeypot v1 template hash The hash of the initial Cartesi machine state that is used in Dave dispute games of Cartesi Honeypot v1. - Hash: `0x615acc9fb8ae058d0e45c0d12fa10e1a6c9e645222c6fd94dfeda194ee427c14` - Repository: code unknown - Verification: not verified - Used in: [Cartesi PRT Honeypot](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot) ## Updates Each date links the update on the HTML page, which also shows its contract diffs. ### [2025-07-14 12:44 UTC](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot?update=f784b394) (14 changes) Discovery rerun on the same block number with only config-related changes. ### [2025-06-18 07:22 UTC](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot?update=727a0939) (1 change) add cartesi multisig withdrawer permission. ### [2025-06-17 15:28 UTC](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot?update=a7d24ef3) (13 changes) Initial cartesi fault proofs discovery. ## Operator ### There is no central operator There is no privileged entity that sequences transactions or produces blocks. This activity is permissionless and open to anyone. **References** - [Honeypot Docs - Running a validator node](https://github.com/cartesi/honeypot/wiki/Running-a-validator-node) ### Users can force any transaction Because the state of the system is based on transactions submitted on the underlying host chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract on the host chain directly. ## Withdrawals ### No user withdrawals No address apart from the Cartesi Multisig can trigger a withdrawal and deposits are considered donations to the Honeypot. If a withdrawal is requested by them, all funds in the escrow are withdrawable to the permissioned address as soon as the next settlement on L1 occurs (min. every 7d 1h). **References** - [Requesting withdrawals, Honeypot Wiki](https://github.com/cartesi/honeypot/wiki/Requesting-withdrawals) ## Permissions Explore these contracts and permissions in Disco, ETHBEAT's contract explorer: https://disco.ethbeat.org/ui/p/cartesi-prt-honeypot ### Ethereum #### Actors ##### Cartesi Multisig Addresses: [0x60247492F1538Ed4520e61aE41ca2A8447592Ff5](https://etherscan.io/address/0x60247492F1538Ed4520e61aE41ca2A8447592Ff5) A Multisig with 3/6 threshold. - Can interact with Application - withdraw the entire balance in the escrow Participants (6): [0xD91C0C2fC065a2e094129066D2683ef16E6F6032](https://etherscan.io/address/0xD91C0C2fC065a2e094129066D2683ef16E6F6032), [0x53cfaE10bb087bd67288eCA9e7d58E216aEbD961](https://etherscan.io/address/0x53cfaE10bb087bd67288eCA9e7d58E216aEbD961), [0xF4554F08Ed918893996DC36428Cb9DCbF2De990E](https://etherscan.io/address/0xF4554F08Ed918893996DC36428Cb9DCbF2De990E), [0xA7Dd0A6AF60ae9Accc7533d016dc7B68Db3324b1](https://etherscan.io/address/0xA7Dd0A6AF60ae9Accc7533d016dc7B68Db3324b1), [0xccD54bae0DfadA083F590f9aA16285f3eE4b5325](https://etherscan.io/address/0xccD54bae0DfadA083F590f9aA16285f3eE4b5325), [0xC826D6061b5C62237932c834B60a5eFf04D80F30](https://etherscan.io/address/0xC826D6061b5C62237932c834B60a5eFf04D80F30) Used in: [Cartesi PRT Honeypot v2](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot-v2#Cartesi%20Multisig) ## Smart contracts ![A diagram of the smart contract architecture](https://ethbeat.org/static/images/architecture/cartesi-prt-honeypot.c7147334.png) Explore these contracts and permissions in Disco, ETHBEAT's contract explorer: https://disco.ethbeat.org/ui/p/cartesi-prt-honeypot ### Ethereum #### Application (escrow) Addresses: [0x4c1E74EF88a75C24e49eddD9f70D82A94D19251c](https://etherscan.io/address/0x4c1E74EF88a75C24e49eddD9f70D82A94D19251c#code) Main dApp contract that escrows assets and executes the verified results (outputs) from off-chain computation. It relies on the DaveConsensus contract to validate outputs before releasing assets or triggering on-chain actions. The immutable template hash of the dApp is `0x615acc9fb8ae058d0e45c0d12fa10e1a6c9e645222c6fd94dfeda194ee427c14`. - Roles: - **withdrawer**: Cartesi Multisig All supported tokens in this escrow are included in the value secured calculation. #### DaveConsensus Addresses: [0x6CE590b9F0697327f18c601DF6f0baE4a0801B68](https://etherscan.io/address/0x6CE590b9F0697327f18c601DF6f0baE4a0801B68#code) Contract managing PRT fraud-proof tournaments, application epochs and input validation, as well as settlement and challenge periods. Dispute tournaments are started here and the final, verified computation result (as an `outputsMerkleRoot`) is recorded when they are resolved. #### InputBox Addresses: [0xc70074BDD26d8cF983Ca6A5b89b8db52D5850051](https://etherscan.io/address/0xc70074BDD26d8cF983Ca6A5b89b8db52D5850051#code) Serves as both the canonical log for arbitrary dApp inputs and a portal for depositing assets (one possible type of input). It ensures data availability and that all off-chain participants process the same inputs in the same order. #### TopTournament Addresses: [0x09114973AE4bf3Af3896E4e541082C73f224F8Aa](https://etherscan.io/address/0x09114973AE4bf3Af3896E4e541082C73f224F8Aa#code) Represents the entry point and highest level of a dispute in PRT. Disagreeing validators join this tournament to resolve conflicts over the entire computation trace through a bisection game. #### BottomTournament Addresses: [0x18256941eC7B661F9F46C228b74e775b581e63f8](https://etherscan.io/address/0x18256941eC7B661F9F46C228b74e775b581e63f8#code) Referees the dispute over a single contested Cartesi machine step as the final stage of arbitration in a dispute. It calls the CartesiStateTransition contract to get a definitive on-chain ruling and identify the winner. #### CartesiStateTransition Addresses: [0x772732EFbDE6559B2960327276ed33d707fF057f](https://etherscan.io/address/0x772732EFbDE6559B2960327276ed33d707fF057f#code) Onchain verifier that can execute a single, disputed instruction of the Cartesi machine. It is the ultimate arbiter that BottomTournament calls to determine which party's claimed state transition is correct. #### MultiLevelTournamentFactory Addresses: [0xA31C2aCfF3464658866960c0fBD3d798310272D7](https://etherscan.io/address/0xA31C2aCfF3464658866960c0fBD3d798310272D7#code) Responsible for creating and orchestrating the multi-stage dispute process. It instantiates the correct tournament contract (Top, Middle, or Bottom) depending on the current stage of the dispute game. #### ERC20Portal Addresses: [0xc700D6aDd016eECd59d989C028214Eaa0fCC0051](https://etherscan.io/address/0xc700D6aDd016eECd59d989C028214Eaa0fCC0051#code) Contract that allows anyone to perform transfers of ERC-20 tokens to Cartesi DApps. #### CanonicalTournamentParametersProvider Addresses: [0xcC0a49320891Bf35bca834aF1045ab89Ecd44c0c](https://etherscan.io/address/0xcC0a49320891Bf35bca834aF1045ab89Ecd44c0c#code) Provides constant configuration data for the tournament system. It defines parameters like the number of levels (3), the minimum challenge period of ~7d, and the size of computation segments at each stage of a dispute. #### MiddleTournament Addresses: [0xe49E4CB0Ab5c0E5792E762807329B420Cc4FF1AE](https://etherscan.io/address/0xe49E4CB0Ab5c0E5792E762807329B420Cc4FF1AE#code) Handles the intermediate stages of a dispute following the TopTournament targeting a more granular bisection game. ### Program Hashes #### Cartesi Honeypot v1 template hash The hash of the initial Cartesi machine state that is used in Dave dispute games of Cartesi Honeypot v1. - Hash: `0x615acc9fb8ae058d0e45c0d12fa10e1a6c9e645222c6fd94dfeda194ee427c14` - Repository: code unknown - Verification: not verified - Used in: [Cartesi PRT Honeypot](https://ethbeat.org/layer2s/projects/cartesi-prt-honeypot)