Deploy Local Network

[Tany-Secomo]

I want to deploy the vendor-agnostic version and create/fund my own token.
Which project does prefer to us, solo or local node?
While I selected local node and installed it my Ubuntu server, I can't install multi node due to not finding network node.
Could you provide user friendly guide for deployment network with step by step?
Thanks

[hendrikebbers]

Hi,
solo will be the right tool for your usecase. While it is still in development you can find some good documentation about it at https://solo.hiero.org/v0.36.0/

[hendrikebbers]

If I understood you correctly you have a 3 node network setup by using solo? Is that correct? If yes, I do not really understand what you mean with "use Hiero as a mainnet". Is your question how you can connect an SDK to your custom network?

[Tany-Secomo]

Thanks for your questions, Hendrik.
"use Hiero as a mainnet" means that I want to know the configuration method for multiple nodes using 3 dedicated servers.

[hendrikebbers]

@jeromy-cannon can you help here?

[jeromy-cannon]

Solo is designed to run a network within one or more Kubernetes Cluster. It has configurations for multiple clusters. It is not designed to run on standalone servers. You could setup a Kubernetes Cluster in each of the dedicated servers, then run one Consensus Node in each of the clusters. Currently, we have only tested up to two clusters, but we designed it for 1+.

FYI, v0.37.1 is now the latest. v0.36.1 had some bugs, and when we released a bug fix on main it also created v0.37.0, and we didn't back patch release/0.36 (at least, not yet).

Also, we don't have any documentation for running Solo in Production mode at this time. I would recommend you run solo account init, as this will rekey all of the system accounts. Else, they are currently defaulting with the well known GENESIS key.

[jwagantall]

Closing due to lack of follow up. Please re-open if necessary