Most chains drive builders into one digital machine. Lithosphere is constructed to help a number of without delay, natively
Each sensible contract platform makes an early, principally invisible choice: which digital machine builders are required to construct on. That selection finally ends up shaping nearly every little thing downstream — which languages can be found, which developer communities really feel at residence, and which present instruments and libraries may be reused versus rebuilt from scratch. Decide the EVM and also you get Solidity’s monumental ecosystem. Decide one thing else and also you’re typically beginning over.
The same old workaround for chains that need to attain builders exterior their native VM is bridging — rise up a separate chain or setting for the opposite VM, then join the 2 with a bridge. It really works, technically, nevertheless it additionally reintroduces precisely the type of friction and fragility multi-chain techniques already wrestle with: bridges are slower, they’re a typical level of failure, and so they deal with the 2 environments as basically separate techniques that occur to speak to one another, fairly than one coherent community.
A real multi-VM Layer 1 takes a unique method: as an alternative of choosing one VM and bridging to the remaining, it helps a number of natively, on the identical community, below the identical validator set. That’s the route Lithosphere is constructing towards — a series able to natively executing contracts throughout the EVM, the Solana Digital Machine, CosmWasm, a local high-performance LithoVM, and WebAssembly, with Transfer VM help deliberate for the longer term.
The unifying items are what make this extra than simply a number of chains sitting subsequent to one another. A single validator community processes all of it, fairly than every VM having its personal separate safety assumptions. Liquidity is shared throughout VMs as an alternative of fragmented into remoted swimming pools. Contracts on completely different VMs can name one another natively, and not using a bridge in between. Accounts work below one unified mannequin, supporting each litho1… and 0x… handle codecs relying on which setting a person or contract is interacting with. And every little thing runs on one fuel token, LITHO, with the LEP100 token normal usable constantly throughout each VM fairly than needing a separate token normal per setting.
What that unlocks in apply is actual: a developer might deploy a Solidity-based DeFi protocol on the EVM aspect, construct a high-speed order guide utilizing the SVM, launch an NFT market by way of CosmWasm, and run AI brokers natively on LithoVM — with all of it interacting immediately, paying fuel in the identical token, and drawing from the identical shared liquidity, as an alternative of present as 4 disconnected functions that occur to share a model identify.
That’s the precise promise of a multi-VM Layer 1: not forcing each developer by way of the identical door, however giving them a number of doorways into the identical constructing. The more durable engineering work is ensuring it nonetheless appears like one constructing as soon as they’re inside — shared liquidity, native cross-VM calls, and one account mannequin doing the work of constructing 4 completely different execution environments really feel like a single coherent community fairly than 4 chains carrying the identical identify.
