Sentinel, a decentralized VPN protocol built on Cosmos SDK-based architecture, announced today that bandwidth sharing will become available for testing on the Sentinel Turing-4 Cosmos IBC-enabled testnet starting in May. This transition marks a major step forward in the development of dApps that can be built on top of the Sentinel protocol as part of the emerging arguably private Web3 stack.
Sentinel has supported Cosmos from the start …
The Cosmos IBC went live in February and enables dApps building on the Cosmos blockchain to interact with other blockchains in a fast and seamless manner. As a result of the testnet migration, Sentinel users will be able to take advantage of the underlying Tendermint Byzantine fault tolerant (BFT) protocol to enable cross-blockchain compatibility with immediate finality.
Blockchains using similar consensus algorithms, such as Proof-of-Stake (PoS), can communicate with each other through Cosmos IBC using the Tendermint protocol. This alignment allows dApps building on top of the Sentinel protocol to leverage their demonstrably private decentralized communications network.
In a statement on what the scalability and usability of Cosmos IBC will mean for the Sentinel network in general, co-founder and CEO of Exidio, an employee of the Sentinel dVPN Protocol codebase, Dan Edlebeck said: Sentinel millions of users every day as we launch our white label technology. Cosmos IBC allows us to accommodate any number of users using the Sentinel protocol through horizontal scalability. of payment that Sentinel dVPN nodes want to accept. In other words, any IBC-compliant currency could potentially become a way to pay for Sentinel’s dVPN services. “
Echoing Edlebeck’s sentiment, Peng Zhong, Tendermint’s CEO said, “The permissive transfer of token value across chains is a historic moment on the timeline to a valuable internet of blockchains. We will continue to focus on building the Cosmos Hub as the heart of the interchain – enabling trade and connecting politically sovereign chains to create a new paradigm for economic exchange. We have a defined roadmap to realize this future and will continue to develop services for the Cosmos Hub that will create tremendous value for all the chains associated with it. “
Sentinel is also very happy to be integrated with Keplr, an interchain wallet. The Keplr wallet integration makes the wider Sentinel network IBC-ready right after the Cosmos Hub is upgraded and just in time for the launch of Gravity DEX, a decentralized exchange bringing DeFi to Cosmos.
These additions complement the community’s ambition to see Sentinel as one of the first Cosmos native assets. The goal is for Sentinel’s most liquid trading pair to be priced in ATOMs to be consistent with Cosmos’s vision that ATOM will be the interchain’s reserve currency; where each asset will be priced in ATOMS, making it both a store of value and a medium of exchange. Sentinel will continue to build on Cosmos to complement the link between Sentinel and Cosmos both economically and technically.
Once the testnet build has been inspected by contributors and the wider development community, Sentinel users can monetize their bandwidth across blockchains. This process is expected to take between 3 and 4 days. Successful implementation is determined by Sentinel validators.
To release the governance update, validators must certify the updated proposal. This will trigger the transition to the Cosmos IBC main net, after which users can build new applications, such as arguably private decentralized exchanges (DEXs) across blockchains. This rapid advancement of the Sentinel protocol will exponentially expand developer usage.
With this important development, Sentinel is inviting validators to begin testing the Sentinel dVPN protocol on the Cosmos IBC testnet from Monday, May 3. If testing goes according to plan, the Sentinel network should migrate to the IBC mainnet by May 24. Validators wishing to participate in the testnet will have to submit GenTx to the testnet repository, more details on this will be shared shortly.
The stakeholders involved in the Sentinel network include:
- Validators – Consensus participants in the upcoming Sentinel – Cosmos Hub who will be responsible for securing the network and participating in the management of the Sentinel ecosystem.
- User – The end user who wants to access a dVPN built on the Sentinel framework to demonstrably secure the internet.
- dVPN node hosts – Community members who want to monetize the provision of unused bandwidth to dVPNs built on the Sentinel network, by hosting either an exit node or a relay node (meeting certain required service levels).
- dVPN Application Creator – The creator of a dVPN built on the Sentinel framework while using the Sentinel dVPN zone as an infrastructure layer. The application creator is responsible for user acquisition and marketing to generate revenue to pay for dVPN node hosts.