checkAd

    Transformation from QASH token to Liquid token (LQT) and Liquid Chain  244  0 Kommentare Liquid by Quoine's Ambition to Develop Next-Gen Financial Services - Seite 2


    The LQT asset, Quick Exchange , and World Book liquidity

    Three years ago, Liquid.com introduced the Liquid World Book and the QASH token. World Book sources and aggregates liquidity from company's own exchange and products, as well as externally. QASH was launched as a utility token to power products and services on the Liquid platform.

    Both these concepts have been expanded upon and improved. QASH will be rebranding and migrating to "Liquid Token", or LQT. Built to be a decentralized and independent asset while still serving as Liquid's native token for transaction settlement, network usage and rewards, LQT will become open-source and will run on its own native blockchain. In time, it will be decoupled from Liquid altogether, and governance and future project development will be decided by LQT holders.

    Liquid.com has launched a new B2B service called Quick Exchange, or QEX. QEX is powered by World Book liquidity, which any Liquid-vetted partner can tap into. QEX B2B aims to provide liquidity to a B2B widget to allow partners to swap between digital assets, as well as have access to fiat gateways for debit/credit card purchases.

    Liquid Chain: Introducing an institutional-grade blockchain for Finance 2.0

    Liquid Chain, or previously named "Liquid Distributed Ledger" is an all new blockchain built and designed to be efficient, secure, scalable, and most importantly, easily upgradeable as technology evolves over time.

    Liquid Chain has two special features: a unique virtual state machine (or smart contract execution unit) that can be programmed by more familiar coding language makes it perfect for not only running decentralized applications but also centralized applications; and a consensus engine that can be upgraded easily as technology evolves overtime.

    Liquid built the state machine to be high-performing, with far lower execution latency (~200 milliseconds) than other blockchain based platforms. Apps are built using the WebAssembly (WASM) language, allowing anyone with knowledge of C, C++ or Rust to build applications. It is also secure, providing a sandbox to ensure apps running on the virtual machine may only change their own states, and cannot perform any exploits on the host environment.

    These features overcome many of the problems with popular blockchain platforms today, such as Ethereum that faces scalability issues, high gas fees, disagreements and delays over protocol rules, and requirement to use a specialized programming language (Solidity) limiting its appeal to be used in applications that require scalability. Liquid Chain on the other hand has been designed to solve all of these problems.

    Liquid Chain currently uses the Tendermint BFT (Byzantine Fault Tolerance) consensus mechanism based on proof-of-stake (PoS) validators. However Liquid Chain's modular design means this can be swapped out at some future point without changing the way the platform operates.

    With Liquid, blockchain can finally deliver on its promises

    With Liquid Chain, LQT, QEX and World Book, Liquid is providing a complete platform and network for all developers and their users. It's built with sound expertise in both the financial and blockchain industries, and is designed to serve all users' needs well into the future.

    Seite 2 von 2


    Diskutieren Sie über die enthaltenen Werte


    PR Newswire (engl.)
    0 Follower
    Autor folgen

    Verfasst von PR Newswire (engl.)
    Transformation from QASH token to Liquid token (LQT) and Liquid Chain Liquid by Quoine's Ambition to Develop Next-Gen Financial Services - Seite 2 SINGAPORE, Jan. 27, 2021 /PRNewswire/ - Now, more than ever, there is a need for trustworthy technology to handle financial applications. Liquid.com is ready to launch the renewal of QASH (Liquid Token) and Liquid Chain, Liquid's advanced native …

    Schreibe Deinen Kommentar

    Disclaimer