Opendex Deployment Guide
中文
  • Introduction
  • Why Deploy OpenDex Locally?
  • Deployment Steps
  • User Manual
  • Technical Support
Powered by GitBook
On this page
  • 1 Front-end autonomous control
  • 2 Performance optimization
  • 3 Security enhancement
  • 4 Convenient development and testing

Why Deploy OpenDex Locally?

1 Front-end autonomous control

  • Free interface customization: UI/UX design can be modified, brand logo can be added, or unnecessary functional modules can be deleted

  • Avoid hosting restrictions: No need to rely on third-party services, avoid service provider compliance review risks

2 Performance optimization

  • Local cache acceleration: The browser caches transaction history, token list and other data locally to improve secondary loading speed

  • Reduce the middle layer: Directly connect to the blockchain node to avoid platform proxy delays

3 Security enhancement

  • Anti-front-end hijacking: Avoid DNS pollution or CDN poisoning attacks when using pages

  • Code transparent audit: All front-end logic is visible locally, and it can be verified whether it contains malicious code

4 Convenient development and testing

  • Fast function iteration: Freely modify and debug front-end code without waiting for third-party updates

  • Sandbox environment testing: Supports connection to the test network for transaction simulation without affecting the production environment

PreviousIntroductionNextDeployment Steps

Last updated 2 months ago