Sentinel, a decentralized VPN protocol based on the Cosmos SDK-based architecture, today announced that bandwidth sharing will be available for testing on the IBC-compatible Sentinel Turing-4 Cosmos test network starting in May. This transition marks a significant leap forward for the development of dApps that can be built on the Sentinel protocol as part of its proven and upcoming Web3 stack.
Sentinel has supported Cosmos from the very beginning …
Cosmos IBC uploaded in february and allows dApps based on the Cosmos blockchain to interact with other blockchains quickly and transparently. Following the migration from testnet, Sentinel users will be able to take advantage of the underlying Tendermint Byzantine fault-tolerant (BFT) protocol to enable inter-blockchain compatibility with instant finality.
Blockchains that use similar consensus algorithms, such as Proof-of-Stake (PoS), will be able to communicate with each other via Cosmos IBC using the Tendermint protocol. This alignment allows dApps that rely on the Sentinel protocol to use its proven private decentralized communications network.
In a statement regarding what the scalability and usefulness of Cosmos IBC will mean for the Sentinel network as a whole, co-founder and CEO of Exidio, Sentinel dVPN codebase contributor Dan Edlebeck said, “We envision Sentinel to have millions of daily users as we launch our white label technology. Cosmos IBC will allow us to accommodate any number of Sentinel protocol users thanks to horizontal scalability. With an emphasis on ease of use, we will allow any type of payment that Sentinel dVPN nodes wish to accept. In other words, any IBC compatible room can potentially become a way to pay for Sentinel’s dVPN services. “
Echoing Idlibeck’s sentiment, Peng Zhong, CEO of Tendermint, said, “The permissionless transfer of token value across chains is a historic moment on the timeline of a precious internet of blockchains. We will continue to focus on building the Cosmos Hub as the heart of the interlink – enabling trade and connecting politically sovereign chains to create a new paradigm of economic exchange. We have a defined roadmap in place to achieve this future and we will continue to develop services for the Cosmos Hub that will create immense value for all channels that connect to it.
Sentinel is also very happy to be integrated with Keplr, a interchain wallet. the Keplr wallet the integration will make the larger Sentinel network IBC ready right after the Cosmos Hub upgrade and just in time for the launch of DEX gravity, a decentralized exchange bringing DeFi to Cosmos.
These additions complement the community’s ambition to see Sentinel as one of Cosmos’ first native assets. The goal is for Sentinel’s most liquid trading pair to be valued in ATOM to align with Cosmos’ vision that ATOM will be the reserve currency of the interchain; where each asset will be valued in ATOMS, making it both a store of value and a medium of exchange. Sentinel will continue to rely on Cosmos to complete the tie-up between Sentinel and Cosmos both economically and technically.
Once the testnet build has passed the inspection of contributors and the wider development community, Sentinel users will be able to monetize their bandwidth on blockchains. This process is expected to take between 3 and 4 days. The success of the implementation will be determined by the Sentinel validators.
In order to publish the governance update, validators must certify the updated proposal. This will trigger the transition to the Cosmos IBC mainnet, in which case users will be able to build new applications such as Proven Private Decentralized Exchanges (DEX) through blockchains. This rapid advance in the Sentinel protocol will exponentially increase developer use cases.
With this important development, Sentinel invites validators to start testing the Sentinel dVPN protocol on the Cosmos IBC testnet starting Monday, May 3. If testing goes as planned, the Sentinel network is expected to migrate to the main IBC network by May 24. Validators who wish to participate in testnet will need to submit GenTx in the testnet repository, more details will be shared soon.
Stakeholders involved in the Sentinel network include:
- Validators – The participants in the consensus in the next Sentinel – Cosmos Hub who are responsible for securing the network and participating in the governance of the Sentinel ecosystem.
- User – The end user who wants to access a dVPN built on the Sentinel framework in order to secure the Internet in a provable way.
- DVPN node hosts – Community members intending to monetize the provision of unused bandwidth to dVPNs built on the Sentinel network, by hosting either an egress node or a relay node (meeting certain service level thresholds required) .
- DVPN app creator – The creator of a dVPN based on the Sentinel framework while using the Sentinel dVPN area as an infrastructure layer. The creator of the app is responsible for user acquisition and marketing in order to generate revenue so that they can pay dVPN node hosts.