Skip to main content
It is often convenient for developers to work in an environment where changes to client or application software can be deployed and tested rapidly and without putting real-world users or assets at risk. For this purpose, the Parallax client has a --dev flag that spins up the Parallax client in “developer mode”. This creates a single-node Parallax test network with no connections to any external peers. It exists solely on the local machine. Starting the Parallax client in developer mode does the following:
  • Initialises the data directory with a testing genesis block
  • Sets max peers to 0 (meaning the Parallax client does not search for peers)
  • Turns off discovery by other nodes (meaning the node is invisible to other nodes)
  • Sets the gas price to 0 (no cost to send transactions)
  • Uses the Clique proof-of-authority consensus engine which allows blocks to be mined as-needed without excessive CPU and memory consumption
  • Uses on-demand block generation, producing blocks when transactions are waiting to be mined
This configuration enables developers to experiment with the Parallax client’s source code or develop new applications without having to sync to a pre-existing public network. Blocks are only mined when there are pending transactions. Developers can break things on this network without affecting other users. This page will demonstrate how to spin up a local Parallax testnet and a simple smart contract will be deployed to it using the Remix online integrated development environment (IDE).

​
Prerequisites

It is assumed that the user has a working the Parallax client installation (see installation guide). It would also be helpful to have basic knowledge of the Parallax client and the Javascript console. See Getting Started. Some basic knowledge of Solidity and smart contract deployment would be useful.

​
Start the Parallax client in Dev Mode

Starting the Parallax client in developer mode is as simple as providing the --dev flag. It is also possible to create a realistic block creation frequency by setting --dev.period 5 instead of creating blocks only when transactions are pending. There are also additional configuration options required to follow this tutorial. Remix will be used to deploy a smart contract to the node which requires information to be exchanged externally to the Parallax client’s own domain. To permit this, enable http and the net namespace must be enabled and the Remix URL must be provided to --http.corsdomain. For this tutorial some other namespaces will also be enabled. The full command is as follows:
The terminal will display the following logs, confirming the Parallax client has started successfully in developer mode:
This terminal must be left running throughout the entire tutorial. In a second terminal, attach a Javascript console. By default the ipc file is saved in the datadir:
The Javascript terminal will open with the following welcome message:
For simplicity this tutorial uses the Parallax client’s built-in account management. First, the existing accounts can be displayed using eth.accounts:
An array containing a single address will be displayed in the terminal, despite no accounts having yet been explicitly created. This is the “coinbase” account. The coinbase address is the recipient of the total amount of Laxes created at the local network genesis. Querying the balance of the coinbase account will return a very large number. The coinbase account can be invoked as eth.accounts[0] or as eth.coinbase:
The following command can be used to query the balance. The return value is in units of Wei, which is divided by 1e18 to give units of Lax. This can be done explicitly or by calling the web3.FromWei() function:
Using web3.fromWei() is less error prone because the correct multiplier is built in. These commands both return the following:
A new account can be created using Clef. Some of the Laxes from the coinbase can then be transferred across to it. A new account is generated using the newaccount function on the command line:
The terminal will display a request for a password, twice. Once provided, a new account will be created and its address printed to the terminal. The account creation is also logged in the Parallax client’s terminal, including the location of the keyfile in the keystore. It is a good idea to back up the password somewhere at this point. If this were an account on a live network, intended to own assets of real-world value, it would be critical to back up the account password and the keystore in a secure manner. To reconfirm the account creation, running eth.accounts in the Javascript console should display an array containing two account addresses, one being the coinbase and the other being the newly generated address. The following command transfers 50 Laxes from the coinbase to the new account:
A transaction hash will be returned to the console. This transaction hash will also be displayed in the logs in the Parallax client console, followed by logs confirming that a new block was mined (remember in the local development network blocks are mined when transactions are pending). The transaction details can be displayed in the Javascript console by passing the transaction hash to eth.getTransaction():
The transaction details are displayed as follows:
Now that the user account is funded with some Laxes, a contract can be created ready to deploy to the Parallax client.

​
A simple smart contract

This tutorial will make use of a classic example smart contract, Storage.sol. This contract exposes two public functions, one to add a value to the contract storage and one to view the stored value. The contract, written in Solidity, is provided below:
Solidity is a high-level language that makes code executable by the Parallax Virtual Machine (PVM) readable to humans. This means that there is an intermediate step between writing code in Solidity and deploying it to Parallax. This step is called “compilation” and it converts human-readable code into PVM-executable byte-code. This byte-code is then included in a transaction sent from the Parallax client during contract deployment. This can all be done directly from the Parallax client Javascript console; however this tutorial uses an online IDE called Remix to handle the compilation and deployment of the contract to the local Parallax client.

​
Compile and deploy using Remix

In a web browser, open https://remix.ethereum.org. This opens an online smart contract development environment. On the left-hand side of the screen there is a side-bar menu that toggles between several toolboxes that are displayed in a vertical panel. On the right hand side of the screen there is an editor and a terminal. This layout is similar to the default layout of many other IDEs such as VSCode. The contract defined in the previous section, Storage.sol is already available in the Contracts directory in Remix. It can be opened and reviewed in the editor. The Solidity logo is present as an icon in the Remix side-bar. Clicking this icon opens the Solidity compiler wizard. This can be used to compile Storage.sol ready. With Solidity.sol open in the editor window, simply click the Compile 1_Storage.sol button. A green tick will appear next to the Solidity icon to confirm that the contract has compiled successfully. This means the contract bytecode is available. Below the Solidity icon is a fourth icon that includes the Ethereum logo. Clicking this opens the Deploy menu. In this menu, Remix can be configured to connect to the local Parallax client. In the drop-down menu labelled ENVIRONMENT, select Injected Web3. This will open an information pop-up with instructions for configuring the Parallax client - these can be ignored as they were completed earlier in this tutorial. However, at the bottom of this pop-up is a box labelled Web3 Provider Endpoint. This should be set to Parallax client’s 8545 port on localhost (127.0.0.1:8545). Click OK. The ACCOUNT field should automatically populate with the address of the account created earlier using the Parallax client Javascript console. To deploy Storage.sol, click DEPLOY. The following logs in the Parallax client terminal confirm that the contract was successfully deployed.

​
Interact with contract using Remix

The contract is now deployed on a local testnet version of the Parallax blockchain. This means there is a contract address that contains executable bytecode that can be invoked by sending transactions with instructions, also in bytecode, to that address. Again, this can all be achieved by constructing transactions directly in the Parallax client console or even by making external http requests using tools such as Curl. Here, Remix is used to retrieve the value, then the same action is taken using the Javascript console. After deploying the contract in Remix, the Deployed Contracts tab in the sidebar automatically populates with the public functions exposed by Storage.sol. To send a value to the contract storage, type a number in the field adjacent to the store button, then click the button. In the Parallax client terminal, the following logs confirm that the transaction was successful (the actual values will vary from the example below):
The transaction hash can be used to retrieve the transaction details using the Parallax client Javascript console, which will return the following information:
The from address is the account that sent the transaction, the to address is the deployment address of the contract. The value entered into Remix is now in storage at that contract address. This can be retrieved using Remix by calling the retrieve function - to do this simply click the retrieve button. Alternatively, it can be retrieved using web3.getStorageAt using the Parallax client Javascript console. The following command returns the value in the contract storage (replace the given address with the correct one displayed in the Parallax client logs).
This returns a value that looks like the following:
The returned value is a left-padded hexadecimal value. For example, the return value 0x000000000000000000000000000000000000000000000000000000000000000038 corresponds to a value of 56 entered as a uint256 to Remix. After converting from hexadecimal string to decimal number the returned value should be equal to that provided to Remix in the previous step.

​
Reusing —datadir

This tutorial used an ephemeral blockchain that is completely destroyed and started afresh during each dev-mode session. However, it is also possible to create persistent blockchain and account data that can be reused across multiple sessions. This is done by providing the --datadir flag and a directory name when starting the Parallax client in dev-mode.

​
Re-using accounts

The Parallax client will fail to start in dev-mode if keys have been manually created or imported into the keystore in the --datadir directory. This is because the account cannot be automatically unlocked. To resolve this issue, the password defined when the account was created can be saved to a text file and its path passed to the --password flag on starting the client, for example if password.txt is saved in the top-level parallax directory:
Note that this is an edge-case that applies when both the --datadir and --dev flags are used and a key has been manually created or imported into the keystore.

​
Summary

This tutorial has demonstrated how to spin up a local developer network using the Parallax client. Having started this development network, a simple contract was deployed to the developer network. Then, Remix was connected to the local Parallax client and used to deploy and interact with a contract. Remix was used to add a value to the contract storage and then the value was retrieved using Remix and also using the lower level commands in the Javascript console.