nRide docs
Search
K

Driver Registry

The driver registry is a fundamental component of the nRide protocol that enables riders to discover available drivers in their area. The registry is implemented as a decentralized database using blockchain technology, allowing for secure and transparent storage of driver information. Each driver entry includes their NKN address and an arbitrary location field that can be used to represent their location information in any format, giving maximum flexibility to nRide applications and users. In addition to the location field, driver entries also contain signed certificates indicating their affiliation with specific ride-hailing applications or entities. Drivers can update their location and certificate information on the registry as they move around or change affiliations, allowing riders to easily find nearby drivers and make informed choices about who to ride with.
Regarding the location field, nRide is working on a Hexagonal Hierarchical Spatial Index, which is one proposed standardized method for representing location information that provides a high level of precision while maintaining data privacy. However, since the location field is an arbitrary string, users and developers are free to define and implement their own standardized methods for organizing drivers in their area. This allows for maximum flexibility in the location field of the registry, giving developers creating applications on top of the nRide platform the ability to implement a custom location scheme to organize their drivers differently. Different location schemes correspond to different, potentially overlapping user-bases.
To ensure that riders have access to trustworthy drivers, the registry includes a certificate system that allows drivers to demonstrate their affiliation with specific ride-hailing applications or entities. Apps can filter drivers by certificate to ensure that only drivers affiliated with their app or a trusted entity are presented to their users. For example, in regions where only licensed private hire vehicles or traditional taxis are allowed to take rides, the rider can upload a signed certificate from a licensed private hire operator, and apps might broadcast requests only to drivers that have a certificate from a trusted private hire operator.
The driver registry is shared by all nRide-compatible applications, providing a common pool of drivers for riders to choose from. This allows for a more open and competitive marketplace, as riders have access to a larger pool of drivers, and apps can choose which drivers to present to their users based on specific criteria.
In summary, the driver registry is a critical component of the nRide protocol, providing a decentralized database of driver information that allows riders to easily discover available drivers in their area. By utilizing a standardized location index and certificate system, the registry ensures that riders have access to trustworthy drivers, while also allowing for maximum flexibility and customization for developers creating applications on top of the nRide platform.