1DLT Frequently asked Questions (FAQ)
Common questions about 1DLT

The QPQ Beta Program is designed to help our clients transition their projects to 1DLT. During the Beta phase, QPQ has opened the access to 1DLT's testnet and developer environment. DLT developers can deploy, test, and adapt their applications to an environment with unbounded throughput, ultra-low costs, and sub-10 second finality.

1DLT offers developers and users alike the same experience as Ethereum, with much higher throughput, much faster finality, at a fraction of the cost. Switching from Ethereum to 1DLT is like moving your applications from an Intel 286 processor to an Intel Core i9.

1DLT is 100% compatible with Ethereum, but consensus is reached on much cheaper blockchains like Algorand and Hashgraph. Instead of forcing users to pay for transaction fees, developers buy a yearly plan (developer environment, node and pre-paid transactions package). It's like switching from a 1990s mobile phone where you pay $1 per minute to a 2020s subscription with unlimited calls and a smartphone included.

Every client is a product tester if you know what you're doing, no matter the development stage of your product. The Beta Program is there to help you deploy your project under a radically different set of assumptions about throughput and cost. It's an opportunity to get ahead, and make sure everything works in the testnet before going live.

QPQ will indeed offer its Beta participants a discounted license arrangement at the conclusion of the Beta phase. The terms of this agreement will depend on user feedback.

As of July, the product is ready for use within our Beta Program. Over the last quarter, 1DLT has gone through various levels of internal testing. We feel confident that the performance of the product is at a stage where we can offer it to a controlled commercial user base.

The published performance metrics for end users have been validated via months of testing. Although we cannot guarantee the performance of third-party providers, our aim is to provide end users with the best tools and capabilities. 1DLT is our baby, and we'll do everything to see it grow and succeed. We can't do it without you; as such, we'll do everything to meet and exceed your expectations.

1DLT is an enterprise-level framework and environment to deploy and run mission critical applications. It offers all the benefits of decentralisation and Ethereum standards, without the constraints of unpredictable transaction costs, throughput, speed, and reliability.

We believe that current L1 solutions either price out most real-world use cases, or suffer from unreliability and unpredictability. 1DLT solves these issues:
- scalability, speed and cost: by routing consensus outside of L1 Ethereum, we offer virtually unbounded throughput, with sub-10 second finality at exceptionally low, predictable costs
- reliability: deploying your project on a specific blockchain exposes you to the risk of that particular blockchain breaking down; 1DLT diversifies consensus among multiple blockchains
- compatibility: 1DLT is a standard Ethereum environment where developers and users alike enjoy a frictionless experience

Are you in search of a way to scale Ethereum? Are you looking for cheap gas to manage your transactional volume? Is Security a concern? Do you hate it when Ethereum’s network is at a crawl and your business suffers? If you answered yes to any of these questions, then 1DLT is your answer. 1DLT is an easy way to deploy Ethereum and avoid all its associated shortcomings.

1DLT is built by a team of distributed systems engineers. It is purpose designed for resilient operations and therefore not be a single point of failure. To illustrate, transactions are prepared by the user’s EVM instance. These EVMs can be dedicated instances per client or shared instances, hosted in a centralised or decentralised manner.
The EVM instance then uses a service called Consensus as a Service which helps it find fast, low cost and decentralised public DLTs that can provide consensus. CaaS is a distributed routing module that passes messages between EVM instances and Layer 1 decentralised DLTs which provide consensus.
In the future, CaaS will also be able to be operated by anyone for their own purposes or in a shared manner. In conclusion, the entirenetwork is distributed and can be fully decentralised. For more information, please refer to our Whitepaper.

We choose decentralised, fast, and well recognised protocols that have research grade technical papers, strong technical teams and have adequate benchmarked data to validate their designs. Algorand and Hedera are the initial projects that meet those criteria. We continue to evaluate other candidate projects for future integration.

There are two phases to scalability. The first is increasing adoption of Blockchains in general, by delivering 1DLT as a powerful and useful product to the market. Currently there is abundant consensus and block space capacity. As adoption increases, 1DLT taps into this underutilised capacity. In parallel to this, as new fast, low cost, decentralized DLTs come to the market, 1DLT will connect to this new capacity. QPQ’s own consensus solution which can operate in millions to billions of transactions per second will be on the market in 2023. Adoption and scalability will grow in synergistic fashion.

We will implement Bridges using existing best practices. Post implementation, it will be verified through security audits. This will allow us to get insurance cover should there be any security breaches.
Our research on bridges and alternatives to bridges is ongoing. Next year we will bring to market our solution to augment and improve current best standards and practises.

See answer to previous question.

We support the latest Solidity Version 0.8.15

No. QPQ builds, deploys and maintains your network nodes. In subsequent releases, QPQ may offer its users other deployment options for its 1DLT product.

No. Network nodes are dedicated to each client of 1DLT and resources are not shared amongst clients.

QPQ hosts all network nodes in the West Europe region of the Microsoft Azure environment. In subsequent releases, QPQ may offer its users other deployment options for its 1DLT product.

Yes, end users can migrate their current applications and smart contracts to 1DLT. For the steps on how to do this, please reach out to a member of the QPQ team.

1DLT will offer a variety of payment and pricing options for our clients. To begin with, we offer a pay-as-you-go option as well as an option to pre-buy transactional volume. The price always includes a software licensing fee that covers current usage, bug fixes and on-going improvements.

The 1DLT Beta phase will work on a best-efforts basis to identify and repair any reported issues by our Beta Program Members.

Beta participants can engage QPQ 1DLT team via Slack Channel.

QPQ will be responsible for any issue raised by our Beta Program Members that is a direct result of a bug associated with the infrastructure deployed by our 1DLT product.
Copy link
On this page
Beta
What is the Beta Program?
Why should I use 1DLT?
How is 1DLT different?
Am I a product tester for you?
Can I expect favorable license conditions as a reward for being an early addopter of 1DLT?
Is the product ready for use?
What happens if you fail to achieve your promises of performance and cost outside of the testnet?
General:
Why 1DLT?
What problems does 1DLT solve?
Why do I need 1DLT?
Scaling 1DLT:
How do you avoid centralisation risk and being a single point of failure?
How do you vet and approve layer 1s into your ecosystem?
Do you have infinite scalability with demand?
How do you manage risk of cross chain transactions and bridges?
Do you assume responsibility for loss of customer assets? (For example in the event of a smart contract hack)
What versions of Ethereum Smart Contracts do you support?
Onboarding & Account Set-up:
Do I host and maintain my nodes or do you, is this optional?
Are the Nodes dedicated to me and my Network?
Do you offer multi-cloud and multi-location placement of my nodes?
Can I migrate my existing DAPP and contracts?
Billing & Payments:
What does it cost?
Client Support:
What is your SLA to monitor, repair, update and replace nodes?
How do I communicate and report issues?
If it breaks what happens, who is responsible and accountable?