GameChain Explorer is a blockchain browser for GameChain blockchains.

https://github.com/tedchain/gamechain-explorer

Copyright (c) 2010-2018 The Bitcoin developers
Original code was distributed under the MIT software license.
Copyright (c) 2014-2018 TEDLab Sciences Ltd
GameChain code distributed under the GPLv3 license, see COPYING file.

This software reads the GameChain block file, transforms and loads the data into a database, and presents a web interface similar to that popularized by Bitcoin block explorers like http://blockexplorer.com

GameChain Explorer is a fork of the popular Abe project to add support for GameChain blockchains with assets and permissions. GameChain nodes must be online for all explorer functions to work.

GameChain Explorer is still under development, so things may break or change!

You must have Python 2.x installed on your system to run the explorer.

On Ubuntu, you will need to install the following dependencies:

sudo apt-get install sqlite3 libsqlite3-dev
sudo apt-get install python-dev
sudo apt-get install python-pip
sudo pip install --upgrade pip
sudo pip install pycrypto

On CentOS, you will need to install the following dependencies:

sudo yum install epel-release
sudo yum install python-pip
sudo pip install --upgrade pip
sudo yum install sqlite-devel
sudo yum install python-devel
sudo yum groupinstall "Development tools"
sudo pip install pycrypto

The explorer currently supports GameChain 1.0.x versions (since 1.0 alpha 29) and protocol versions up to 10009, which is the default for GameChain 1.0.x. You can check the protocol version of an existing chain using the getinfo command.

Note that this Explorer does not yet support GameChain 2.0 preview releases.

To install GameChain Explorer for the current user (recommended):

cd gamechain-explorer
python setup.py install --user

If you have root permission and want to install GameChain Explorer for all users on the system:

cd gamechain-explorer
sudo python setup.py install

The explorer needs to connect to a local GameChain node. Before configuring the explorer, let's make sure you have a gamechain blockchain up and running.

If you do not yet have a chain you want to explore, Download GameChain to install GameChain and create a chain named chain1 as follows:

gamechain-util create chain1
gamechaind chain1 -daemon

By default the runtime parameter txindex is enabled so that the node keeps track of all transactions across the blockchain, and not just those for the node's wallet. This is required for the explorer to work correctly.

The explorer supports viewing streams which the node has subscribed to. Launch GameChain with the runtime parameter autosubscribe=streams to automatically subscribe to every stream.

The rest of this document assumes your blockchain is named chain1. If not, please substitute accordingly.

The explorer needs to communicate with the blockchain using JSON-RPC. When you created the blockchain, the JSON-RPC connection details were automatically created by GameChain and stored in a file named gamechain.conf.

The explorer will read this file. If you examine the file you will see a username and password have been auto-generated.

cd ~/.gamechain/chain1/
cat gamechain.conf

All you need to do is add the RPC port number. Copy the default-rpc-port value from params.dat and add an entry to gamechain.conf as follows:

cd ~/.gamechain/chain1/
grep rpc params.dat
# Make a note of the default-rpc-port value, let's say it's 1234, and add it to gamechain.conf
echo "rpcport=1234" >> gamechain.conf

The bundled example config file chain1.example.conf can be used as a template for your own chain.

cd gamechain-explorer
cp chain1.example.conf chain1.conf

You can store the config file chain1.conf anywhere you want. When you launch the explorer you can specify the location of your config file. By default, it will look for a config file in the current directory.

The following changes can be made:

• Change port to the port number for serving web pages (make sure your host's firewall allows traffic through that port).
• Change host to 0.0.0.0 to serve web pages to anybody (make sure there is only a single host entry in the config file).
• Change dirname to match the directory for your blockchain.
• Change chain to set how the chain should be listed in the explorer.
• Change connect-args for the location to store the explorer database.

Note: The explorer will automatically read GameChain specific parameters such as the magic handshake, address checksum, version and script version bytes from params.dat.

To load existing blockchain data into the explorer:

cd gamechain-explorer
python -m Mce.abe --config chain1.conf --commit-bytes 100000 --no-serve

Look for output such as:

block_tx 1 1
block_tx 2 2
...

This step may take several minutes to even days depending on chain size and hardware.

To launch the explorer and serve web pages from your local computer:

cd gamechain-explorer
python -m Mce.abe --config chain1.conf

By default, the explorer will be listening for web requests on port 2750, unless you changed it in the Explorer's configuration file. In your browser visit:

http://localhost:2750/

To launch the explorer on a server, make sure the explorer is not accidentally terminated when you close your SSH terminal connection.

cd gamechain-explorer
nohup python -m Mce.abe --config chain1.conf &

To check the explorer is runnning, in your browser visit:

http://ip_address_of_server:2750/

To start over with new chain data for a chain of the same name, simply:

1. Stop the explorer.

2. Delete the explorer database file chain1.explorer.sqlite (set in connect-args parameter in chain1.conf).

3. Launch the explorer as above.

The following options can be set in the explorer config file chain1.conf or as a command-line option with the format --option=value.

• home_refresh_interval_secs specifies how frequently the home page refreshes itself when open in a browser window. The default is every 60 seconds.
• recent_tx_interval_ms specifies how frequently the home page refreshes the recent transactions table including any mempool transactions. The default is every 5000 milliseconds (5 seconds),
• catch_up_tx_interval_secs specifies how frequently the explorer will load blockchain transactions into the explorer database. The default is every 60 seconds.

• Currently it is not recommended to configure multiple chains in one config file as the search function does not search across chains for an address

• You can run two instances of the Explorer with the same config file, with one being passed the --no-serve argument and the other --no-load, so that one instance only loads data into the database, and the other only serves web pages.