Interact with the network
Every action that inserts data into the blockchain, or alternatively extracts data from the blockchain is considered an interaction within the blockchain network. The "Interact with the network" page explains the different possibilities for other applications to interact with the blockchain network. For example, an interaction in this regard could be to POST a transaction or to GET account data from the blockchain.
Exchanges interact heavily with the network. For example, by transferring tokens for their customers. It is highly recommended to utilise exchanges to set up a node in order to interact with the network reliably.
Delegates also interact with the network by forging new blocks and adding them to the blockchain. A delegate is also typically known as a node operator.
Node operators and developers also have a general interest in monitoring their node(s) as well as the network. Their nodes provide them with a private API that can be used to perform different queries, or to post transactions to the network. Depending on their preferences, node operators may wish to use Lisk Elements, Lisk Commander or a graphical interface such as Lisk Desktop.
Applications interact with the network through the API. For convenience, applications may use wrappers such as @liskHQ/lisk-api-client. A wrapper is a library that holds methods to easily interact with the node’s API without having to know the exact underlying details of the API. This is a distinct advantage as it is not required to write API calls manually using the API specifications.
LSK Token Holders mostly interact with the network through Graphical User Interfaces (GUIs), such as wallet applications such as Lisk Desktop or Lisk Mobile.
The diagram shown below illustrates the different possibilities of interacting with the network. It is possible to use the regular interaction method through the
lisk-api-client library or deploy different methods such as the Lisk Commander CLI, Lisk Hub Wallet, or the Lisk Explorer. Lastly, it is possible to write your own API request in any programming language.
The following tools covered here are suited for network interaction with both the Lisk Mainnet and Testnet. In addition, they can also be used to interact with other blockchain applications that have been developed using the Lisk SDK. However, in this case it may be necesssary to customize the tools in order to function correctly with these other applications.
It is possible to choose up to 5 different methods to interact with an existing network, based on the most convenient and appropriate requirements as described below:
In the Lisk Elements page all available packages are both listed and documented.
Lisk Desktop is the Graphical User Interface (GUI), used to interact with the network.
This consists of wallet functionalities, such as sending transactions and viewing account history, including more extended features such as delegate voting or registering as a delegate.
Lisk Explorer is a web application that visualizes the vast information from Lisk’s blockchain.
Lisk offers Explorers for the following public networks:
The source code of Lisk Explorer is open source, and hence can be utilized to set up the user’s own Explorers to visualize and monitior the activity inside the network.
Query the API manually. Either from a public node, or connect to your own private node to interact with the network.
|To view the full specification of the Lisk Core API including example queries, please see the Lisk Core API.|
To execute the query, use any applicable tool that is suitable for HTTP API requests.
Popular tools for HTTP requests:
There are a number of nodes that are available for public use.
For example, LiskHQ is running a public testnet node that is also used to make live requests whilst trying out the different API endpoints in the documentation.
When pressing the "Try it out" button beside each endpoint, it is possible to execute the corresponding API request and receive a live response from the Lisk Testnet. It will also display the corresponding curl command in order to execute the request from the command-line.
When setting up Lisk Core, the API will be private by default. Therefore API requests will be only be accepted from the localhost.
If it is required to change this, it is possible to define exclusive whitelists that allow specific addresses to perform API requests on that specific node.