Thanks for your reply. I’m going to address each point below:
-
This isn’t true. The difference between a Validum compared with Roll-up is very small, and is only concerned with the way that data-availability is handled. In the future Deversifi will give users a choice over whether to have their data on-chain or off-chain. See this post for more: Volition and the Emerging Data Availability spectrum | by StarkWare | StarkWare | Medium
It is not possible for a Validium to be ‘easily hijacked by hackers’, and there is already significant TVL held on DeversiFi. The DeversiFi team has no ability to control user assets, and in the case where there was an issue with the proposed state, or if DeversiFi tried to act maliciously (e.g. if the exchange was taken offline), users can trigger a freeze on the exchange and withdraw their funds on-chain via an emergency escape mechanism, based on their balances at the last state transition. -
It isn’t entirely clear to us what your point is here. DeversiFi can interact with other Layer 2 solutions using L2-L2 bridges and it can also be composable with L1 using L2-L1 bridges (something that is close to mainnet release now). All L2 solutions, whether EVM compatible or not, will not be directly composable with L1 smart-contracts. DeversiFi is written using Cairo, a STARK optimised language, and in the near future there will be transpilers from Solidity into Cairo.