A Strong BP is Also A DSP
DAPP Service Providers add value to themselves, their chains, and the ecosystem as a whole. Here’s why you should become one.
- In addition to processing transactions on their chains, many high-quality Block Producers are enhancing their chains with a range of tools and services.
- Every BPs should become DSPs in order to accelerate interoperability, scalability and adoption on their chains
- By becoming a DSP, BPs can scale the impact of their contributions and help take their chain to the next level.
Decentralized public networks are creating new, exciting ways to coordinate economic activity. Consensus mechanisms allow distributed groups of individuals and companies to process a flow of transactions, while cryptoeconomics incentivizes a global pool of contributors to accelerate network growth. On many networks, the responsibility of processing transactions falls to the miners, while maintaining and enhancing the software is the job of ecosystem developers.
One of the advantages of EOSIO is that many high-quality Block Producers fulfill both these roles. In addition to validating their chain and processing transactions, BPs are expected to work hard to advance their networks in a variety of ways. They run open source tools, promote and incubate dApp development, and drive the overall direction of their chains.
Yet, despite the BPs’ sizable contributions to EOSIO, the platform still falls short of its goal of mainstream adoption. In order to make the leap and attract the masses, EOSIO stakeholders must do two things:
- Overcome its inherent resource constraints
Even though EOSIO’s unique resource model allows quicker and cheaper transactions than other chains, there are still limitations that prevent the platform from dependably servicing millions of users. Smart contract memory, decentralized storage, oracles and computational power are some of the resources that are either in short supply or not available at all. For dApps to reach mass usage, resource scarcity must be replaced with resource abundance. - Achieve interoperability through inter-blockchain communication (IBC)
While each EOSIO chain can function independently, the real scaling potential of EOSIO lies in having all EOSIO-based chains interoperating with one another and making it simple to exchange data and value across the EOSIO network. From the EOS mainnet to sister chains, private chains, and even customizable LiquidChains, connecting the EOSIO ecosystem into an integrated network can scale the network horizontally into a single, powerful blockchain layer.
The DAPP Network, the first universal middleware that is used across multiple blockchains, provides developers with a suite of powerful services that tackle some of the thorniest issues facing EOSIO adoption. Its services expand the pool of resources and functionalities available for dApp developers, while its IBC solution allows them to leverage the strengths of multiple chains when building their applications.
At the heart of the DAPP Network are the DAPP Service Providers (DSPs), unique nodes that offer a range of scaling and interoperability services on the network’s marketplace. DSPs are central to achieving the objective of enabling mass-scale dApps to emerge across multiple chains. By joining the DAPP Network as DSPs, BPs from various EOSIO chains will scale the impact of their contributions and help take their chain to the next level.
WAX is the first EOSIO chain outside the mainnet to integrate the DAPP Network and its services, setting an example for others to follow. The WAX community has even added a recommendation that all WAX Guilds (BPs) become DSPs. By becoming DSPs, WAX Guilds could earn a higher score from WAX’s Independent Office of the Inspector General — the community-driven quality control committee.
Whatever your technical capabilities and specialities, you can make significant contributions to your dApps, your chain and the entire EOSIO network by becoming a DSP.
- If this is your first time offering tools for the community, you can get started by seamlessly spinning up a DSP node and offering one of our DAPP services out of the box.
- More experienced BP teams can develop their own services, or even plug existing services into the DAPP Network and harness its robust provisioning layer and cross-blockchain compatibility to reach a wider audience of users.
EOSIO BPs are often more than just validators. Without the contribution of the BPs, much of the network infrastructure would not be as mature as it is today. Tools built by BPs include block explorers (Bloks.io developed by EOS Cafe Block and HkEOS; EOSX built by EOS Asia), full history APIs (EOS sw/eden, Greymass, EOS RIO), and incubators (HkEOS, EOS Argentina).
If You’re for Scalability, Interoperability and Adoption — You Should Become a DSP.
Becoming a DSP gives BPs an opportunity to take their contributions even further and maximize their impact across 3 key areas: Scalability, Interoperability, and Adoption.
Scalability
EOS constantly places first amongst blockchain networks when it comes to usage stats. Over the last 3 months, it has processed an average of 23 transactions per second compared to 4 TPS on Bitcoin and 7 TPS on Ethereum.¹ Not only does EOS have superior processing capabilities, but its free transaction model also makes it attractive to developers building high-usage applications. Instead of paying for transactions, token holders stake EOS in order to access RAM, CPU, and NET — 3 network resources essential to interacting with the chain. While EOS’s resource model makes it significantly cheaper for developers, the scarcity of these resources makes it difficult for them to build dApps that can service millions of users.
Many of the DAPP Network services are specifically designed to expand the pool of resources available to developers. The first service that went live on the DAPP Network was vRAM, an alternative memory solution that gives developers access to unlimited decentralized memory. Since then, the DAPP Network has tackled CPU issues by releasing vCPU, solved account creation difficulties with LiquidAccounts and overcome the challenge of supplying credible data to the blockchain with LiquidOracles.
For almost three years, we have seen tremendous experimentation come to life on EOSIO. DSPs have the power to free their chains from resource limitations, allowing them to transcend the early adopter phase and reach new pools of consumers.
Another way to scale EOS is by linking it to other chains and reducing the resource load placed on the mainnet, which brings us to the next point…
Interoperability
EOS is just one of the many chains based on EOSIO software. Other variants running in parallel to the EOS mainnet — such as WAX, Ultra, and BOS — each come with their own design, advantages, and user base. While each chain can scale on its own, connecting them together scales the network horizontally by distributing the computing load.
As the first middleware layer that can be utilized on multiple chains, the DAPP Network provides a crucial link between different variants of EOSIO. This link scales both individual chains and EOSIO as a whole.
LiquidX, which is already live, gives developers access to the DAPP Network’s suite of services no matter which EOSIO chains they wish to use. Additionally, DSPs could offer LiquidLink service packages and allow smart contract chains to communicate data and value between each other in a trustless fashion. LiquidLink is the first interblockchain communication (IBC) protocol that can bridge between EOSIO chains but can also link to Ethereum as well. Taken together, the interoperability solutions on the DAPP Network could enable a new class of multi-chain dApps to emerge. This means more efficient migration processes for dApps, a larger user-base that can expand across multiple chains, and more overall power for all chains involved.
Adoption
Companies — big and small, public and privately owned — are looking to leverage the trustlessness and transparency of blockchain technology to improve their processes and unlock new value chains for their business. With LiquidChains, a blockchain-as-a-service solution on the DAPP Network, these enterprise customers can spin up a customizable EOSIO-based blockchain in minutes and connect it to a public blockchain ledger for transparent record-keeping (if they so choose). This could allow them to enjoy the best of all worlds — the confidentiality of private blockchains, the reliability of permissioned public blockchains, and the advantages of being able to transfer data and value to and from public chains — all while harnessing the powerful services already in action on the DAPP Network.
Whichever DSP gets selected by a company gets to serve as a validator on their LiquidChains, making the DSPs key enablers of enterprise adoption for EOSIO. DSPs have a unique opportunity to leverage the DAPP Network’s suite of services, vibrant community, and cross-chain compatibility to deliver value-add solutions to traditional enterprises.
3 Simple Steps to Launch Your DSP
As a DSP, you have full autonomy when deciding how you wish to impact the EOSIO ecosystem. After you’ve registered your DSP, you are free to design whichever service packages you wish to provide. All you need to do is to choose the rates, terms and conditions, and technical specifications you think are best suited to your user base and offer those packages on a free market. The DAPP token’s inflation is distributed to the DSPs in proportion to the number of DAPP tokens staked towards their services.
In order to become a DSP, we recommend that you follow these steps:
- Prepare and host a dsp.json file
- Design your Service Packages and prepare & host dsp-package.json files
- Register your Service Packages
Step 1 — Prepare and host a dsp.json file
A DSP.json file contains information used to identify Service Providers on the DSP catalog. You may choose to include information such as a description about your DSP, your DSP’s EOS account name, links to social accounts, and contact information.
Step 2 — Design your Service Packages and prepare & host dsp-package.json files
DSPs create service packages and offer them to developers on a free market. DSPs have complete control over the service packages they provide, meaning you get to decide the Service Level Agreement of your service packages, including the cost of various actions, rate limits, and the staking duration of the agreement.
Step 3 — Register your Service Packages
Once you have designed your service packages and you’ve prepared and hosted the matching dsp-packages.json files, you can now register each package to the DAPP Network.
For a comprehensive walkthrough on becoming a DSP, visit our documentation.
EOSIO BPs: If you are serious about scalability, interoperability & adoption, then you should become a DAPP Service Provider.
Your node is up and running & the services are easily implementable, so why wait?
Here’s how you can add value to devs👇👇
https://liquidapps.io/becoming-a-DSP
