Explorer is a simple, powerful utility to browse activity on the underlying blockchain network
Explorer is a simple, powerful utility to browse activity on the underlying blockchain network
| Explorer Version | Fabric Version Supported | NodeJS Version Supported |
|---|---|---|
| v2.0.0 (Sep 05, 2023) | v2.2, v2.4, v2.5 | ^12.13.1, ^14.13.1, ^16.14.1 |
| Explorer Version | Fabric Version Supported | NodeJS Version Supported |
|---|---|---|
| v1.1.8 (Aug 14, 2021) | v1.4 to v2.3 | ^12.13.1, ^14.13.1, ^16.14.1 |
| v1.1.7 (Jul 04, 2021) | v1.4 to v2.3 | ^12.13.1, ^14.13.1 |
| v1.1.6 (Jun 06, 2021) | v1.4 to v2.3 | ^12.13.1, ^14.13.1 |
| v1.1.5 (Apr 20, 2021) | v1.4 to v2.3 | ^12.13.1, ^14.13.1 |
| v1.1.4 (Jan 29, 2021) | v1.4 to v2.2 | ^12.13.1, ^14.13.1 |
| v1.1.3 (Sep 28, 2020) | v1.4.0 to v2.2.0 | 12.16.x |
| v1.1.2 (Aug 12, 2020) | v1.4.0 to v2.2.0 | 12.16.x |
There are 2 options to get Explorer started. Following are the software dependencies required for each option. And if you want to know more about each configuration, please refer README-CONFIG.md.
Note(for v2.0.0 and above): The following docker images are automatically pulled from GHCR instead of Docker Hub when starting docker-compose.
Note(for v1.1.8 and below): The following docker images are automatically pulled from Docker Hub when starting docker-compose.
This guide assumes that you've already started the test network by following Hyperledger Fabric official tutorial.
Create a new directory (e.g. explorer)
mkdir explorer
cd explorerCopy the following files from the repository
wget https://raw.githubusercontent.com/hyperledger/blockchain-explorer/main/examples/net1/config.json
wget https://raw.githubusercontent.com/hyperledger/blockchain-explorer/main/examples/net1/connection-profile/test-network.json -P connection-profile
wget https://raw.githubusercontent.com/hyperledger/blockchain-explorer/main/docker-compose.yamlCopy entire crypto artifact directory (organizations/) from your fabric network (e.g /fabric-samples/test-network)
cp -r ../fabric-samples/test-network/organizations/ .Now, you should have the following files and directory structure.
docker-compose.yaml
config.json
connection-profile/test-network.json
organizations/ordererOrganizations/
organizations/peerOrganizations/Edit environmental variables in docker-compose.yaml to align with your environment
networks:
mynetwork.com:
external:
name: fabric_test
...
services:
explorer.mynetwork.com:
...
volumes:
- ./config.json:/opt/explorer/app/platform/fabric/config.json
- ./connection-profile:/opt/explorer/app/platform/fabric/connection-profile
- ./organizations:/tmp/crypto
- walletstore:/opt/explorer/walletAn alternative option is to export environment variables in your shell.
export EXPLORER_CONFIG_FILE_PATH=./config.json
export EXPLORER_PROFILE_DIR_PATH=./connection-profile
export FABRIC_CRYPTO_PATH=./organizationsWhen you connect Explorer to your fabric network through the bridge network, you need to set DISCOVERY_AS_LOCALHOST to false for disabling hostname mapping into localhost.
services:
...
explorer.mynetwork.com:
...
environment:
- DISCOVERY_AS_LOCALHOST=falseReplace the user's certificate with an admin certificate and a secret (private) key in the connection profile (test-network.json). You need to specify the absolute path on the Explorer container.
Before:
"adminPrivateKey": {
"path": "/tmp/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp/keystore/priv_sk"
}After:
"adminPrivateKey": {
"path": "/tmp/crypto/peerOrganizations/org1.example.com/users/[email protected]/msp/keystore/priv_sk"
}Make sure you replace all paths.
Run the following to start up explore and explorer-db services after starting your fabric network:
$ docker-compose up -dTo stop services without removing persistent data, run the following:
$ docker-compose downIn the docker-compose.yaml, two named volumes are allocated for persistent data (for Postgres data and user wallet). If you would like to clear these named volumes up, run the following:
$ docker-compose down -vThis guide assumes that you've already started the test network by following Hyperledger Fabric official tutorial.
Clone this repository to get the latest using the following command.
$ git clone https://github.com/hyperledger/blockchain-explorer.git
$ cd blockchain-explorer$ cd blockchain-explorer/appModify app/explorerconfig.json to update PostgreSQL database settings.
"postgreSQL": {
"host": "127.0.0.1",
"port": "5432",
"database": "fabricexplorer",
"username": "hppoc",
"passwd": "password"
}Another alternative to configuring database settings is to use environment variables:
export DATABASE_HOST=127.0.0.1
export DATABASE_PORT=5432
export DATABASE_DATABASE=fabricexplorer
export DATABASE_USERNAME=hppoc
export DATABASE_PASSWD=pass12345Important repeat after every git pull (in some cases, you may need to apply permission to db/ directory, from blockchain-explorer/app/persistence/fabric/postgreSQL run: chmod -R 775 db/
Modify app/platform/fabric/config.json to define your fabric network connection profile:
{
"network-configs": {
"test-network": {
"name": "Test Network",
"profile": "./connection-profile/test-network.json",
"enableAuthentication": false
}
},
"license": "Apache-2.0"
}test-network is the name of your connection profile and can be changed to any namename is a name you want to give to your fabric network. You can change the only value of the key nameprofile is the location of your connection profile. You can change the only value of the key profileModify connection profile in the JSON file app/platform/fabric/connection-profile/test-network.json:
fabric-path to your fabric network disk path in the test-network.json file:_sk, for example:
/fabric-path/fabric-samples/test-network/organizations/peerOrganizations/org1.example.com/users/[email protected]/msp/keystore/priv_skexploreradmin and exploreradminpw is the credential for the user of Explorer to log in to the dashboardenableAuthentication is a flag to enable authentication using a login page. Setting to false will skip authentication.create database script:Ubuntu
$ cd blockchain-explorer/app/persistence/fabric/postgreSQL/db
$ sudo -u postgres ./createdb.shMacOS
$ cd blockchain-explorer/app/persistence/fabric/postgreSQL/db
$ ./createdb.sh
$ createdb `whoami`Connect to the PostgreSQL database and run DB status commands. To export the
settings from app/explorerconfig.json to the environment, run source app/exportConfig.sh; this will set $DATABASE_DATABASE and related envvars.
Ubuntu
sudo -u postgres psql -c '\l'
sudo -u postgres psql $DATABASE_DATABASE -c '\d'MacOS
psql -c '\l'
psql $DATABASE_DATABASE -c '\d'Expected output
…(On MacOS, expect to see your `whoami` rather than postgres. Entries with
$DATABASE_USERNAME will have the valuei of that parameter, whether set as an
environment variable or as a JSON keyval; it will not show the literal string.)
Important: repeat the below steps after every git pull
From the root of the repository:
./main.sh clean./main.sh installOr
$ cd blockchain-explorer
$ npm instNo open issues yet, or sync has not completed.