D.Light
  • 🥳Welcome!
    • D.Light
    • Vision
    • Roadmap
  • 👀Getting Started
    • Protocol Overview
    • Optimizer
    • Tutorial
    • D.Light Farm
  • ➕More about D.Light
    • Background
      • What is Yield Farming
      • Why D.Light
    • Token Information & Allocation
  • 💻Tech & Security
    • Technical Documents
    • Smart Contract
  • 🛠️Tirms & Policy
    • Minimum Delegate Period
    • Operating Policy
    • Risk
    • Terms of Service
      • Legal Notice
    • Privacy Policy
    • Acceptable Use Policy
  • 🐦Community
    • FAQ
Powered by GitBook
On this page
  • Traditional Token Utilization Approach
  • Token Utilization Approach Using D.Light
  1. Getting Started

Protocol Overview

PreviousRoadmapNextOptimizer

Last updated 1 year ago

integrates multiple platforms dispersed across Ground Chain, providing unrivaled simplicity in usage.

Traditional Token Utilization Approach

Ground Chain offers an asset management system that utilizes various tokens.

While various platforms including FLUX, Atheneswap Staking, and Atheneswap Swap together form a comprehensive token ecosystem,

each platform has its purpose and token and the structure is somewhat complex,

making it difficult for users to easily use the service.

Token Utilization Approach Using D.Light

As mentioned earlier, the existing system using FLUX and Atheneswap within Ground Chain required users to understand the characteristics and operational methods of each protocol. As a result, many users had to invest time to learn these protocols, with some eventually giving up during the process. To address this issue and enhance user convenience, we have devised the following system.

We can observe that practical user actions were reduced to 1/3 when compared to the traditional token utilization method explained earlier.

The image above illustrates the completely redesigned crypto-life that D.Light proposes. It has been designed so that users can easily interact with D.Light through a single cycle, while the rest of the complex processes are handled internally by the D.Light Protocol.

👀
D.Light