-
Notifications
You must be signed in to change notification settings - Fork 37
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.
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
Backend: make sure fee is less than out #221
Conversation
98a842d
to
c800bf6
Compare
6d9a77b
to
fad07ba
Compare
I tested this today with BTC and I got this crash:
|
This prevents any future bug to cause unreasonable fees.
be97ade
to
746a662
Compare
@aarani what is that last 'fiup' commit? it doesn't make much sense from my point of view, I guess I'm missing something |
PS: please don't push anything to this PR until you have answered the above and I have replied/acked. |
The commit's purpose is to fix sanity check step. The Backend.Tests was referencing an old version of Logging package. |
aaa8c2e
to
86e96e5
Compare
Question: does the prompt "are you absolutely sure..." happen before or after asking the user for the password to unlock the account? |
After. |
Ok, let's change it to before, please. Otherwise I cannot test properly without losing a bunch of time and fees (and anyway , doing it before is better UX). |
We noticed in [1] that some servers return error response that has only a string error instead of an error object, so we're adding a test to prove the issue. [1] nblockchain#221
We noticed in [1] that some servers return error response that has only a string error instead of an error object, so we're adding a test to prove the issue. [1] nblockchain#221
We noticed in [1] that some servers return error response that has only a string error instead of an error object, so we're adding a test to prove the issue. [1] nblockchain#221
We noticed in [1] that some servers return error response that has only a string error instead of an error object, so we're adding a test to prove the issue. The error originally happened when I passed uint256 as txId to GetBlockchainTransaction electrum request when it should've been a string. [1] nblockchain#221
We noticed in [1] that some servers return error response that has only a string error instead of an error object, so we're adding a test to prove the issue. The error originally happened when I passed uint256 as txId to GetBlockchainTransaction electrum request when it should've been a string. [1] nblockchain#221
This prevents any future bug to cause unreasonable fees.