A TX on the 'rejected' state should still be watched for authorization.
This fixes the bug where delayed cash-out confirmations would not
trigger a exchange sell command.
* Get miner fee written in some wallet plugins
* Return txid and fee for geth. possible problem with txid (zero hash on pending transaction)
* bitgo fee return
* Wallet apis fees save in cryptoAtoms
* Add device names to sms alerts
* Write machine name on each alert
* Fixed alertSubject function (do not display machine name if null)
* Group machineNames by alertType
* Code review fixes. Filter empty machine names
* Use lodash complement instead of negate
* Revert "Use lodash complement instead of negate"
This reverts commit 385801624e432f03211867729281d7328493c30a.
* Initial itBit implementation
* Add tests for calculatePrice in exchange/itbit.js
* Add etherium to supported crypto codes in common/itbit.js
* Apply standardjs to itbit files
* itbit trade test. not important
* test getCurrencyRates in ticker/itbit.js
* Save trade error in table trades
* Add one migration, Add error column to trades table
* changes in plugins.js file
* Apply standardjs to plugins.js file
* Filter only mock options when in dev mode
* Filter only in production mode
* Refactor filter to separate function, add unit tests
* Check for mock codes in test
* Change seed file with a bip39 mnemonic
* Create helper for bip39 mnemonic
* Prod mode on lamassu-update-to-mnemonic script
* Fix standard styling issues
* Remove clutter from the logger
Prior to this commit the logger was stringfying even functions.
Because of this response errors from axios was dumping a log of info on
the logs.
* Fixing standard style issues
* Check for toString on meta
If a costumer originates a cashOut transaction at one device, and then
redeemed at a different device, the wrong machine would have bills debited from it.
With device_id being saved at the cash_out_actions table the bills can
be properly reconciled.
Made API calls return 204 on serialization error.
When network is unreliable there is a high chance of generating a
serialization exception. By returnig 204 on them the lamassu-machine can
just continue working as if nothing happened.
Made the queries from 'monitorLiveIncoming' and 'monitorStaleIncoming'
return mutually exclusive records from the db.
Both this methods are polled and perform the same actions on the
records. As a result, transaction erros were prone to happen.
