Practical overview
When it fits
Use Dex when you need a forkable exchange frontend and can manage its configuration and hosting. The README provides a separate build procedure for updating the app from the related unifactory project.
Who it is for
- Teams that want to publish a branded exchange frontend for selected EVM networks.
- Operators comfortable managing a GitHub fork, page settings and custom-domain DNS.
- Operators who want to configure administrator access or optional referral activity reporting.
Documented uses
- Fork and publish an exchange interface under a custom domain.
- Choose which EVM network IDs the interface displays.
- Set the blockchain address used to access admin settings.
- Optionally route connected-address and referrer logs to a reporting endpoint.
Requirements & limits
The public repository identifies a GPL-3.0 license. Its README describes a free-start revenue-share option and an alternative premium version; it says the revenue-share fee is one-fifth of profit rather than trading volume.
- The documented deployment path depends on a GitHub fork, GitHub Pages and custom-domain DNS configuration.
- Network visibility is set through chain IDs in index.html; private-chain additions require contacting the provider.
- Referral reporting is optional and can be disabled by removing or commenting out its endpoint configuration.
- The README’s update procedure uses GitHub Codespaces with 16 GB of RAM, Node Version Manager and npm to build the related unifactory project.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Fork and publish a Dex frontend on a custom domain
Publish a forked Dex interface through GitHub Pages and connect a custom domain.
Before you start
- A GitHub account and a fork of the appsource/dex repository.
- A custom domain whose DNS you can change.
Steps
Fork the appsource/dex repository.
In the fork’s settings, enable GitHub Pages.
Add the custom domain in the repository settings and update the domain’s DNS.
Expected outcome
The fork is configured for GitHub Pages with a custom domain.
Guide limitations
- This setup sequence does not cover configuring networks or the administrator address.
- The README does not specify DNS records or propagation timing.
Set administrator access and visible EVM networks
Configure the administrator blockchain address and network IDs in a fork’s frontend.
Before you start
- A fork of the repository.
- An EVM address to use for access to admin settings.
- The chain IDs for the networks to show.
Steps
Open the root index.html in the fork.
Add the documented global configuration script inside the head element.
Set masterAddress to the administrator EVM address and chainIds to the selected network IDs.
Expected outcome
The frontend configuration specifies an administrator address and the EVM networks to display.
Guide limitations
- The README describes the index.html file as minified.
- The listed network IDs are examples; private-chain additions require contacting the provider.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- appsource/dex · Official homepage title · retained in its source language