Quant launches Overledger Release 1.5 enabling MainNet Interoperability | 29.01.2021


The new version provides MainNet access for Bitcoin, Ethereum and Ripple blockchains through Overledger. It features an updated developer portal UI and a new compliance and KYC process for MainNet access. This major milestone for Quant takes us into full live production.

We have implemented mandatory identity checks for use of Overledger production environments in order to meet regulatory compliance requirements and provide support for these checks via both desktop and mobile.

Additionally, our engineering team has migrated our Overledger Test Environment and Overledger Production Environment into AWS EKS clusters for improved resilience. The resilience for our TestNet and MainNet nodes have been improved as well. One new feature of the Developer Portal UI is an environment selector, allowing for a seamless switch between test and production environment views.

In the new version, users no longer need to have their account request approved by Quant, instead we have implemented automated approval for users once the email verification process is completed. The 1.5 version of the Developer Portal UI includes a “My Profile” page for a more personalised experience. Our technical experts have also updated the user flow, so that wallets are mandatory in preparation for the next release of Overledger Community Network.

The “Create Account” form, wallet creation user journey and key creation journey have all been updated to ensure a smoother user experience.

The requirement to have separate Developer Portal accounts in order to be both a Developer, and an RCG operator, has been removed in this new release. We have also implemented a different approach for generating mDApp IDs for developers.

Since the 1.0 release in June 2019, we have carried out major back end enhancements. Our infrastructure has been hardened to production readiness, with end-to-end automated deployment.

We have integrated with our KYC partner to provide a low friction KYC experience for MainNet access (KYC is not needed for TestNet access).

Applications developed against the June 2019 Overledger Network Community Release 1.0 release can now be moved to MainNet deployment. We have also been testing and learning from the successful 1.0 deployment in 2019 and are taking the lessons of this scaled testing into Overledger for the next release, later in spring of 2021. That release will enable community members to run remote connector gateways with their own nodes as part of the Overledger Network Family. The next upcoming release will include many enhancements for the operators of remote connector gateways.

For more details visit this page.

Download the new Guides:

Developer Portal Application

Developer Portal Remote Connector Gateways


Overledger 2.x

Overledger 1.x


OAuth 2.0 standard (allowing SSO)

Proprietary (BPI Keys)


In API, seamless updates

In SDK, re-download for updates


Full abstraction across all DLTs

Partial, DLT-specific edge cases

RCG Framework

REST / JSON APIs from OVL Core

Proprietary P2P (experimental)

Time to Deploy

32 minutes (CI / CD pipelines)

1-2 weeks

QNT Utility Token / Treasury

Optimised, audited smart contracts

Experimental smart contracts


Optimised to scale fast – 23 Microservices

Hardened proof of concept
– 9 Microservices

Transaction Routing Algorithm

6 factor, game theory optimised

Experimental P2P emergent


Cloud native (scaling / resilience)

Standalone DB deployments

Cross-DLT Implementation

REST API calls direct to OVL, integrated smart contract back end

SDK-based Javascript 
apps call smart contract functions
via OVL

2021 Achievements

50% Quant team has grown by over 50% and will continue to do so 

OVL1.0 to 2.0 Release schedule accelerated, moved to much more frequent automated updates
– Previously, last major update was seven months, then in early 2021 moved to three months (Jan and March)
and then to monthly (April and May). We’re now moving to fortnightly releases. 

2.5X Overledger is now 2.5x bigger (April)  

2.0 Re-engineered the entire 2.0 architecture

Open API 3.0 for easy integration into developer workflows

OAuth 2.0 for single sign on for enterprise customers    

Cloud Native Scalable and resilient already, now deployable automatically 

Native Transactions 

OVL 2.0 Developer portal 2.0