Nibiru Chain: The breakthrough smart contract platform ushering in the next era of money. Nibiru powers an ecosystem of dApps including perps, RWAs, and more.
On 2024-06-24, while exploring the setup of a local network for new developers,
we noticed that it's too challenging to utilize the configuration that results
from running make chaosnet, which several services with docker compose:
2 Nibiru nodes
2 oracle data feed services
2 hermes IBC relayer services
Faucet service
Heart Monitor services such as graphql, heartmonitor, heartmonitor-db, and liquidator
The Point: Several of these services depend on private docker images, meaning that most
people cannot utilize the current docker compose setup.
Suggested Changes
The group proposed some improvments to the current setup:
[x] Make the default docker compose service run a single-node Nibiru network
for development ease and simplicity.
[x] Move the IBC-related services to operate under a different profile. This could include
the 2 nodes and IBC relayer services.
[x] Make the rest of the services available through a different command (or remove them), since
these are only used internally and not by third-party developers building on Nibiru.
The Problem
On 2024-06-24, while exploring the setup of a local network for new developers, we noticed that it's too challenging to utilize the configuration that results from running
make chaosnet, which several services with docker compose:graphql,heartmonitor,heartmonitor-db, andliquidatorThe Point: Several of these services depend on private docker images, meaning that most people cannot utilize the current docker compose setup.
Suggested Changes
The group proposed some improvments to the current setup: