译文/Translated：
很多网络认为，任何形式的分叉都是不好的，这只有在解决治理权争端的时候才不得已为之的手段。
但是EOSIO的初始版本就希望能够基于EOSIO区块链铺设各种变化方案，能够并行运行并在其中实现无缝互操作。因为EOSIO网络把姊妹链和EOS主网联系到一起，所以它能够实现横向的规模化发展。同时，EOSIO主网还拥有亚秒级的区块时间和免费交易模型，它因此让整个网络能够成为领先的去中心化应用的基础层。
我们很高兴地宣布发布LIquidX，这是DAPP（decentralized application去中心化应用）网络的一项新功能，有了这个功能，DSP（Dapp Service Provider Dapp服务商）可以在任何EOSIO区块链上提供服务。一开始我们在DAPP网络提供服务的时候，我们就希望提供必要开发者服务的DSP市场也能在其它链上实现。
EOS主网依然是DAPP网络的中心，但是我们也坚信，大规模应用的道路在多链互操作上。有了LiquidX，我们就为DSP提供了舞台，让它能在多个区块链中，包括任何运行EOSIO软件的区块链，提供诸如vRAM、LiquidAccounts、 LiquidOracles等服务。LIquidX可以比以往任何时候都提供更多的互操作性。
适用于EOSIO的LiquidX
姊妹链上的开发者现在可以使用DAPP网络服务，而不用引入任何新的代币或基础架构。LiquidX可以被用在任何EOSIO链上。
想在EOSIO上奇思妙想？你的机会来了，参加DAPP网络黑客马拉松，探索DAPP网络潜力，利用DSP服务传播你的DAPP.点击参与。
DAPP是怎么跨链工作的
为了在姊妹链上获得DSP服务，开发者质押DAPP代币获得EOS主网上选定的服务包，然后获得该服务包相应份额的QUOTA。当开发者向EOS侧链上的DSP发送服务请求时，DSP首先在主网上检查是否该开发者有足够执行该动作的QUOTA。
这个功能甚至不需要任何形式，如LiquidLink，的区块链内部通信。只要在EOS姊妹链每个账户和主网上对应账户上建立经过验证的映射，LiquidX就可以让DAPP网络扩展到其它EOSIO区块链上，同时在主网上保留服务供应层。
LiquidX和LiquidLink有什么不同？
LiquidLink是一个去信任化的双向通信协议，现在它联系EOS和以太坊，它可以实现从EOSIO区块链到很多区块链的只读联系，它是DAPP网络首次涉足相互操作的解决方法
LiquidLInk解决方案实际上是利用了两个单独的部件– Oracles 和 MultiSig，完整的相互操作模式如下：
- LiquidLInk的Oracles部件实现智能合约链—数据传输、代币转移、合约部署和运作—和阅读非智能合约区块链（如比特币和Binance）的通信
- LiquidLink的MultiSig服务可以被用来实现到非智能合约区块链的通信。
- LiquidX让DAPP网络服务—存储、oracle数据库、计算—能在其它区块链本地提供，而不需要LiquidLink介入。服务甚至可能可以跨链分享，而不需要数据传输。
用于以太坊的LiquidX
虽然LiquidX可以让EOS姊妹链上的开发者实现产品规模化、多功能化、实惠化、和可互操作化，但是其功能不单单局限在EOSIO上。比如，以太坊开发者也可以利用LiquidX获得便宜的WEB oracles数据库和其它DAPP网络服务。社区未来会把DSP服务扩展到许多其它的智能合约区块链上。
Github上的LiquidX
github.com
你最喜欢的EOSIO区块链是哪个？加入我们的Telegram讨论组一起讨论DAPP网络如和帮助扩散你链上的Dapp。
想在EOS姊妹链上搞事情？加入DAPP Network Devs Telegram小组，从我们团队和优秀的社区成员中帮你获得DAPP网络的启动帮助吧！
关注 LiquidApps
Website | Twitter | Telegram | LinkedIn | Github
原文/Original：
Many networks view forking of any kind as an adversarial, last-resort move taken only to resolve a governance dispute.
But the initial vision of EOSIO laid out a plan for multiple variants of EOSIO-based chains, running in parallel and interoperating seamlessly with one another. By meshing sister chains together with the EOS mainnet, the EOSIO network can scale horizontally. Together with its sub-second block times and free transaction model, this positions the entire network as a leading base layer for decentralized applications.
We are excited to announce LiquidX, a powerful new functionality of the DAPP Network which allows DSPs to offer services on any EOSIO chain. When we began launching services on the DAPP Network, we envisioned the DSP marketplace for essential developer services being implemented on other chains as well.
While the EOS mainnet remains the home of the DAPP Network, we strongly believe that the road to mass adoption runs through multi-chain interoperability. With LiquidX, the stage is now set for DSPs to begin offering services such as vRAM, LiquidAccounts, LiquidOracles, and more on multiple chains, including any chain that runs EOSIO software. LiquidX can enable more interoperability than ever before.
LiquidX For EOSIO
The DAPP Network’s services can now be made available to developers building on sister chains without having to introduce any additional tokens or infrastructure. LiquidX can potentially be used on any EOSIO chain.
Building something cool on EOSIO? The DAPP Network Hackathon is your chance to explore the capabilities of DAPP Network and use DSP services to scale your DAPPS. Sign up to get started.
How Does DAPP work across chains?
In order to access DSP services on a sister chain, developers stake DAPP tokens to a service package of their choice on the EOS mainnet and receive the allocated amount of QUOTA set by the package’s specifications. When the developer sends out a service request to the DSP on an EOS sidechain, the DSP first runs a check on the mainnet to determine whether the developer has a sufficient amount of QUOTA available to execute the action.
This functionality does not even require any form of interblockchain communication such as LiquidLink. By simply creating a verified mapping between each account on an EOS sister chain and the corresponding account on the mainnet, LiquidX enables the DAPP Network to expand to other EOSIO chains while keeping the service provisioning layer on the mainnet.
How does LiquidX differ from LiquidLink?
LiquidLink, a trustless two-way communication protocol that currently connects EOS and Ethereum and allows read-only connections to many blockchains from an EOSIO chain, was the DAPP Network’s first foray into interoperability solutions.
As LiquidLink solutions can actually make use of two separate components, Oracles and MultiSig, the complete interoperability picture is as follows:
- LiquidLink’s Oracles component allows communication between smart contract chains — data transfer, token transfers, and contract deployment and operation — as well as reading non-smart-contract chains such as Bitcoin and Binance.
- LiquidLink’s MultiSig service could be used to allow communication to non-smart contract chains.
- LiquidX allows DAPP Network services — storage, oracles, computation, and so on — to be offered natively on other blockchains, without needing LiquidLink. Services can even be potentially shared across chains without the need for data transfers.
LiquidX for Ethereum
While LiquidX could empower developers on EOS sister chains to make their creations more scalable, more versatile, more affordable, and more interoperable, its functionality is not limited to EOSIO. Ethereum developers, for example, could harness LiquidX to access cheap web oracles and other DAPP Network services. The community could expand DSP services to multiple other smart contract chains in the future.
LiquidX on GitHub
github.com
Have a favorite EOSIO-based blockchain? Join our Telegram group to discuss ways the DAPP Network could help scale dApps on your chain.
Building something cool on an EOS sister chain? Get the support you need in order to get started with the DAPP Network from our team and dedicated community members on the DAPP Network Devs Telegram group.
Follow LiquidApps
Website | Twitter | Telegram | LinkedIn | Github
Please click here to read an important disclaimer.
原文链接/Original URL:
