> For the complete documentation index, see [llms.txt](https://docs.dexifier.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dexifier.com/black-paper/the-solution.md).

# The Solution

### Who is the Solution Made for?

There are multiple protocols and projects that facilitate cross-chain swaps/trades, some more decentralized than others. Regardless, once machines start trading and using crypto, front-ends will become obsolete, as the machines don't need them.

Dexifier is intended for human (ALL HUMANS) use.

### Solution Characteristics 

{% hint style="info" %}
The below ideas and concepts are not neccessarily implemented yet, but that's the goal. 
{% endhint %}

To ensure Dexifier is Location, Race, & Belief (LRB) friendly the following characteristics should be available:

1. Intuitive Design.
   1. Experience must be breakthrough seamless, if user adoption is to be achieved. User adoption achieves security by numbers. The more a system is used, the more it becomes normalized, and creates pressure against shutting it down.
   2. Design must be Multilingual to achieve reach & international accessibility.
2. Availability and ease of access on most platforms, operating systems & devices.
3. Aggregation.
   1. Decentralizing trade/exchange routes and solutions, offers not only flexibility and endurance through redundancy (one route down, others still working), avoids having a single point of failure.
   2. Dramatically reduces the resources needed, as starting from scratch is not required.
4. Built on Decentralized Infra.
   1. Crypto services level: integrate the hardest solutions to shut down.
   2. Web & server hosting level: this may affect performance and accessibility, so this should be the backup version.
   3. World Wide Web alternatives: launching a lite copy of the project on alternate Networks such as ZeroNet.
5. Open Source to allow replication in case of shutdown.