![]() There are also price caps to ensure developers pay a sensible average price with no “single massive transaction cost” to encourage economic competition. ![]() The routing algorithm ensures the best priced RCGs receive the most transactions, while fairly weighting the traffic flow. Once downloaded and installed, the operator of an RCG points the connectors to their DLT and blockchain nodes (Bitcoin, Ethereum and XRP Ledger will be supported for the initial rollout, further supported DLTs will be added with the release of production connectors), a connectivity check occurs and they can set a price for transaction processing in QNT through their RCG, in addition to the mining rewards blockchain nodes already provide operators. Connection to MainNets requires a paid license. With Overledger 2.1.x, the second generation Remote Connector Gateways will be available as a download from the Overledger Portal. We wanted to have that ready to go, in the hands of partners, customers and the community to migrate to Overledger 2.0 prior to rolling out the supply side of the network – that is, Remote Connector Gateways (RCGs). These mDapps create volume on the Overledger Network (OVN), they are essentially the demand side of the platform and the OVN ecosystem. This is the theme of the Overledger 2.0.x release train – expand the API, bring better tutorial applications and projects and make it even easier to build interoperable, stable cross-platform mDapps for enterprise and community developers. We phased our work with API releases to initially make it compelling and easy for our customers and community to migrate from Overledger 1.0/1.5, release and develop their mDapp applications on Overledger 2.0 and benefit from the new technology and innovation it brings. ![]() The second-generation remote connector gateways are in final testing and will release immediately following the Overledger 2.0.x API releases that have been released since the beginning of June. We’re very grateful to everyone who has installed and run the first-generation gateways – the data from the tests on that network allowed us to get to where we are now. Several experimental technologies were evaluated, some were retained and optimised, others we abandoned in favour of more industry-standard technology. This evolution has taken us some time but has been worth it. REST API calls direct to OVL, integrated smart contract back end Optimised to scale fast – 23 Microservices This table illustrates what’s changed: Feature This release allowed MainNet access on Bitcoin, Ethereum and XRP Ledger, and integrated compliance KYC checking for access to MainNets.ĭuring this time, Overledger 2.0 was being designed, built, and tested. Overledger 1.0 was SaaS-based, but relied heavily on client SDK-based logic and released an experimental set of technologies to the community in the form of “Overledger Gateways” for testing and feedback.īetween June 2020 and January 2021, we have been working on extending the Overledger 1.x product, but also drastically expanding the product architecture into Overledger 2.0. In January 2021, Overledger 1.5 went live. Last June we released Overledger 1.0, based on several years of work and experience with on-premise customers. Since this time last year, an incredible amount of progress has been made and we’re ready to go into detail about what’s been happening behind the scenes with Overledger.
0 Comments
Leave a Reply. |