Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Misleading information when there is not enough lisk to send #197

Closed
karmacoma opened this issue Jun 14, 2016 · 0 comments
Closed

Misleading information when there is not enough lisk to send #197

karmacoma opened this issue Jun 14, 2016 · 0 comments
Assignees

Comments

@karmacoma
Copy link
Contributor

From: https://github.com/LiskHQ/lisk-ui/issues/51

In case we would like send more than we have, lisk return information that lisk account has no lsk at all. It should be information that there is not enough lsk to send, please deduce by X or something like that.

@karmacoma karmacoma added this to the Version 0.3.2 milestone Jun 14, 2016
@karmacoma karmacoma self-assigned this Jun 14, 2016
@fix fix assigned fix and unassigned karmacoma Jun 22, 2016
@fix fix added in progress and removed ready labels Jun 22, 2016
@karmacoma karmacoma modified the milestone: Community Forging Aug 17, 2016
@karmacoma karmacoma self-assigned this Sep 18, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants