Dual Token Model

ERC20/BEP20 Fungible Utility Token of the HydroLink Ecosystem

What is a Fungible Token?

Tokens that are used as a method for payment are an example of fungible tokens. Fungible tokens can be replaced by another token of equal value. The capabilities of fungible tokens have expanded the way in which tokenised systems can be applied. Far beyond the ‘store of value’ use case, fungible tokens can administer governance rights, represent securitisation and ownership, and can be integrated into existing protocols enabling blockchain accessibility.

HydroLink utilises a novel tokenomic design encompassing a utility token and a service token. The details of each token are described below. See HydroLink's 'Utility Loop' to learn more about how our system generates utility for all network participants; whether incumbent holders or node operators.

HLNK Utility Token

HLNK is HydroLink’s fungible ERC20 utility token for the HydroLink ecosystem. The HLNK token derives value from the economic benefits available to users of the HydroLink decentralized application (dApp). HLNK's role within the HydroLink ecosystem results in a strong tie between the demand for the token and the demand to access services hosted on the utility layer of the technology stack - measured by the number of active/registered DIDs.

Decentralized Identifier (DID): A digital, verifiable identity that is user-generated and not controlled by a centralized entity. It can be used to identify any subject. This includes items such as tangible goods (i.e. solar panels, electrolyzers, smart meters), as well as person/s, organisation, and intangible assets.

Learn more: Section: Technology -> Tools

NameHydroLink Token

Symbol

HLNK

Circulating Supply

100,000,000

Contract Address

0x536a7BcdccFaff3a9A2Aa765369631Db2F247b09

Install MetaMask for Chrome

Create a MetaMask wallet using a desktop computer or an iOS/Android mobile device. That will allow you to hold, buy, sell, send, and receive HLINK

Service Token

The service token serves a crucial role in managing the pricing process and the expiration of client access to services, as HLINK payments will differ according to the number of DIDs, the DID type and the duration of service access paid for.

A DID refers to a digital, verifiable identity of any subject, such as a non-tangible asset, a customer, or an organization. Typically, DID’s are generated by the user of an application.

The sole purpose of the service token is to represent the user’s permissions regarding utility layer services and network usage. (Service tokens are not tradeable, do not hold value, and are used for representation/tracking purposes only)

Last updated