> For the complete documentation index, see [llms.txt](https://docs.evedex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evedex.com/strategic-approach/empowering-users-through-decentralization.md).

# Empowering Users Through Decentralization

*At EVEDEX we are building a platform that progressively reduces centralized control points through a combination of technologies and governance structures. The platform implements non-custodial trading, meaning users retain control of their private keys and assets. Our architecture combines decentralized elements (like smart contract-based order settlement and community governance) with necessary operational components (like the Data Availability Committee or Hybrid Matching Engine) to balance security, performance, and trust minimization.*

## <mark style="background-color:purple;">**Create a platform for trading perpetual options and other derivatives.**</mark>

* Utilize Arbitrum’s infrastructure to deliver high scalability and reduced transaction costs.
* Leverage a custom Data Availability Committee (DAC) for secure and efficient data management.

## <mark style="background-color:purple;">Create a Trading Platform based on Hybrid Model</mark>

* Eliminate the need for trusted intermediaries, ensuring direct user control over their assets.
* Integrate decentralized oracles to provide accurate and manipulation-resistant pricing.

## <mark style="background-color:purple;">**Leverage Smart Contracts**</mark>

* Develop a robust smart contract system for automating trading processes and dispute resolution
* Ensure all trades are verifiable and immutable through blockchain integration.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.evedex.com/strategic-approach/empowering-users-through-decentralization.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
