DSP2.0 Is Here!
The DAPP Network Can Now Activate Beta LiquidServices, Enhanced Multi-DSP Support, EOSJS Upgrade, and Much More
Note: DSPs are strongly encouraged to set up DSP2.0 on Kylin testnet for one week before upgrading on mainnet. In addition, we encourage DSPs to add Postgres to their installation.
DAPP Service Providers (DSPs) sit at the heart of the DAPP Network. By running a dedicated node on the DAPP Network, DSPs are able to provide a host of powerful services that enable developers to scale their dApps. To that end, it is crucial that the code run by DSPs is robust, efficient, and quick so that the services the provide minimize latency while maximizing security and trustlessness.
We are pleased to unveil the next evolution of DSPs, one that will bring more speed, security, and stability to the entire DAPP Network.
Headlining DSP2.0 are 3 powerful services that have been upgraded and are now ready for Beta phase.
The promoted services are:
- LiquidAccounts: Free account creation and key management tool that allows developers to seamlessly onboard new users.
- LiquidScheduler: A task scheduler and automated task service.
- LiquidOracles: Decentralized web oracle services for sourcing external data trustlessly from within smart contracts.
In addition to the new Beta services, the DSP code has been enhanced to allow DSPs to operate more smoothly. Note: DSPs are strongly encouraged to test on Kylin for one week before upgrading on mainnet.
Many new features and changes come with DSP2.0, including:
- Third party staking is now supported, making it possible for DAPP token holders to stake DAPP and allocate services to their favorite development teams. Note: EOS mainnet contracts have not yet been upgraded to support this feature.
- Multi-DSP support has been enhanced, solidifying the ability of dApps to use redundant providers for maximum confidence.
- Database and logging are now enabled to make the DSP backend more efficient and easier to work with. Note: We encourage DSPs to add Postgres to their installation.
- The Zeus SDK is now compatible with the latest version of eosjs (20), while retaining backwards compatibility.
- DSPs can now resume from the latest block, deduplicate service request delivery, and disable and re-enable service packages.
- Services now include additional lightweight verification to increase reliability.
- k of n LiquidOracles support is now available. dApps can specify a minimum number of staked DSP LiquidOracle providers that must be live, e.g. 3 out of 5.
- A number of bugs have been exterminated.
- Support for the ZMQ demux backend has been removed.
- More documentation has been added for database, IPFS, and recovery process.
- Introducing the DAPP Network Client library! More details to follow.
The first iteration of the DSP code was powerful enough to bring around 30 DSPs around the world offering numerous packages — and enable live, cheap airdrops and onboarding. Moonlighting was even able to onboard their 750,000 users onto the blockchain without any additional friction and trust assumptions using the vRAM system. Thanks to this upgrade, not only will vRAM operate quicker and more reliably, but DSPs can now begin offering LiquidOracles, LiquidAccounts, and LiquidScheduler service packages to developers.
This latest release puts more power in the hands of DSPs, allowing them to expand their offerings with bigger and better services. The DAPP Network is becoming more flexible and more powerful, and developers can build custom services and Zeus SDK extensions to add additional capabilities.
The DAPP Network is becoming more flexible and more powerful. (Click to Tweet)
Read more at the LiquidApps documentation page.
