Cyber
Badges
About
Cyber is a chain designed for social applications using an implementation of OP Plasma with DA challenges.
Badges
About
Cyber is a chain designed for social applications using an implementation of OP Plasma with DA challenges.
Funds can be stolen if
- an invalid state root is submitted to the system (CRITICAL),
- the sequencer is malicious and is able to economically outspend the altruistic challengers,
- there is no challenger willing to challenge unavailable data commitments,
- the source-unavailable L2 node is configured to ignore successful DA challenges,
- a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).
Funds can be frozen if
MEV can be extracted if
Sequencer failure
Self sequenceState validation
NoneCurrently the system permits invalid state roots. More details in project overview.
Data availability
ExternalProof construction and state derivation rely fully on data that is NOT published onchain. A custom data availability (DA) provider without attestations is used, but data unavailability can be challenged.
Exit window
NoneThere is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Proposer failure
Cannot withdrawOnly the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
Fraud proofs are not enabled
OP Stack projects can use the OP fault proof system, already being deployed on some. This project though is not using fault proofs yet and is relying on the honesty of the permissioned Proposer and Challengers to ensure state correctness. The smart contract system permits invalid state roots.
Funds can be stolen if an invalid state root is submitted to the system (CRITICAL).
Data required to compute fraud proof is published offchain without onchain attestations
Xterio relies on DA challenges for data availability. If a DA challenger finds that the data behind a tx data commitment is not available, they can submit a challenge which requires locking a bond within 12h. A challenge can be resolved by publishing the preimage data within an additional 12h. In such a case, a portion of the challenger bond is burned, with the exact amount estimated as the cost incurred by the resolver to publish the full data, meaning that the resolver and challenger will approximately lose the same amount of funds. The system is not secure if the malicious sequencer is able to outspend the altruistic challengers. If instead, after a challenge, the preimage data is not published, the chain reorgs to the last fully derivable state. This mechanism fully depends on the derivation rule of the L2 node and can only be verified in its source code, which in this case is not made available.
Funds can be stolen if the sequencer is malicious and is able to economically outspend the altruistic challengers.
Funds can be stolen if there is no challenger willing to challenge unavailable data commitments.
Funds can be stolen if the source-unavailable L2 node is configured to ignore successful DA challenges.
- OP Plasma specification
- Universal Plasma and DA Challenges - Ethresear.ch
- Derivation: Batch submission - OP Mainnet specs
- BatchInbox - Etherscan address
- OptimismPortal.sol - Etherscan source code, depositTransaction function
CyberDAThe system has a centralized operator
The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system.
MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.
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.
Regular exit
The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is finalized the funds become available for withdrawal on L1. The process of block finalization takes a challenge period of 7d to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.
Funds can be frozen if the centralized validator goes down. Users cannot produce blocks themselves and exiting the system requires new block production (CRITICAL).
Forced exit
If the user experiences censorship from the operator with regular exit they can submit their withdrawal requests directly on L1. The system is then obliged to service this request or halt all withdrawals, including forced withdrawals from L1 and regular withdrawals initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular exit.
EVM compatible smart contracts are supported
OP stack chains are pursuing the EVM Equivalence model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on L1 can be deployed on L2.
The system uses the following set of permissioned addresses:
Challenger is an actor allowed to challenge or delete state roots proposed by a Proposer.
Guardian is an actor allowed to pause deposits and withdrawals.
Proposer is an actor allowed to post new state roots of the current layer to the host chain.
- This is a Gnosis Safe with 3 / 4 threshold.
- Can act on behalf of ProxyAdmin.
- Can change the configuration of AddressManager (acting via ProxyAdmin) - set and change address mappings.
- Can upgrade the implementation of DataAvailabilityChallenge, SuperchainConfig, OptimismPortal, L1ERC721Bridge, OptimismMintableERC20Factory, SystemConfig, L2OutputOracle (acting via ProxyAdmin).
- Can upgrade the implementation of L1StandardBridge (acting via ProxyAdmin) - upgrading the bridge implementation can give access to all funds escrowed therein.
Those are the participants of the CyberMultisig.
Is a Guardian.
Is a Challenger.
- Can change the configuration of DataAvailabilityChallenge - can upgrade the parameters of DA challenges like the bond size or refund percentages, potentially making challenges infeasable or insecure.
- Can change the configuration of SystemConfig - it can update the preconfer address, the batch submitter (Sequencer) address and the gas configuration of the system.
Is a Sequencer.
Is a Proposer.
The system consists of the following smart contracts on the host chain (Ethereum):
The DataAvailabilityChallenge contract is used to challenge the full availability of data behind commimted transaction data hashes. See the technology section for more details.
Upgrade delay: No delay
The main entry point to deposit ERC20 tokens from host chain to this chain. This contract can store any token. This contract can store any token.
Upgrade delay: No delay
Legacy contract used to manage a mapping of string names to addresses. Modern OP stack uses a different standard proxy system instead, but this contract is still necessary for backwards compatibility with several older contracts.
This is NOT the shared SuperchainConfig contract of the OP stack Superchain but rather a local fork. It manages the PAUSED_SLOT, a boolean value indicating whether the local chain is paused, and GUARDIAN_SLOT, the address of the guardian which can pause and unpause the system.
Upgrade delay: No delay
The main entry point to deposit funds from host chain to this chain. It also allows to prove and finalize withdrawals. This contract stores the following tokens: ETH.
Upgrade delay: No delay
Sends messages from host chain to this chain, and relays messages back onto host chain. In the event that a message sent from host chain to this chain is rejected for exceeding this chain’s epoch gas limit, it can be resubmitted via this contract’s replay function.
Used to bridge ERC-721 tokens from host chain to this chain.
Upgrade delay: No delay
A helper contract that generates OptimismMintableERC20 contracts on the network it’s deployed to. OptimismMintableERC20 is a standard extension of the base ERC20 token contract designed to allow the L1StandardBridge contracts to mint and burn tokens. This makes it possible to use an OptimismMintablERC20 as this chain’s representation of a token on the host chain, or vice-versa.
Upgrade delay: No delay
- Can be used to configure AddressManager - set and change address mappings.
- Can be used to upgrade implementation of DataAvailabilityChallenge, SuperchainConfig, OptimismPortal, L1ERC721Bridge, OptimismMintableERC20Factory, SystemConfig, L2OutputOracle.
- Can be used to upgrade implementation of L1StandardBridge - upgrading the bridge implementation can give access to all funds escrowed therein.
Contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots.
Upgrade delay: No delay
Value Locked is calculated based on these smart contracts and tokens:
Main entry point for users depositing ERC20 token that do not require custom gateway.
Upgrade delay: No delay
Main entry point for users depositing ETH.
Upgrade delay: No delay
The current deployment carries some associated risks:
Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).
