Skip to content

fetchai/cosmos-explorer

Repository files navigation

Fetch.ai Cosmos Network Explorer

This project is a fork from the excellent Big Dipper block explorer. It has been customised for the requirements of the Fetch.ai testnets.

Projects running on mainnets

Explore Akash with Big Dipper

Explore Band Protocol with Big Dipper

Explore Cosmos Hub with Big Dipper

Explore e-Money with Big Dipper

Explore IRISnet with Big Dipper

Explore IOV with Big Dipper

Explore Kava with Big Dipper

Explore LikeCoin Chain with Big Dipper

Projects with testnets

Agoric

Desmos Network

Persistence

Regen Network

Sentinel

How to run The Big Dipper

  1. Copy default_settings.json to settings.json.
  2. Update the RPC and API URLs
  3. Update Bech32 address prefixes
  4. Add coins settings
  5. Update Ledger settings

Requirements

Run in local

meteor npm install --save
SERVER_NODE_OPTIONS="--no-wasm-code-gc" meteor --settings settings.json

Run via docker-compose

docker-compose up

Run in production

./scripts/build.sh

It will create a packaged Node JS tarball in Linux x86_64 architecture at ../output. Deploy that packaged Node JS project with process manager like PM2 or Phusion Passenger.

You will need to have MongoDB >= 4.x installed and setup environment variables correctly in order run in production. For more details on how to deploy a Meteor application, please refer to the offical documentation on Custom Deployment.

Docker builds

big-dipper docker image is a multi stage build that is based on disney/meteor-base. When you change the meteor or node version, change the lines FROM geoffreybooth/meteor-base:2 and FROM node:12.16.1-alpine respectively. When running the image follow the same environment variable principles mentioned above. If you get an non-zero exit (137) error during the build phase, increase docker container memory and swap limit. Ideally you can set up remote docker host to prevent your computer's fan going brrrrrr.


Donations 🙏

You will need to have MongoDB >= 4.x installed and setup environment variables correctly in order run in production. For more details on how to deploy a Meteor application, please refer to the offical documentation on Custom Deployment.

ATOM: cosmos1n67vdlaejpj3uzswr9qapeg76zlkusj5k875ma
BTC: bc1qye4k27zsn5nehzded6jwsvzg8qd6kgvxyhckts
ETH: 0x8CAb9F3fC6bBBD819050365627FC6B79d0ea73e6

big-dipper docker image is a multi stage build that is based on disney/meteor-base. When you change the meteor or node version, change the lines FROM geoffreybooth/meteor-base:1.12.1 and FROM node:12.16.1-alpine respectively. When running the image follow the same environment variable principles mentioned above. If you get an non-zero exit (137) error during the build phase, increase docker container memory and swap limit. Ideally you can set up remote docker host to prevent your computer's fan going brrrrrr.