-
Couldn't load subscription status.
- Fork 1
Open
Description
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.
Metadata
Metadata
Assignees
Labels
No labels