
Citrea
⚠️ Core assumption: Users trust Clementine signers and the security council to operate the protocol honestly.
Citrea's signer, operator, and verifier set are publicly available. Participants in the secuirty council are currently not.
Clementine is made of various participants. Clementine signers are 10, publicly known institutions. All of the Clementine signers also act as verifiers for the bridge. Clementine also has 2 publicly known operators who are able to run operated fronted withdrawals. Members of Citrea's security council are not publicly known. Users can learn more about the identities of the participants in the Clementine set up by visiting Citrea's documentation site. They can additionally use the Clementine CLI tool to verify the aggregate Musig2 key for Clementine's signers.
⚠️ Core assumption: Sequencer commitments are accepted into bitcoin blocks and bitcoin full nodes make Citrea state data available.
⚠️ Core assumption: Users trust the Citrea sequencer to not censor them and not go offline. If a user's transaction is censored or the sequencer goes offline, they cannot exit the network.
⚠️ Core assumption: Sequencer commitments and prover's validity proofs are accepted into bitcoin blocks and bitcoin full nodes make said data available so Citrea full nodes can advance their state.
Rollups initially pull blocks from the sequencer, but state finalization depends on data being posted to bitcoin.
Bitcoin does not enforce the finality of rollup state transitions. Rollups initially pull blocks form the sequencer and execute proposed transactions locally. However, the sequencer must commit state updates to bitcoin in order for the rollup to view its state as committed. Additionally, the network's prover must post validity proofs to bitcoin for light client finalization and for full nodes to view its state as proven.
Bridge Vault Contract
Sequencer address
Prover address
Clementine is specifically an implementation of BitVM2.
Clementine leverages BitVM2 as a way to process operated funded withdrawals in the event that one (or many) of the bridge signers is unresponsive and the 10/10 signing path is unable to sign a withdrawal transaction. Operators front capital for a user withdrawal and the request a reimbursement from the Clementine bridge program for processing an honest withdrawal. Withdrawals are bound to the rules of the Clementine bridge program, which executes a bitcoin light client to ensure that processed withdrawals align with the state of Citrea. Clementine only needs to execute a bitcoin light client because Citrea is a bitcoin rollup.