DL (DL) Price

DL is the token ticker for Dill. Exchange materials list it as a BSC token and state a total supply of 6 billion tokens; this defines the token's issuance network and ticker, and does not directly demonstrate that the chain architecture described in the Dill whitepaper has launched or operates as envisioned in that document. The Dill whitepaper describes Dill as a blockchain concept using a modular and sharded design, and envisages the Dill token as the common currency of that ecosystem. When reviewing related materials, distinguish the listed BSC token information from the protocol design in the whitepaper.

Under the Dill whitepaper's design, DL is envisaged as a common currency and settlement medium within the ecosystem, serving value interactions among applications, users, and intelligent agents. This describes the intended use in the whitepaper and should not be used to infer that any specific application, payment scenario, or on-chain feature is already available. The intent of this “common currency” design is to allow different applications to use an asset that can be jointly measured and settled within the same ecosystem; whether the token can be used in a given service still depends on the actual deployment and rules of the relevant network, application, and product.

The Dill whitepaper proposes a sharded architecture that is “internally modular and externally unified”: the base layer handles consensus and data availability, the settlement layer handles settlement and proof aggregation, and the execution layer lets each application use a dedicated execution environment and sequencer; native verified bridges are envisaged for interoperability between applications. Its goal is to improve scalability by separating responsibilities while avoiding ecosystem fragmentation caused by applications becoming independently isolated. The validator design is an important part of this concept. The whitepaper proposes two tiers, light validators and full validators: full validators maintain state, produce blocks, and participate in consensus voting; light validators focus on state verification, data-availability sampling, and voting. Finality requires two-thirds voting from each tier, so an attacker would need to influence both tiers simultaneously. The figures in the document, including up to 800,000 TPS, up to 1 million validators, three-slot finality, and approximately 36 seconds, are design targets, assumptions, or performance descriptions from the 2025 whitepaper and must not be treated as measured performance already achieved by the current network.