L1X Workspace Overview
The Workspace allows you to follow a development lifecycle by establishing a strong use case and following templates and customising it as per your needs.
L1x Protocol allows you to build considering various contract lifecycle and its runtime environment.
The Runtime are logically abstracted into three different environments.
L1X VM which allows you to build native contracts that compiles to WASM and to eBPF bytecode.
L1X EVM which allows you to deploy Solidity contracts. It can be interacted with directly or by L1X VM / X-Talk contract as an intermediary which allows you to reduce cross-contract calls on EVM reducing the call stack execution time.
X-Talk including Client Chain Contract Execution that includes cross-chain contract execution and business logic establishment.
The L1x Developer Workspace are divided into four main parts based on the runtime and the complexity of the contracts. We will divide the workspace into these components to make it easier for developers to Migrate and/or build Cross-Chain applications future proofing your Web3 applications.
L1X VM runtime
This workspace helps you get started with contemporary on-chain contracts such as Fungible Token and Non-Fungible Token called L1X-FT and L1X-NFT standard contracts respectively. These contracts only leverage the L1X VM runtime natively and allow you to have dual compilation strategy which uses the proprietary compiler to compile WASM code to eBPF bytecode.
L1X EVM runtime with L1X VM Cross Contract Calls
L1X VM runtime allows you to Migrate and/or build with Solidity and leverage the Solidity language to build on L1X. There are various restrictions that EVM has and this provides problems to future proof your web3 application. We have introduced Cross Contract calls that allow you to leverage the flexibility of L1X Contracts while leveraging the solidity and EVM runtime.
X-Talk Flow Contracts Execution Lifecycle
“X-Talk Flow” allows you to define interfaces that facilitate native (L1X) and/or cross blockchain logic execution that includes interacting with events, functions and validations. X-Talk Flow contract structure and execution lifecycle has been built from ground up to facilitate native cross chain web3 application development. For detailed understanding of X-Talk visit link. Built Future Proof Cross Chain Applications by separating execution logic and runtime with X-Talk Flow contracts that are divided in three different sections which are;
X-Talk Port Contract Event Listener Node which are responsible to register event sources and off-chain data into a single flattened structure. When trying to add an event source; the contract registry contract has to be initiated without deploying an extra contract.
X-Talk Commander Execution Node which allows you to save event data, apply business logic and prepare payload.
X-Talk Customs Contract (TSS) Signing & Broadcasting Node which allows you to isolate the payload signing process.
Observed: While building a cross chain application; there were only 3 contracts that were needed on L1X including X-Talk contract compared to 12 contracts using a Bridge. The execution time was 20 seconds on X-Talk VS 4.5 Minutes with a bridge and the Tx Fees was $3 on X-Talk VS $12 on X-Talk. Link to the Video.
X-Talk and L1XVM and L1XEVM Contract execution
Already established contracts for complex projects on EVM and Solidity such as Balancer, Compound, MakerDAO, Aave and others have pre built contracts that limit the ability to use it with a cross chain application. By leveraging L1x Protocol heterogenous runtime and contract execution cycle; building a project such as cross chain lending and borrowing, balancer pool is accessible. By combining the workspace concepts such as L1X VM contemporary contracts, EVM contract deployment and cross chain with X-Talk developers and projects can build such projects.
Last updated