Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CLI[BUG]: solo is not assigned node account ID correctly #748

Closed
Tracked by #420
leninmehedy opened this issue Feb 9, 2024 · 1 comment · Fixed by #749
Closed
Tracked by #420

CLI[BUG]: solo is not assigned node account ID correctly #748

leninmehedy opened this issue Feb 9, 2024 · 1 comment · Fixed by #749
Assignees
@leninmehedy
Labels
released

Comments

@leninmehedy
Copy link
Member

leninmehedy commented Feb 9, 2024 •
edited
Loading

Currently it is starting node account Ids from 0.0.0 instead of 0.0.3 as specified in the constant HEDERA_NODE_ACCOUNT_ID_START
@leninmehedy leninmehedy mentioned this issue Feb 9, 2024
Closed
@leninmehedy leninmehedy self-assigned this Feb 9, 2024
@leninmehedy leninmehedy mentioned this issue Feb 9, 2024
Merged
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.21.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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

@leninmehedy leninmehedy

Labels
released
Projects
FST Suite
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(cli): assign node account ID correctly base on start account ID hashgraph/full-stack-testing
2 participants
@leninmehedy @swirlds-automation