Architecture
Last updated
Last updated
The Infinity smart contract is controlled by a multisig which currently permits a secure AWS cloud instance access to update, and action accordingly.
The multisig can alternatively, permit another user or cloud instance access to the Infinity smart contract creating a single point of both failure and control. The centralized control is not unlike many hybrid, L2 rollups, and L2 applications in their early days.
Decentralization
There is a spectrum or various levels of decentralization that should be considered:
Level 1: Centralized custody (fully trusted): Coinbase
Level 2: Collective custody (trust in the honest majority): Sidechains
Level 3: Non-custodial via fraud proofs (trust in the honest minority): Optimistic rollups
Level 4: Non-custodial, centrally operated (trustless): Argent, zkSync
Level 5: Multi-operator (trustless, weak censorship-resistance): Cosmos
Level 6: Multi-operator (trustless, strong censorship-resistance): Ethereum, Bitcoin
We are currently close to level 2.
Infinity's off-chain infrastructure is managed via Kubernetes enabling us to operate within a multi-cloud / cloud-agnostic / lift-and-shift environment. We are on the path to set up multiple clones on different cloud providers / hybrid environments, or even bare metal protecting against longer-term outages on AWS.
Trustless Computing
We are furthermore able to sequence or batch transactions with single, or multiple Trade & Risk servers-turned-validators enabling us to both create trustless (but expensive) compute, and decentralize our off-chain compute accordingly.
In an effort to reduce computational overhead (and increase scaling), we are also considering integrating zk proofs into our architecture and/or migrating to an L2 that provides off-the-shelf zk capability and is zk EVM compatible. At the moment, zkSync looks like the most robust solution with their hyperchains, potential shared sequencer amongst the hyper chains, and custom parameterization.
