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

TODO: Detect user's available network resources #2

Open
grctest opened this issue Oct 25, 2024 · 0 comments
Open

TODO: Detect user's available network resources #2

grctest opened this issue Oct 25, 2024 · 0 comments

Comments

@grctest
Copy link
Contributor

grctest commented Oct 25, 2024

If the user has insufficient CPU/RAM for their planned operation it will fail to broadcast.

Currently the only way for someone to realize this is the reason the broadcast failed is if they're running the BeetEOS client in dev mode, as the warning is shown in the terminal.

We should therefore detect the user's available system resources when they provide an EOS blockchain account, and warn them if they have insufficient resources before proceeding.

Alternatively, we could just inform the user to make sure they have sufficient EOS blockchain resources for their planned blockchain operation.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@grctest