# LINK(ChainLink)

* Issue Time

  2017-09-22
* Total Supply

  1,000,000,000 LINK
* Circulation

  491,599,971  LINK
* White paper

  \--
* Website

  <https://chain.link/>
* Block Explorer

  <https://etherscan.io/token/0x514910771af9ca656af840dff83e8264ecf986ca>

Chainlink (LINK) is a decentralized network that provides information (oracles) to smart contracts. Founded in 2017 by Sergey Nazarov and Steve Ellis, Chainlink aims to solve the problem of off-chain information sourcing by smart contracts for their execution parameters. Smart contracts are designed to execute automatically when certain paramenters are met, however, when these parameters exist off-chain there is a reliance on sources of information (known as oracles) to provide the necessary information. Off-chain oracles tend to be centralized and with it comes a reliance on a third party to provide critical information in a trustworthy and time critical manner. ChainLink aims to break this reliance by feeding information to smart contracts via a network of decentralized oracles that work together on the Link blockchain to verify and forward critical information to these contracts. The ChainLink network allows users who have either a data feed or information carrying APIs to easily provide information to smart-contracts in exchange for the LINK token.

{% hint style="info" %}
Trade on ZKE Exchange：<https://www.zke.com/&#x20>;

Twitter：<https://twitter.com/ZKE\\_com>

Telegram：<https://t.me/ZKEGlobal>
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.zke.com/symbol/link-chainlink.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.