# 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>

* Build our own Layer 3 network using Arbitrum Orbit's Nitro Stack to enhance scalability and reduce 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: 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.evedex.com/strategic-approach/empowering-users-through-decentralization.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.