Use Case

The below section describes the actors and their interactions in the network.

Let’s consider an example of two customers, C1 and C2, with specific database requirements. Additionally, there are two node providers, X and Y, and a marketplace and deployment monitoring interface - Data3 console, which enables customers to efficiently manage their deployments. All the participants, customers and node providers, are uniquely addressed, based on their wallet addresses, when they sign-up. Kandola Network supports both custodial and non-custodial wallets, while we primarily prefer non-custodial wallets. Apart from this, the Data3 console provides a user experience for staking, by the node providers, and to the customers to be able to pay for their subscriptions.

Users have the option to register through the Data3 console and initiate requests for database deployments. These requests are then transmitted across the network, allowing node providers to submit bids. Once accepted by the user, bids become visible to the respective node provider. Additionally, node providers can engage with peers through designated communication mechanisms and protocols, following a publish-subscribe model for interactions.

Let’s consider a simple use-case, where customer C1 requests deployment using the Data3 console and Node provider X wins the bid and provisions deployment. Once the deployment is ready, customers can access the deployment directly as they would access their current centralized databases without going through the node provider. The customers can also request multiple deployments from different node providers.