You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 10, 2019. It is now read-only.
Describe the bug
When I make calls to getTransactions, I'm getting back transactions with a null address as the sender (0x000....) which represent deposits. I don't think these should be returned in getTransactions since I can (and should) get deposits from the contract, not the operator.
Steps to reproduce
Steps to reproduce the behavior:
Make a deposit for an address.
Query transactions for that address using getTransactions.
Get back the deposit as a transaction.
Expected behavior getTransactions should not return deposits.
The text was updated successfully, but these errors were encountered:
@kfichter do you need the deposit blocks? Like the Ethereum block that the deposit was made? If I remember correctly that's why we were returning deposits. Hopefully we don't because that removing it would for sure clean up the code
Describe the bug
When I make calls to
getTransactions
, I'm getting back transactions with a null address as the sender (0x000....
) which represent deposits. I don't think these should be returned ingetTransactions
since I can (and should) get deposits from the contract, not the operator.Steps to reproduce
Steps to reproduce the behavior:
getTransactions
.Expected behavior
getTransactions
should not return deposits.The text was updated successfully, but these errors were encountered: