Skip to content

Conversation

@lumtis
Copy link
Contributor

@lumtis lumtis commented Aug 8, 2022

We initialized the chain in a temporary directory so we could have a genesis to check the existing accounts without erasing the current gentx.
At the end, I think we don't need this if we don't provide a gentx from a custom path. If we use the default gentx, it means we use the one from the chain home, so the chain is already initialized.
We initialize the chain in the home if a custom gentx is used to check the accounts, when a custom gentx is used the node ID will be parsed in the gentx itself

@lumtis lumtis linked an issue Aug 8, 2022 that may be closed by this pull request
@lumtis
Copy link
Contributor Author

lumtis commented Aug 8, 2022

I think I see the error.

We set a temporary home to test the chain with the requests. Then this home is used by chaincmd to run the command to get the node ID. In consequence, the returned node ID is different from the one from the actual config

@lumtis lumtis marked this pull request as ready for review August 8, 2022 20:32
@lumtis lumtis requested a review from ilgooz August 8, 2022 20:33
@lumtis lumtis self-assigned this Aug 8, 2022
@ilgooz ilgooz merged commit c048fbe into develop Aug 9, 2022
@ilgooz ilgooz deleted the fix/gitpod-node branch August 9, 2022 08:33
Jchicode pushed a commit to Jchicode/cli that referenced this pull request Aug 9, 2023
* remove address check

* set back public address check

* change init logic

* import
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

network: Can't launch a network with several nodes on Gitpod

3 participants