# Overview

Traditional ride-hailing applications are often plagued by high fees, a lack of transparency, and data privacy concerns. To address these issues, nRide has developed a peer-to-peer (P2P) ride-hailing protocol that connects riders and drivers directly, without intermediaries.&#x20;

This protocol includes a messaging system, an escrow mechanism, and a driver registry, all of which are built on top of the NKN network and the JUNO blockchain.&#x20;

<img src="https://1939296743-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FowBhmkbuo7c2FBvbeV7N%2Fuploads%2FAtWP4BcRdMkGJ3ImOMOE%2Ffile.excalidraw.svg?alt=media&#x26;token=1f4f366a-fa40-4818-87ba-96b88d32cf52" alt="" class="gitbook-drawing">

The nRide protocol is governed by a decentralized autonomous organization (DAO), and is powered by the NRIDE token, which provides access to the platform and allows holders to participate in the growth and direction of the project.&#x20;

This documentation provides an in-depth technical explanation of the nRide protocol and its key components, as well as a detailed overview of the nRide governance model and the opportunities it creates for various stakeholders.

## Quick Links

{% content-ref url="introduction" %}
[introduction](https://docs.nride.com/introduction)
{% endcontent-ref %}

{% content-ref url="messaging-protocol" %}
[messaging-protocol](https://docs.nride.com/messaging-protocol)
{% endcontent-ref %}

{% content-ref url="escrow" %}
[escrow](https://docs.nride.com/escrow)
{% endcontent-ref %}

{% content-ref url="driver-registry" %}
[driver-registry](https://docs.nride.com/driver-registry)
{% endcontent-ref %}

{% content-ref url="token" %}
[token](https://docs.nride.com/token)
{% endcontent-ref %}

{% content-ref url="governance" %}
[governance](https://docs.nride.com/governance)
{% endcontent-ref %}

{% content-ref url="roadmap" %}
[roadmap](https://docs.nride.com/roadmap)
{% endcontent-ref %}

##

##

##

##

##


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.nride.com/overview.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
