Welcome to the world of decentralized blockchain exploration! In this guide, we will unravel the steps to run the Big Dipper block explorer, a tool designed for monitoring Cosmos-based chains. Let’s navigate through this process with ease and flair!

Why Use Big Dipper?

As the Cosmos ecosystem evolves, the legacy Big Dipper faces challenges in accommodating the increasing traffic from its interconnected chains. The official support for the legacy Big Dipper ended on December 1, 2021. However, for those interested in a customizable, easy-to-deploy block explorer compatible with Ledger for internal testnets using Cosmos SDK v0.42.x, you’re in the right place!

Projects Running on Mainnets

Big Dipper supports various projects. Here’s a glimpse:

• 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

Testnets are also well-supported:

• Agoric
• Desmos Network
• Persistence
• Regen Network
• Sentinel

How to Run Big Dipper

Get ready for the setup! Follow these steps:

1. Copy default_settings.json to settings.json.
2. Update the RPC and API URLs in settings.json.
3. Change the Bech32 address prefixes.
4. Add coins settings as per your requirement.
5. Update the Ledger settings.

Requirements

Before you proceed, ensure you have Meteor v2.x installed.

Run in Locals

To execute Big Dipper in your local environment, run:

meteor npm install --save meteor --settings settings.json

Run via Docker Compose

For Docker users, you can run it using:

METEOR_SETTINGS=$(cat settings.json) docker-compose up

Run in Production

For production deployment, utilize:

sh scripts/build.sh

This will create a packaged Node.JS tarball in the ..output directory. Use a process manager such as PM2 or Phusion Passenger for deployment. Ensure MongoDB (4.x) is installed and environment variables are correctly set.

Troubleshooting

If you encounter a non-zero exit (137) error during the build phase, consider increasing your Docker container memory and swap limit. To optimize performance, setting up a remote Docker host is recommended to prevent overheating your computer.

For more insights, updates, or to collaborate on AI development projects, stay connected with fxis.ai.

The Big Dipper Docker Image

The Big Dipper image is built using a multi-stage Docker build based on disney/meteor-base. When changing the Meteor or Node version, ensure to update the files FROM geoffreybooth/meteor-base:2 and FROM node:12.16.1-alpine respectively. Always adhere to the environment variable principles during deployment.

Analogy: Running Big Dipper

Think of running Big Dipper as setting up a captivating festival in a bustling city. Just like you need to choose a location (updating URLs), create invitations (setting up address prefixes), and define attractions (adding coin settings), running Big Dipper involves customizing its settings. The final setup is akin to opening the gates to your exciting festival, where attendees can freely explore and engage with various attractions in the Cosmos ecosystem.

Conclusion

Big Dipper is a powerful tool for monitoring Cosmos chains, whether it’s on a mainnet or testnet. With the instructions laid out, you’re now equipped to create your own instance and contribute to the evolving ecosystem.

At fxis.ai, we believe that such advancements are crucial for the future of AI, as they enable more comprehensive and effective solutions. Our team is continually exploring new methodologies to push the envelope in artificial intelligence, ensuring that our clients benefit from the latest technological innovations.