This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Can't send transactions leaving the account with less than 0.05 LSK #2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sameersubudhi
force-pushed
the
2022-cannot-send-outgoing-transactions-with-balance-less-than-0_05-lsk
branch
from
93386b7 to
bc60739
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## development #2023 +/- ##
===============================================
- Coverage 67.89% 67.89% -0.01%
===============================================
Files 303 303
Lines 5704 5703 -1
Branches 1081 1081
===============================================
- Hits 3873 3872 -1
Misses 1831 1831
|
sameersubudhi
deleted the
2022-cannot-send-outgoing-transactions-with-balance-less-than-0_05-lsk
branch
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What was the problem?
This PR resolves #2022
How was it solved?
How was it tested?
Locally/ already patched on prod