Xterio Chain
Badges
About
Xterio Chain is an OP stack Optimium on Ethereum. The chain focuses on gaming, high performance and low fees .
$17.20 K
11.88%
Website | xter.io |
---|---|
App | xter.ioeth-bridge.xter.io |
Docs | stack.optimism.io |
Explorer | eth.xterscan.io |
Repository | github.com/XterioTech |
Social | @XterioGamesDiscord@XterioGames |
Badges
About
Xterio Chain is an OP stack Optimium on Ethereum. The chain focuses on gaming, high performance and low fees .
...
Choose token
![](https://assets.coingecko.com/coins/images/279/large/ethereum.png?1595348880)
...
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,
- 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
State validation
In developmentCurrently the system permits invalid state roots. More details in project overview.
Data availability
ExternalProof construction and state derivation rely on data that is NOT published onchain. Xterio uses a custom data availability provider without attestations, relying though on DA challenges.
Exit window
NoneThere is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.
Sequencer failure
Self sequenceProposer 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 in development
Ultimately, OP stack chains will use interactive fraud proofs to enforce state correctness. This feature is currently in development and the 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 proofs 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.
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.
The 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:
Owner of AddressManager. Admin of OptimismPortal, SystemConfig, L2OutputOracle, L1ERC721Bridge, OptimismMintableERC20Factory, L1StandardBridge.
Central actor allowed to post new L2 state roots to L1.
Central actor allowed to delete L2 state roots proposed by a Proposer.
Central actor allowed to pause deposits and withdrawals.
Those are the participants of the RollupOwnerMultisig.
Owner of the DataAvailabilityChallenge contract. It can upgrade the contract params, potentially making the system insecure.
![A diagram of the smart contract architecture](/images/architecture/bedrock-superchain.png)
The system consists of the following smart contracts on the host chain (Ethereum):
The L2OutputOracle contract 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
The L1CrossDomainMessenger (L1xDM) contract sends messages from L1 to L2, and relays messages from L2 onto L1. In the event that a message sent from L1 to L2 is rejected for exceeding the L2 epoch gas limit, it can be resubmitted via this contract’s replay function.
Upgrade delay: No delay
Upgrade delay: No delay
The DataAvailabilityChallenge contract is used to challenge the data availability of tx data hashes. See the technology section for more details.
Upgradable contract that manages the PAUSED_SLOT, a boolean value indicating whether the Superchain is paused, and GUARDIAN_SLOT, the address of the guardian which can pause and unpause the system. The address of the guardian can only be modified by the ProxyAdmin by upgrading the SuperchainConfig contract. This contract is a fork of Optimism’s superchainConfig contract and is unrelated to the one used by the OP stack Superchain.
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).