Upgrade your Ethereum DApps to interoperable mDApps with Overledger


With Overledger 2.0, developers can get the best out of all DLT ecosystems by allowing single-DLT DApps to be universally interoperable. Transforming single blockchain DApps to cross-platform Multi-DLT applications (mDApps) that are no longer bound to any single blockchain. 

Before the introduction of Overledger 2.0, making a digital asset and blockchain payment was complicated and involved multiple steps. With Overledger 2.0, this multi-step process has been reduced to only two simple steps.  

For example, before the introduction of Overledger 2.0, it was much harder to make a ERC20-based token payment from an app. Developers had to:   

  • Integrate a signing method and the native signing libraries   
  • Add or pass the private key for transaction signing    
  • Know the ERC20 smart contract address and function name and parameters   
  • Understand and calculate Ethereum fees for the transaction    
  • Code to a valid Ethereum transaction in the native format to invoke the smart contract function    
  • Perform transaction signing with the signing method above   
  • Connect to the node with the node’s own API   
  • Send the signed transaction    
  • Consult a Blockchain explorer website to check the confirmation status of the transaction   

And to do another transaction on XRP Ledger or Bitcoin, all of the same steps would have to be done again (bar the smart contract parts) with different configuration and code.   

Overledger 2.0 simplifies the whole process. Now developers just need to:   

  1. Add a private key to the SDK (or signing service in 2.2)
  2. Call the endpoint https://api.overledger.io/payment with the required information: 
  • From Address: Sending Address    
  • To Address: Recipient Address    
  • Type: e.g. ETH, USDC, QNT    
  • Network: e.g. Ethereum, Ropsten     
  • Urgency: Overledger will handle fee calculations for each network based on desired urgency of the payment    
  • Optional: Callback URL – status updates will be sent direct to the application as the transaction confirms on the DLT  

This single API call works across all the supported DLTs. To do a transaction on XRP Ledger or Bitcoin, only small modifications need to be made. Developers just need to change the “Type” to BTC or XRP and the “Network” to the relevant Bitcoin or XRP Ledger TestNet or MainNet.  

Overledger 2.0 puts new and powerful tools in the hands of our developers. But we’re not stopping there. We plan to add more functionality to our framework all the time. In the future, there will be enhancements to ERC721 asset transfers, escrows, cross-DLT atomic swaps, cross-DLT asset transfers and much more.

Gilbert Verdian
CEO of Quant

Find out more and get started today by visiting:


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