The Web3 Frankenstein problem and DeInfra as a remedy___________________________
Is web3 on fire, in agony? What's going on?
Why are we where we are? How did we get here?
What can we do to turn this situation around?
I think many of you are wondering the same thing
Our team has thoughts on this too, which we would be happy to share with you.
A small remark, we are a team of crazy techies, so we look at all things through its specific prism, please take this into account ;)
A very-very small glossary
So that we speak the same language
dApp (decentralized application) = web3 app
Layer 1 or protocol layer = blockchain
Web3 = read / write / own
UX/DX - user experience / developer experience
w3 = web3
Web3 dualismWe see a sort of dualism in the web3 world right now.
On the one hand, there is a cohort of people who fully believe in web3. They give a lot of energy to contribute to the development of the web3. This is a very small cohort, unfortunately, but it has a lot of power, because power is in the truth. We call it the real web3 community.
Then there is a cohort of people who are not so much interested in web3 development as in their own self-interest. These people are intentionally or unintentionally pushing web3 into chaos. It's not everything on the surface, but if you analyze a few things that are going on in the market right now, it becomes obvious.
And of course there is the majority who don't really care, who are just interested in being in the trend. We each decide for ourselves which cohort of people to be in.
We see web3 is growing. Both economically and socially. We can see that the w3 community is ready to move forward and this is perfectly visible in the explosive growth of the DAOs market and philosophy.
Of course, everything is not so clear-cut, and there are moments, things for which there are questions. But that is not the subject of this article.
Here we want to unveil the technological part. Below, when we say "web3", we will first and foremost mean the technology on which the web3 world is based.
Web3 FrankensteinsSo what about the technological part? Well, the things we see, we don't like it much.
Almost 99% of all so-called dApps are not really decentralized. It has centralized parts and/or uses centralized services for decentralized stuff (!)
Well, let’s dive into this subject a bit deeper. If we’re talking not about simple smart contracts but about full-fledged web3 apps, there is much more complex architecture. I mean backend, frontend, user data, middleware and so on. And keep in mind the tech environment. You have to deploy all this stuff using different services. You have to provide access to your end-users.
So, you not only have to have a pretty specific set of skills as a developer. You have to deal with all this bunch of details, services, how to match them with each other and many other things.
We call such web3 apps Frankensteins, as they assembled from different centralized and decentralized parts, as Victor Frankensteins was assembled from old body parts.
The fact is that very few centralized services can shut down practically the entire web3 within an hour. For example, centralized hosting providers AWS, Azure, Google Cloud. Another sad fact is that user accounts are owned by web3 companies not by users or DAO, so it can be controlled and compromised by some very specific people.
Right now hundreds of developers are struggling with all these questions, de facto one-on-one.
Do you still want to be a web3 developer, fellow?
So web3 is actually web2?
Right now, web3 projects are facing a hard choice: use relatively cheap centralized web2 services with clear pricing and UX (or rather DX). Or choose a more expensive, less scalable and less clear web3 counterpart. And for many specific things in web3 there is still no alternative to web2 services.
So the question for business is to compromise, and create a product. Or wait for the web3 market to offer decent alternatives.
I think you can already guess what choice businesses are making.
And w3 apps have plenty of technological problems apart from the above - scaling, speed, transaction and storage costs, poor UX for developers and users, security issues, and a bunch of others.
It's a sad fact, but all these problems are either ignored or silenced by big players on the market. Sooner or later this approach, this compromise will result in huge problems for the whole market.
Developers know very well what a kludgy code is. It can be written quickly, but when the load increases, the system crashes.
These are all questions that very few people are trying to answer. You're unlikely to find an active discussion on reddit, or many tweets on the subject. It's an uncomfortable topic, uncomfortable questions that few people want to bring up.
You just have to acknowledge one simple fact:
Almost 100% of the web3 apps we use are not web3. Period.
So how to make web3 a real web3?
Nowadays, web3 is mainly developed in distinct technological layers (you can google layer 1, layer 2, etc. in web3). For example, blockchain developers (layer 1) compete with each other on such metrics as TPS (transactions per second), block completion time, transaction cost and so on.
While these metrics are important, they are useless as long as you use centralized services to host frontend, store user data, or to provide them access to the blockchain.
А while ago, we wondered if we could go the other way. Before that, we were actively involved in this race. We were among the first to propose an unpopular at the time solution for blockchain scaling - sharding, conducted 100,000 TPS test already in 2018 and so on. Today, as we can see, most modern blockchains implement sharding in one way or another. However, even then we saw the bottlenecks of the sharding, and designed the multi-layer blockchain platform with them in mind.
So then the web3 era came.
With much more complex architecture needed, far away from simple smart contracts. And one of the most burning concerns we've seen was how to keep all parts of such full-fledged web3 apps decentralized.
Having studied hundreds of projects, technological solutions and scientific research in this field we came to the conclusion that none of them solves the problem fundamentally. There is no infrastructure that will allow to deploy all parts of the web3 application in one space, there are only different layers that solve this problem only at their level, giving the opportunity to maintain decentralization only at their level, in their layer.
Then we came up with a complicated yet simple idea. Web3 requires a new class of infrastructure that can accommodate all parts of a web3 application. One that would eliminate the use of centralized services entirely.
That's when the idea of DeInfra was born. ‘I got the poison, I got the remedy’
Complicated yet simple idea of DeInfra
So what exactly is it? DeInfra.
DeInfra stands for “Decentralized Infrastructure” and defines as:
- The infrastructure where you can host all parts of a web3 app without exception in a single decentralized environment.
- Sophisticated infrastructure that enables to build and deploy full-fledged web3 apps with functionality that goes far beyond the capabilities of smart contracts.
This is a completely different level of decentralization, security and scalability in comparison to L1 blockchains. This is the next stage in the natural evolution of the Web3 world.
The basic principles to create DeInfra:
- there should be no centralized parts in the dApp stack;
- no centralized services should be utilized while using dApp;
- DeInfra should be governed and owned by web3 community through DAO;
- there should be the highest network liveness and security;
- the highest transaction rate should be ensured where needed;
- the lowest platform fee should be provided when needed;
- the maximum app scalability should be ensured;
- provide the best DX for developers;
- provide the best UX for the end-users;
- fosture business-friendly ecosystem for web3 projects;
- all users of DeInfra should be in a single address space;
- all users should have easy access to DeInfra;
- all user should be motivated to develop and maintain DeInfra;
- DeInfra must provide customization for different business needs;
Why it’s complicated
Well, it’s obvious. So many teams (with lot’s of $) are trying to beat challenges on different layers. DeInfra is going to beat super-challenge at all layers. it cannot be simple by definition;)
Why it’s simple
When you put all the parts in a single decentralized space, it greatly simplifies the architecture of the application. Some technological elements of the stack are no longer needed.
What if I tell you, e.g. you don't need a virtual machine? Or full node (or light, whatever) to get access to blockchain. Or download dApp to your device.
A lot of things are getting easier, cheaper, faster.
Meet the Power DCloud
Power DCloud is the world’s first DeInfra, which completely beats the problem of inability to build really decentralized dApps without centralized parts or the necessity to use centralized services.
Architecture of our platform was designed originally with such tech challenges in mind.
DCloud consists of many elements, logical layers, services and has a unique set of features.
I think to explain what DCloud is and how it works, it is worth outlining what it consists of.
Fundamental layer: blockchain platform
This layer consist of:
- Resonance BFT consensus
- Shards (chains) layer
- Validators layer
- Management layer (Power OS)
- API & SDK
MultiVM: allows to use more than one virtual machine: EVM & WASM VM in a single protocol;
DStorage allows to store frontend code, NFT data or files in a really decentralized way with no need for Web2 Clouds;
Power Nodes maintains the network with special purposes: consensus nodes, seed nodes and storage nodes;
Power Chains allows to use tailored chains with unique settings: community chain, project chain
private chain, satellite chain;
Tokens: NFT (non-fungible tokens) to manage nodes and chains, SBT (soul blade tokens), ERC-20 and our native utility token - SK (Smart Key)
Power Hub is an interface part of DCloud with user-friendly and powerful dashboards. As one-stop entry point Power Hub combines bunch of inner services: web3 store (dApps marketplace), wallet, explorer, DAO
Web3 API allows to validate data through Merkle-proof with no need for intermediate services. Developers and end-users don’t need to run a full-node or use third-party services like Infura or Alchemy thanks to a set of blockchain API and frontend libraries.
DCloud has the following set of features
You don’t need to manage web3 infrastructure. DCloud helps to save money and at the same time become completely protected from inaccess and any data loss.
Deploy your web3 app in a few simple steps. dApps development never was as easy, just try! No need for special skills.
Grow sustainable and scalable web3 business
New opportunities for monetization for the business.
Predictable and transparent tokenomics with fixed transaction price. Gives you predictability of your business and allows you to make tokenomics customized.
Best UX for end-users
One-stop entry for all dApps from mobile and desktop devices
Familiar UX for your customers gives all the blockchain benefits in a user-friendly way.
Best DX for developers
Simple and powerful web3 framework. You can build your first dApp with your skills with vendor-based support.
Highest security and availability of your dApp
No single point of failure of your full-fledged web3 app. Your dApp is available 24/7/365 with 100% SLA.
No centralized part in your full-stack web3 app. Ever
So no one can stop your dApp except the logic in the code.
Unlimited scalability and bandwidth
Build web3 startup regardless of tech bottlenecks
The DAOWe see that the w3 community is ready for products that will turn the world upside down. We see that entrepreneurs, startup founders are ready to create awesome w3 products in response to this demand. The problem is that the tech infra is not keeping up with the demand of society and business.
As we know w3 is not just about technology. Web3 products should not only be consumed, but also governed by the community. So one of the crucial stages of Power DCloud's development is the creation of DAO that will govern it, own and be in charge of future development. We see ourselves as part of this community, maybe for a while the core team.
We want to "infect" as much of the web3 community as possible with the idea of DeInfra. We want to motivate them to become active contributors. To form a variety of communities for different tasks, just like within our network could be created countless chains for special purposes (GameDev, DeFi, Metaverse etc).
We see one of the ultimate outcomes of this process as the shaping of specialized DAOs within the ecosystem. We see one of our key objectives as forming transparent and scalable tools to manage these DAOs.
ResumeWe are on an exciting and challenging journey of mistakes and insights ahead of us. We believe in the power of community, in collective intellect. We encourage developers and other w3 enthusiasts to collaborate.
Our code is always open at GitHub, as well as the documentation in case you want for instance to launch the local node or testnet already today